Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Growaify — Autonomous Commerce for AI Agents

REMOTE · GROWAIFY.COM · SCANNED SEP 20

Autonomous commerce for AI agents: discover, quote, order, pay, verify.

Available components

70 Trust /100
Trust breakdown (7 categories)

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 Security83
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 954 tokens (~190/item across 5 items; 5 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 Management3
  • Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the Growaify — Autonomous Commerce for AI Agents MCP server?

Growaify — Autonomous Commerce for AI Agents is a hosted endpoint at https://growaify.com/mcp, 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 · growaify.com

# add to Claude Code
claude mcp add --transport http com-growaify-mcp 'https://growaify.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-growaify-mcp": {
      "url": "https://growaify.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-growaify-mcp": {
      "type": "http",
      "url": "https://growaify.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-growaify-mcp]
url = "https://growaify.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-growaify-mcp": {
      "type": "remote",
      "url": "https://growaify.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-growaify-mcp --url 'https://growaify.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-growaify-mcp:
    url: "https://growaify.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-growaify-mcp": {
      "Transport": "http",
      "Url": "https://growaify.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-growaify-mcp -t streamable-http -u 'https://growaify.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-growaify-mcp": {
      "type": "http",
      "url": "https://growaify.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 20 Sept 26 0
    • Tool “create_binding_quote” rewrote its description, which is the text the model reads security
    • Tool “discover_capabilities” rewrote its description, which is the text the model reads security
    • Tool “purchase_service” rewrote its description, which is the text the model reads security
    • Tool “query_trust_and_sla” rewrote its description, which is the text the model reads security
    • Schema quality: 166 → 190 functional
    • Stability: unverified → 0.03 functional
    • Schema quality: good → excellent functional
  • 19 Sept 26 70

    First indexed and scored.

Diagnostics

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://growaify.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=growaify.com CN=YE1,O=Let's Encrypt,C=US 24 Aug 2026 22 Nov 2026 ECDSA 256 ECDSA-SHA384 5fb1ae71c4126085780704c80176cef9082
SANs: growaify.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of growaify.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
growaify.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On tool calls
HTTP status 200

Protected resource metadata

Retrieved No
Problem no_resource_metadata

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://growaify.com/mcp Verified 200
http (plaintext) http://growaify.com/mcp HTTPS enforced 301 https://growaify.com/mcp
MCP tools · 5 exposed · ~482 tokens

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 →

Tool Tokens
create_binding_quote ~147

Generate a binding, deterministic quote with agent discount pricing and wholesale volume tiers. Quote is valid for 7 days. AUTH: requires an API key - get one instantly with POST https://growaify.com/api/v1/agents/register using name and purpose fields. No email needed. Send it as the X-API-Key header.

NameTypeReqDescription
partner_idstringOptional partner ID — earns 20% recurring commission on the resulting order
quantityintegerNumber of units to quote (volume discounts apply)
service_idstringyesService identifier: task-worker, website-booking, automation-n8n, ai-receptionist, or smart-consultation
NameTypeReqDescription
expires_atstringQuote expiry (7 days)
fulfillment_slastring
quote_idstringyesBinding quote ID (Q-MCP-...) used for purchase_service
service_idstring
total_usdnumberyes
unit_pricenumberAgent price per unit in USD

No examples provided.

discover_capabilities ~94

Match your requirements (e.g. ['whatsapp', 'booking', 'multilingual']) against the whole Growaify catalogue - services, templates and the 489-item micro catalogue - and return matches with pricing and a direct buy link. No API key required.

NameTypeReqDescription
required_capabilitiesarrayyesList of capability keywords to match, e.g. ['whatsapp', 'booking', 'multilingual', 'automation']
NameTypeReqDescription
matches_foundintegeryesNumber of matching services
servicesarrayyes

No examples provided.

purchase_service ~145

Place an idempotent commercial order from a binding quote. Payment settles via PayPal, x402 (USDC on Base), or Agent Wallet. AUTH: requires an API key - get one instantly with POST https://growaify.com/api/v1/agents/register using name and purpose fields. No email needed. Send it as the X-API-Key header.

NameTypeReqDescription
agent_idstringYour agent identifier for wallet and tracking
emailstringyesContact email for order receipts and deliverable delivery
quote_idstringyesQuote ID from create_binding_quote
webhook_urlstringOptional public https URL to receive order status webhooks
NameTypeReqDescription
amount_usdnumber
order_idstringyesOrder ID (ORD-...) for tracking
payment_statusstringyespayment_pending until settled via a verified rail
payment_urlsobjectPayPal, x402, and wallet payment endpoints
service_idstring

No examples provided.

query_trust_and_sla ~44

Inspect cryptographic checksum policy, refund policies, payment rails, and trust metadata for the platform. No API key required - read this before you decide to buy.

Input schema present but exposes no named parameters.

NameTypeReqDescription
agent_cardstring
payment_railsarray
security_manifeststring
state_machinestring
trust_portalstring

No examples provided.

track_order_telemetry ~52

Query order state, execution progress (0-100%), and provisioned digital deliverables with SHA-256 checksums.

NameTypeReqDescription
order_idstringyesOrder ID returned by purchase_service (ORD-...)
NameTypeReqDescription
deliverablesarray
order_idstringyes
order_statusstringyespayment_required | paid | fulfillment | completed | fulfillment_failed
payment_statusstring
progress_percentinteger

No examples provided.

Common questions

What is the Growaify — Autonomous Commerce for AI Agents MCP server?

Growaify — Autonomous Commerce for AI Agents is an MCP server listed in the public MCP registry as com.growaify/mcp. Autonomous commerce for AI agents: discover, quote, order, pay, verify. This page covers its hosted endpoint (https://growaify.com/mcp).

Is the Growaify — Autonomous Commerce for AI Agents MCP server safe to use?

Growaify — Autonomous Commerce for AI Agents scores 70 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 Growaify — Autonomous Commerce for AI Agents MCP server expose?

Growaify — Autonomous Commerce for AI Agents exposes 5 tools: discover_capabilities, create_binding_quote, purchase_service, track_order_telemetry, query_trust_and_sla. Their descriptions and schemas cost roughly 482 tokens of context every time the server is loaded.

Does the Growaify — Autonomous Commerce for AI Agents MCP server require authentication?

Yes. Growaify — Autonomous Commerce for AI Agents asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Growaify — Autonomous Commerce for AI Agents MCP server still maintained?

Growaify — Autonomous Commerce for AI Agents 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.