ENDPOINT 1
https://peerlytics.xyz/api/v1/mcp
MCP server metadata
- Name
- peerlytics
- Version
- 1.0.0
Peerlytics is the analytics, explorer, and market-data surface for the ZKP2P peer-to-peer USDC-to-fiat protocol on Base. Start buyer flows with plan_routes({ currency, amount_usd }); drop to get_orderbook when you need the raw book. Never surface a take action unless the payload exposes one — private whitelist-hooked liquidity is not publicly fillable. Authentication: send an x-api-key header (free key: https://peerlytics.xyz/developers?tab=account) or pay per call with x402. Unauthenticated tool calls return a 402 payload with self-onboarding links. Machine docs: https://peerlytics.xyz/llms.txt
Known tools 27
CONNECT 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.peerlytics]
url = "https://peerlytics.xyz/api/v1/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"peerlytics": {
"type": "http",
"url": "https://peerlytics.xyz/api/v1/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: peerlytics
Remote MCP URL: https://peerlytics.xyz/api/v1/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": {
"peerlytics": {
"url": "https://peerlytics.xyz/api/v1/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"peerlytics": {
"type": "http",
"url": "https://peerlytics.xyz/api/v1/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "peerlytics",
"transport": "streamable-http",
"url": "https://peerlytics.xyz/api/v1/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.