Skip to content

Growaify — Autonomous Commerce for AI Agents MCP server

com.growaify/mcpgrowaify.comstreamable-httpv2.3.9Scanned

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

7 tools: 1 do something that can't be undone, 3 change things and 3 only read.

Tools: 0 delete, 1 irreversible, 3 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

Anlyon alternative

4 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Its sign-in does not let Anlyon set up an OAuth client on its own, so there is no link to it here.

What the Growaify — Autonomous Commerce for AI Agents MCP server can do

The Growaify — Autonomous Commerce for AI Agents MCP server is published by growaify.com, a domain the MCP Registry verified. It has 7 tools. It can do things that cannot be undone, such as sending, paying or publishing (purchase_service) and create or change data (3 tools: discover_capabilities, create_binding_quote and register_agent_test), but cannot delete data. 3 tools only read.

1 tool can send data out of your system (purchase_service).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 19, 2026, version 2.3.9.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Can't be undone 1Claude Code: ask
  • purchase_servicePlace an idempotent commercial order from a binding quote.Can send data outNo findings

    Why it is in this group

    • The name "purchase_service" says "purchase": a word that usually means money moves, which cannot be taken back.

    What it can reach

    • outboundThe input takes a URL (input.webhook_url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
Changes things 3Claude Code: ask
  • create_binding_quoteGenerate a binding, deterministic quote with agent discount pricing and wholesale volume tiers.No findings

    Why it is in this group

    • The name "create_binding_quote" says "create": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
  • discover_capabilitiesMatch your requirements (e.g.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • register_agent_testRegister 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, pri…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
Only reads 3Show 3 read-only tools
  • get_payment_requirementsReturns the exact x402 payment requirements for a paid resource (amount, asset, network, payTo) so you can construct the signed payment yourself.No findings

    Why it is in this group

    • The name "get_payment_requirements" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • query_trust_and_slaInspect cryptographic checksum policy, refund policies, payment rails, and trust metadata for the platform.No findings

    Why it is in this group

    • The name "query_trust_and_sla" says "query": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
  • track_order_telemetryQuery order state, execution progress (0-100%), and provisioned digital deliverables with SHA-256 checksums.No findings

    Why it is in this group

    • The description's first verb is "query": a word for reading.
    Description, as the server wrote it
    Query order state, execution progress (0-100%), and provisioned digital deliverables with SHA-256 checksums.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:39 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2024-11-05
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://growaify.com/.well-known/oauth-protected-resource/mcp
Authorization servers
https://growaify.com
Legacy HTTP+SSE transport
no
Dynamic client registration
no
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (1 irreversible, 3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://growaify.com/mcp: tools/list returned 7 tools to an anonymous client, including purchase_service (irreversible), discover_capabilities (write), create_binding_quote (write), register_agent_test (write)

    What this check looks for

Posture changes

  1. Nov 13, 2026
    • Reachable: no to yes
    • HTTP status of an anonymous initialize: none to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 4
    • Protocol version: none to 2024-11-05
    • RFC 9728 protected resource metadata: none to https://growaify.com/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://growaify.com
    • Dynamic client registration: not observed to no
    • Client ID metadata documents: not observed to no
  2. Nov 6, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 4 to 0
    • Protocol version: 2024-11-05 to none
    • RFC 9728 protected resource metadata: https://growaify.com/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://growaify.com to none
    • Dynamic client registration: no to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: no -> yes; HTTP status of an anonymous initialize: none -> 200; tools/list served without credentials: no -> yes (and 6 more).View diff
    • Reachable: no to yes
    • HTTP status of an anonymous initialize: none to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 4
    • Protocol version: none to 2024-11-05
    • RFC 9728 protected resource metadata: none to https://growaify.com/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://growaify.com
    • Dynamic client registration: not observed to no
    • Client ID metadata documents: not observed to no
  2. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 4 to 0
    • Protocol version: 2024-11-05 to none
    • RFC 9728 protected resource metadata: https://growaify.com/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://growaify.com to none
    • Dynamic client registration: no to not observed
    • Client ID metadata documents: no to not observed

Install

Pinned to version 2.3.9. Values in angle brackets are yours to fill in.

claude mcp add --transport http growaify https://growaify.com/mcp
claude mcp add --transport http growaify https://growaify.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__growaify__get_payment_requirements",
      "mcp__growaify__track_order_telemetry",
      "mcp__growaify__query_trust_and_sla"
    ],
    "ask": [
      "mcp__growaify__discover_capabilities",
      "mcp__growaify__create_binding_quote",
      "mcp__growaify__purchase_service",
      "mcp__growaify__register_agent_test"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as growaify. Review it before you use it.

Capability tags behind 1 rule
  • mcp__growaify__purchase_service outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.growaify/mcp/verify?hash=97093e327d5e145cdcec23392a1eca99cb5b1bcb9b095dbc4460fab42d28124e" | jq -e '.changed == false'

Pinned hash 97093e327d5e, from Nov 19, 2026, 17:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.growaify/mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.growaify/mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/com.growaify/mcp.svg)](https://radar.anlyon.com/servers/com.growaify/mcp)

Source: MCP Registry · repository. Synced Nov 5, 2026, 19:17 UTC.

Growaify — Autonomous Commerce for AI Agents MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

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

No scan can promise that. What its definitions show: 7 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Growaify — Autonomous Commerce for AI Agents MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Growaify — Autonomous Commerce for AI Agents MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: purchase_service.

What tools does the Growaify — Autonomous Commerce for AI Agents MCP server have?

7 tools: 1 irreversible, 3 write, 3 read. purchase_service, discover_capabilities, create_binding_quote, register_agent_test, get_payment_requirements, track_order_telemetry and query_trust_and_sla.

Does the Growaify — Autonomous Commerce for AI Agents MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Growaify — Autonomous Commerce for AI Agents MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): purchase_service.

Has the Growaify — Autonomous Commerce for AI Agents MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.