GrowVib: Social Media Growth
REMOTE · API.GROWVIB.COM · SCANNED SEP 20
Discover, compare and buy social media growth for Instagram, TikTok, YouTube, Telegram, X and more
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (create_paid_order). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2576 tokens (~368/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability check failed: schema churn in the 10 days we've observed: 2 tool removals, 0 breaking changes, 0 auth/transport breaks, 3 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the GrowVib: Social Media Growth MCP server?
GrowVib: Social Media Growth is a hosted endpoint at https://api.growvib.com/mcp-public, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.growvib.com
claude mcp add --transport http com-growvib-growvib 'https://api.growvib.com/mcp-public'
{
"mcpServers": {
"com-growvib-growvib": {
"url": "https://api.growvib.com/mcp-public"
}
}
} {
"servers": {
"com-growvib-growvib": {
"type": "http",
"url": "https://api.growvib.com/mcp-public"
}
}
} [mcp_servers.com-growvib-growvib] url = "https://api.growvib.com/mcp-public"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-growvib-growvib": {
"type": "remote",
"url": "https://api.growvib.com/mcp-public",
"enabled": true
}
}
} openclaw mcp add com-growvib-growvib --url 'https://api.growvib.com/mcp-public' --transport streamable-http
mcp_servers:
com-growvib-growvib:
url: "https://api.growvib.com/mcp-public" {
"McpServers": {
"com-growvib-growvib": {
"Transport": "http",
"Url": "https://api.growvib.com/mcp-public"
}
}
} assistant mcp add com-growvib-growvib -t streamable-http -u 'https://api.growvib.com/mcp-public'
{
"mcpServers": {
"com-growvib-growvib": {
"type": "http",
"url": "https://api.growvib.com/mcp-public"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 16 Sept 26 0
- Tool “recommend_service” rewrote its description, which is the text the model reads security
- 13 Sept 26 −1
- Stability: 0.07 → fail ▼ security
- A breaking change shipped without a version bump: still 0.1.0 ▼ security
- Tool “paid_order_status” was removed ▼ security
- Tool “place_paid_order” was removed ▼ security
- New tool “create_paid_order”, which the server declares destructive security
- Tool “get_quote” rewrote its description, which is the text the model reads security
- Tool “get_service” rewrote its description, which is the text the model reads security
- Tool “recommend_service” rewrote its description, which is the text the model reads security
- Tool “search_catalog” rewrote its description, which is the text the model reads security
- Schema quality: 2093 → 2576 ▼ functional
- New tool “get_paid_order_status” functional
- New tool “list_paid_orders” functional
- 12 Sept 26 +2
- DNSSEC: fail → pass ▲ security
- 11 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 10 Sept 26 65
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://api.growvib.com/mcp-public
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=growvib.com | CN=WE1,O=Google Trust Services,C=US | 29 Jul 2026 | 27 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | ad290b3ec1509e713f2c63ef60d6e48 |
| SANs: growvib.com, *.growvib.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of api.growvib.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| growvib.com. | present | 2371 | 13 | Verified |
| api.growvib.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.growvib.com/mcp-public | Verified | 200 | |
| http (plaintext) | http://api.growvib.com/mcp-public | HTTPS enforced | 301 | https://api.growvib.com/mcp-public |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_paid_order ~435
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_token | string | – | The agent_token from a previous order's result. Send it INSTEAD of `payment` to pay out of the balance you already hold, with no new signature and nothing on chain. Requires `idempotency_key`. If you… |
| idempotency_key | string | – | A value unique to this order attempt (a UUID is fine), required when using `agent_token`. Sending the same key again returns the SAME order instead of buying a second time, so a retry after a timeout… |
| link | string | yes | The target link the order is delivered to. |
| payment | object | – | The signed x402 v2 payment payload. Omit on the first call to receive the payment requirements. |
| quantity | number | yes | Quantity to order. |
| service_id | string | yes | The service id from search_catalog. |
| service_option_id | string | – | Optional specific service option id; defaults to the service's primary option. |
No output schema declared.
No examples provided.
get_paid_order_status ~173
Track an order placed with create_paid_order: status, start count and remaining quantity. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_token | string | yes | The agent_token from create_paid_order's result, or from the wallet sign-in. It proves which wallet is asking; an order that is not this wallet's is reported as not found. |
| order_id | string | yes | The order_id from create_paid_order. |
No output schema declared.
No examples provided.
get_quote ~223
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).
| Name | Type | Req | Description |
|---|---|---|---|
| quantity | number | yes | Quantity to order (e.g. number of members or views). |
| service_id | string | yes | The service id from search_catalog. |
| service_option_id | string | – | Optional specific service option id; defaults to the service's primary option. |
No output schema declared.
No examples provided.
get_service ~157
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).
| Name | Type | Req | Description |
|---|---|---|---|
| service_id | string | yes | The service id from search_catalog. |
No output schema declared.
No examples provided.
list_paid_orders ~290
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_token | string | yes | The agent_token from one of this wallet's orders, or from the wallet sign-in. It proves which wallet is asking; only that wallet's orders are returned. |
| page | number | – | 1-based page number (default 1). |
| page_size | number | – | Rows per page (default 10, maximum 100). |
| status | string | – | Optional order status to filter by: PENDING, SUBMITTED, PROCESSING, COMPLETED, PARTIALLY_COMPLETED, CANCELED, FAILED, PARTIALLY_FAILED, REFUNDED or PARTIALLY_REFUNDED. |
No output schema declared.
No examples provided.
recommend_service ~772
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…
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | – | "worldwide" (default) for untargeted delivery, or "<axis>:<value>" such as "country:usa" or "emoji:❤️". The response lists the audiences the service serves. |
| goal | string | – | The deliverable metric key (followers, likes, views, short-views, members, comments, ...). Used with platform when service_id is omitted. |
| locale | string | – | Language of the option labels and the reasons: en (default), fa, ru, uz or id. The typed fields are locale-independent, so pass the user's language freely. |
| platform | string | – | Platform key (telegram, instagram, tiktok, youtube, ...). Used with goal when service_id is omitted. |
| priority | string | – | "balanced" (default), "cheapest", "quality" or "fastest": which pick leads. fastest ranks on the LISTED delivery rate then start window (the listing's own claims); when no eligible option lists eithe… |
| quantity | number | yes | The quantity the user wants to order; every pick accepts it. |
| service_id | string | – | The service id from search_catalog. Optional when platform and goal are given. |
No output schema declared.
No examples provided.
search_catalog ~526
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 its plan options (each with id, name, price per 1000, min/max quantity) - 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) instead of defaulting to the cheapest.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Filter to geo-targeted services for a country (matches the catalog's geo-target codes, e.g. a country name or code). Most services are global and unaffected. |
| limit | number | – | Max results per page (1-50, default 20). |
| locale | string | – | Catalog language for names/descriptions (default en). Each service is returned once per call in this single language. |
| max_price | number | – | Only services whose starting price per 1000 is at most this (USD) - use for a budget cap. |
| min_price | number | – | Only services whose starting price per 1000 is at least this (USD). |
| offset | number | – | Row offset for paging (default 0). The response returns total, limit, offset and returned; fetch the next page with offset += limit while offset+returned < total. |
| platform | string | – | Filter by platform key, e.g. telegram, instagram, tiktok, youtube. |
| quality_tier | string | – | Filter by quality tier, e.g. standard, premium. |
| query | string | – | Keyword search over service names and descriptions. Pass concrete keywords (e.g. "telegram members"); map the user's natural-language intent (budget, country, speed) onto the structured filters below. |
| sort_by | string | – | Sort order: "newest" (default) or "name" (alphabetical). |
| sort_order | string | – | "asc" or "desc". Defaults to desc for newest, asc for name. |
| speed_tier | string | – | Filter by delivery speed tier (e.g. instant, fast) - use for "fastest delivery" requests. |
No output schema declared.
No examples provided.
What is the GrowVib: Social Media Growth MCP server?
GrowVib: Social Media Growth is an MCP server listed in the public MCP registry as com.growvib/growvib. Discover, compare and buy social media growth for Instagram, TikTok, YouTube, Telegram, X and more. This page covers its hosted endpoint (https://api.growvib.com/mcp-public).
Is the GrowVib: Social Media Growth MCP server safe to use?
GrowVib: Social Media Growth scores 66 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the GrowVib: Social Media Growth MCP server expose?
GrowVib: Social Media Growth exposes 7 tools: create_paid_order, get_paid_order_status, get_quote, get_service, list_paid_orders, and 2 more. Their descriptions and schemas cost roughly 2,576 tokens of context every time the server is loaded.
Does the GrowVib: Social Media Growth MCP server require authentication?
No. We connected to GrowVib: Social Media Growth without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the GrowVib: Social Media Growth MCP server still maintained?
GrowVib: Social Media Growth is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.