MCP Server
The Zeodyn™ MCP server allows AI agents to interact with the Zeodyn platform natively via the Model Context Protocol. It exposes 8 tools over JSON-RPC 2.0, enabling agents to scan websites, monitor scores, compare competitors, and manage accounts — all without writing REST API integration code.
Endpoint
POST https://zeodyn.com/api/mcp
Content-Type: application/jsonTransport: Streamable HTTP (JSON-RPC 2.0 over POST). Rate limit: 60 requests per minute per IP.
Authentication
Most tools require authentication. Pass your API key via any of these methods (checked in order):
X-API-KeyheaderAuthorization: Bearer zd_live_xxxheaderapi_keyfield in the JSON-RPCparamsobject
Create an API key from your account settings. The get_plans tool does not require authentication.
Quick start
Initialise the connection
curl -X POST https://zeodyn.com/api/mcp \
-H "Content-Type: application/json" \
-H "X-API-Key: zd_live_xxxxx" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "initialize",
"params": {
"protocolVersion": "2025-03-26",
"clientInfo": { "name": "my-agent", "version": "1.0.0" },
"capabilities": {}
}
}'List available tools
curl -X POST https://zeodyn.com/api/mcp \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 2,
"method": "tools/list",
"params": {}
}'Call a tool
curl -X POST https://zeodyn.com/api/mcp \
-H "Content-Type: application/json" \
-H "X-API-Key: zd_live_xxxxx" \
-d '{
"jsonrpc": "2.0",
"id": 3,
"method": "tools/call",
"params": {
"name": "scan_website",
"arguments": { "url": "https://example.com" }
}
}'Available tools
The MCP server exposes 8 tools. Tools marked with Auth require a valid API key.
scan_websiteAuthScan a URL for AI agent commerce readiness
{ url: string }get_scan_resultsAuthRetrieve a scan result by ID
{ scan_id: string }list_scansAuthList your recent scans
{ limit?: number, offset?: number }get_plansList available pricing plans
{}get_accountAuthGet account info, tier, and usage
{}list_watched_sitesAuthList your watched sites
{}add_watched_siteAuthAdd a URL to your watchlist
{ url: string, label?: string }compare_sitesAuthCompare scores for multiple URLs
{ urls: string[] }JSON-RPC methods
| Method | Description |
|---|---|
| initialize | Handshake — returns server info and capabilities |
| tools/list | List all available tools with schemas |
| tools/call | Execute a tool with arguments |
| resources/list | List available resources |
| resources/read | Read a resource by URI |
Error codes
The server returns standard JSON-RPC 2.0 error codes:
| Code | Meaning |
|---|---|
| -32700 | Parse error — invalid JSON |
| -32600 | Invalid request — not a valid JSON-RPC 2.0 request |
| -32601 | Method not found |
| -32602 | Invalid params |
| -32603 | Internal error |
See also
- A2A endpoint — Natural language task interface for agent-to-agent interaction
- REST API — Traditional HTTP API with Bearer token authentication
- MCP specification — Official Model Context Protocol documentation