GrowVib: Social Media Growth

com.growvib由 growvib.com 發布官方發布者v0.4.0更新於 Nov 7, 2026

Discover, compare and buy social media growth (Instagram, TikTok, YouTube, Telegram, X); x402 ready

已驗證Streamable HTTP可網頁執行金融商業與電商

概覽

AI 產生的概覽

GrowVib 讓助理瀏覽社群媒體成長服務目錄、取得精確報價,並透過 x402 以 USDC 下單或追蹤訂單。

可以做什麼
  • 搜尋可販售的社群媒體成長服務目錄,檢視含所有方案選項的服務詳情
  • 依數量、受眾與偏好推薦一個方案選項
  • 下單前取得將實際收取的精確美元價格
  • 以 Base 或 Solana 上的 USDC 下單並付款,或建立由本人錢包付款的結帳連結
  • 查詢結帳狀態、追蹤訂單交付與開始進度,並列出某個錢包的訂單
適用情境
當使用者想為 Instagram、TikTok、YouTube、Telegram 或 X 購買社群媒體成長服務,並希望助理比較選項、報價並下單或追蹤訂單時使用。也適合代理程式需要以 USDC 自主支付服務的情境。
執行需求
遠端 streamable HTTP 端點,不需在本機安裝。訂單須以 Base 或 Solana 上的 USDC 付款,可由代理程式透過 x402 付款協定完成,或由本人透過結帳連結付款。列出某個錢包的訂單需要 agent_token。
安裝前請注意
下單會花費真實的 USDC,且可在無人確認的情況下自動下單,建議先以 get_quote 確認價格與數量。付款要求與錢包憑證屬敏感資訊,agent_token 應視為機密。下單即產生付款,交付是逐步進行的,需要輪詢狀態。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 GrowVib: Social Media Growth,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/com.growvib%2Fgrowvib/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "growvib-social-media-growth": {
      "type": "http",
      "url": "https://api.growvib.com/mcp-public"
    }
  }
}

工具

9

create_checkout

Create a checkout session: a payment link a PERSON opens and pays in their own USDC wallet (Base or Solana), for when you cannot sign a payment yourself or the user wants to pay with their own wallet. Pick the service with search_catalog or recommend_service and price it with get_quote first, then call this with service_id, quantity and link. The result carries page_url (give it to the person), the exact amount, expires_at (the price is held until then, 30 minutes by default) and a token for get_checkout_status. Creating a session moves no money and reserves nothing: nothing is charged until the person signs in their wallet, and an unpaid session simply expires. Each call opens a NEW session, so call it once per intended order and reuse the token you were given. Prefer create_paid_order when you hold a wallet and should pay yourself.

輸入參數link必填quantity必填return_urlservice_id必填ttl_secondsexternal_refservice_option_id

create_paid_order

Place an order and pay for it with USDC on Base or Solana, with no GrowVib account and no human in the loop, using the x402 payment protocol. Call it FIRST without the `payment` argument: it returns the exact payment requirements, one `accepts` entry per network (amount in atomic units, asset, recipient, network, and for Solana the facilitator's feePayer). Pick the network your wallet is on: sign an EIP-3009 transferWithAuthorization (Base) or build and sign the USDC transfer transaction (Solana) for exactly those requirements, then call it AGAIN with the same arguments plus `payment` set to the signed x402 payment payload. Anything paid above the order's price stays as spendable balance on the wallet's account, so many small orders can be paid for with one settlement. If a call reports that the payment is still being confirmed, do NOT sign and send a new payment: the first one may already have gone through. Use get_quote first if you only want a price.

輸入參數link必填postspaymentquantity必填service_id必填agent_tokenidempotency_keyservice_option_id

get_checkout_status

Read a checkout session created with create_checkout: its status (open, pending, paid, paid_no_order, failed, expired), the frozen quote, and once paid the payment and the order with its tracking code. Poll it after handing the person the link, every few seconds, until it reports paid or expired. `pending` means a payment is being confirmed: tell the person to wait, never to pay again. `paid_no_order` means the money arrived as balance on the paying wallet's account but the order could not be placed; the person was told to contact support. Read-only and idempotent, so polling is safe.

輸入參數token必填

get_paid_order_status

Track an order placed with create_paid_order: status, start count and remaining quantity, plus a delivery block (the start bucket the option listed and its bound in hours, whether delivery has started, and start_overdue when an active order has not started past that bound). Delivery is gradual once it starts and completion time is not estimated, so a falling remains is progress, not a stall. Pass the `agent_token` that create_paid_order returned (or one from the wallet sign-in at POST /v1/agent/auth/challenge). Read-only and idempotent, so polling it is safe. Statuses: PENDING, SUBMITTED, PROCESSING, COMPLETED, PARTIALLY_COMPLETED, CANCELED, FAILED, PARTIALLY_FAILED, REFUNDED, PARTIALLY_REFUNDED.

輸入參數order_id必填agent_token必填

get_quote

Get the exact price that will be charged, with no account needed. Call this before every order: never total up the per-1000 prices the catalog tools return yourself, because the quantity bounds and rounding are applied here and nowhere else. Returns unit price and total in USD, priced by the same server-side path a real order uses. It places no order and charges nothing. The result's payment_methods says how the order can be paid: from a connected GrowVib account (connect one over OAuth at the /mcp endpoint, which is where the account ordering tool lives), or, when listed, with no account at all over x402 (USDC on Base or Solana, via create_paid_order or the REST endpoint it names; payment_methods.x402.networks lists the rails).

輸入參數postsquantity必填service_id必填service_option_id

get_service

Look up ONE service you already have the id for. No id yet? Find one with search_catalog. Want a single option chosen for a quantity rather than all of them? Use recommend_service. Returns the service's full detail, including ALL of its plan options (id, name, price per 1000, min/max quantity, quality tier, typed axes such as country or watch length, listed delivery speed and start window, and the recommended flag), so you can present the available plans and quantity range to the user, then pass the chosen service_option_id to get_quote and create_paid_order (this endpoint lists it while the accountless x402 payment channel is on), or create_checkout when a person will pay in their own wallet instead (listed while checkout sessions are on).

輸入參數service_id必填

list_paid_orders

List the orders belonging to the wallet behind an agent_token, newest first, each with the same fields get_paid_order_status returns. Use it when you no longer have the order_id an order gave you: after a restart, when resuming work another session started, or to check everything this wallet has bought. Pass the `agent_token` from any of its orders (or from the wallet sign-in at POST /v1/agent/auth/challenge). Optional `status` narrows to one order status, `page` and `page_size` page through the rest (page_size defaults to 10 and is capped at 100; the result carries the total so you know when to stop). Read-only and idempotent, so polling it is safe.

輸入參數pagestatuspage_sizeagent_token必填

recommend_service

Choose WHICH plan option to order, once you know what to buy and for how many. Use it instead of comparing options yourself from search_catalog or get_service. Takes a service (or a platform plus a goal), a quantity, an audience and a preference. Returns one recommended option plus the cheapest, highest-tier and fastest-listed alternatives. Each pick carries the price per 1000, the total for this quantity, the quantity range it accepts, its quality tier, typed axes such as country or watch length, the listed delivery speed and start window, a sensitive flag marking a deliberate product such as a negative reaction, and short reasons written for the buyer. Branch on the typed fields; the reasons are prose in the requested locale and state only what an option gives, so their absence is never a drawback. One reason states how many independent delivery pools can serve the option, when two or more can: it is a count of the ways we can deliver it, not a promise about any one order, and a pick without it is not worse. The response also says how many options were considered, how many fit, and why the rest fell out (rejected: audience_mismatch, quantity_below_min, quantity_above_max, dominated). It carries quoted_at and catalog_version: the version fingerprints the option data the answer came from, so if you recommend, ask the user, then order, re-call and compare catalog_version to know whether the card changed in between. Prices are live at order time; placing an order re-prices from the same data get_quote does, so treat quoted_at as when this answer was computed, not as a price hold. tradeoffs compares each alternative with the lead as data (price and total deltas, quality steps, listed speed ratio, start bucket delta, max quantity delta, plus gives and costs naming the dimensions it wins and loses on; null means one side lists nothing). Use it to CHOOSE and to explain a choice as what each option gives ("$18.60 less for one tier lower and twice the listed rate"); never p

輸入參數goallocaleaudienceplatformpriorityquantity必填service_id

search_catalog

START HERE when you do not yet know which service to buy: this is the entry point to the catalog. Already have a service id? get_service returns that one in full detail. Know the service and only need the right plan for a quantity? recommend_service picks one. Searches the sellable social growth service catalog (Telegram, Instagram, TikTok, YouTube and more). Each result includes the service (id, name, platform, starting/cheapest price per 1000) AND up to 8 of its plan options (the recommended and cheapest ones, each with id, name, price per 1000, min/max quantity; options_total says how many there are and get_service returns them all) - present the options to the user and let them choose a plan, then pass that service_option_id to get_quote and create_paid_order (this endpoint lists it while the accountless x402 payment channel is on), or create_checkout when a person will pay in their own wallet instead (listed while checkout sessions are on) instead of defaulting to the cheapest.

輸入參數limitquerylocaleoffsetcountrysort_byplatformmax_pricemin_pricesort_orderspeed_tierquality_tier

版本歷史

3
  1. v0.4.0最新Nov 7, 2026
  2. v0.3.0Oct 3, 2026
  3. v0.2.0Sep 16, 2026

評分

已滿足適用檢查項的 83%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分

    請宣告包含 README 的 GitHub 儲存庫,或在 OAuth 受保護資源後設資料中提供 resource_documentation。

  • 授權條款不適用

    託管服務按其提供方的條款使用,因此這裡不要求授權條款。此檢查項不計入百分比。