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

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

Available components

0 this week 89 Trust /100

Last scanned (3 hours ago)

Scores higher than 97% of remote servers

Unreachable for 1 day in a row. Last reached 4 Nov 2026.

Category E-commerce

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 Security11
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

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.

  • 5 Nov 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • DNSSEC: fail → unverified ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • HSTS header: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 19 Oct 26 0
    • Stability: 0.97 → pass security
  • 18 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 70. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 60. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

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 5 Nov 2026 · Probed https://growaify.com/mcp

TLS unreached
DNSSEC inconclusive

Validation of growaify.com. — Inconclusive

Zone DS Keys Algorithms Outcome
growaify.com. Error no A/AAAA/CNAME RRset answered for the name
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

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 Unreachable
http (plaintext) http://growaify.com/mcp HTTPS enforced
MCP tools · 7 exposed · ~763 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_idstring–Optional partner ID — earns 20% recurring commission on the resulting order
quantityinteger–Number of units to quote (volume discounts apply)
service_idstringyesService identifier: task-worker, website-booking, automation-n8n, ai-receptionist, or smart-consultation
NameTypeReqDescription
expires_atstring–Quote expiry (7 days)
fulfillment_slastring––
quote_idstringyesBinding quote ID (Q-MCP-...) used for purchase_service
service_idstring––
total_usdnumberyes–
unit_pricenumber–Agent 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.

get_payment_requirements ~150

Returns the exact x402 payment requirements for a paid resource (amount, asset, network, payTo) so you can construct the signed payment yourself. Open without a key - the requirements are public because paying is the only thing they enable. 80% of agent visits stop at /mcp and never reach a paid path; this tool puts the paywall where the agents actually are.

NameTypeReqDescription
resourcestringyesThe paid path, e.g. /x402/obs/tick, /x402/obs/agents, /x402/obs/methodology, /x402/template, /x402/audit, or /x402/item/<id> for a micro item

No output schema declared.

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_idstring–Your agent identifier for wallet and tracking
emailstringyesContact email for order receipts and deliverable delivery
quote_idstringyesQuote ID from create_binding_quote
webhook_urlstring–Optional 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_urlsobject–PayPal, 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.

register_agent_test ~131

Register once and receive a private path where your agent meets a real HTTP 402: the production wire format, the production signing requirements and the production facilitator, priced at the cheapest artefact we sell so a success costs $0.001 rather than a guess. The response carries a report URL where you read your own agent's funnel - challenged, attempted, rejected, delivered. No API key required. The id is the capability: whoever holds it can read the report.

NameTypeReqDescription
namestringyesWhich agent is being tested. Required.
notestring–Anything worth recording about it. Optional.

No output schema declared.

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.

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'
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 89 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 7 tools: discover_capabilities, get_payment_requirements, create_binding_quote, purchase_service, track_order_telemetry, and 2 more. Their descriptions and schemas cost roughly 763 tokens of context every time the server is loaded.

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

Its publisher declares no required credentials for Growaify — Autonomous Commerce for AI Agents. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

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

Growaify — Autonomous Commerce for AI Agents is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.