eCommerce
growaify.com
An MCP server for agentic commerce that discovers capabilities, generates binding quotes, places idempotent service orders, tracks deliverables, and inspects trust and SLA metadata.
ENDPOINT 1
https://growaify.com/mcp
MCP server metadata
- Name
- growaify
- Version
- 2.3.0
Growaify sells finished digital services and end-to-end bundles, delivered by automation rather than a project team. 32 services across 15 sectors (healthcare, hospitality, real estate, e-commerce, logistics, manufacturing, robotics and more), plus an importable n8n workflow library. Typical flow: discover_capabilities to find a service by requirement, create_binding_quote for a deterministic price valid 7 days, purchase_service to place an idempotent order, then track_order_telemetry for progress and the SHA-256 verified deliverable. query_trust_and_sla reports the refund policy, payment rails and checksum guarantees. FIRST: get a key in one call — POST https://growaify.com/api/v1/agents/register with {"name": "<your name>", "purpose": "<what you buy, 8+ chars>"}. No email, no human step: it returns an api_key immediately. Keep it, send it as the X-API-Key header on purchase_service. Check your profile and wallet any time at GET https://growaify.com/api/v1/agents/me. Catalog with agent pricing: https://growaify.com/store/catalog.json — public, no auth needed. Discovery and quoting are open. Payment settles via PayPal, x402 (USDC on Base) or Agent Wallet. Every order carries a 7-day money-back guarantee.
Known tools 5
create_binding_quoteGenerate a binding, deterministic quote with agent discount pricing and wholesale volume tiers.
Inferred read-onlytrack_order_telemetryQuery order state, execution progress (0-100%), and provisioned digital deliverables with SHA-256 checksums.
Inferred read-onlyquery_trust_and_slaInspect cryptographic checksum policy, refund policies, payment rails, and trust metadata for the platform.
Potential side effectsCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.growaify]
url = "https://growaify.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"growaify": {
"type": "http",
"url": "https://growaify.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: growaify
Remote MCP URL: https://growaify.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"growaify": {
"url": "https://growaify.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"growaify": {
"type": "http",
"url": "https://growaify.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "growaify",
"transport": "streamable-http",
"url": "https://growaify.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.