Skip to content
External endpointresponds

peerlytics

ZKP2P analytics on Base: live orderbook, route planning, explorer, and protocol market data.

Endpoint URL
https://peerlytics.xyz/api/v1/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:06 AM UTC
Check
MCP initialize · 8s limit
Latency
122 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
xyz.peerlytics/peerlytics

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
peerlytics
Version
1.0.0
Capability keys
tools
Tool names
get_analytics_summary, get_protocol_overview, get_leaderboard, get_vault_analytics, get_timeseries, search_explorer, get_deposit, get_deposit_context, get_intent, get_address, get_maker, get_verifier, get_vault, get_taker, get_integrator, get_platform, get_delegate, list_deposits, list_intents, plan_routes, get_orderbook, get_market_summary, list_activity, list_platforms, list_currencies, get_maker_history, get_taker_history, export_trade_log
Instructions excerpt

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 }); follow its single, multi_intent, or partial allocation legs, then 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

Reported Aug 17, 2026, 05:06 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 142ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 137ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 145ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 122ms