xyz.peerlytics/peerlytics
REMOTE · PEERLYTICS.XYZ · SCANNED SEP 21
ZKP2P analytics on Base: live orderbook, route planning, explorer, and protocol market data.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 404. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the xyz.peerlytics/peerlytics MCP server?
xyz.peerlytics/peerlytics is a hosted endpoint at https://peerlytics.xyz/api/v1/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · peerlytics.xyz
claude mcp add --transport http xyz-peerlytics-peerlytics 'https://peerlytics.xyz/api/v1/mcp'
{
"mcpServers": {
"xyz-peerlytics-peerlytics": {
"url": "https://peerlytics.xyz/api/v1/mcp"
}
}
} {
"servers": {
"xyz-peerlytics-peerlytics": {
"type": "http",
"url": "https://peerlytics.xyz/api/v1/mcp"
}
}
} [mcp_servers.xyz-peerlytics-peerlytics] url = "https://peerlytics.xyz/api/v1/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"xyz-peerlytics-peerlytics": {
"type": "remote",
"url": "https://peerlytics.xyz/api/v1/mcp",
"enabled": true
}
}
} openclaw mcp add xyz-peerlytics-peerlytics --url 'https://peerlytics.xyz/api/v1/mcp' --transport streamable-http
mcp_servers:
xyz-peerlytics-peerlytics:
url: "https://peerlytics.xyz/api/v1/mcp" {
"McpServers": {
"xyz-peerlytics-peerlytics": {
"Transport": "http",
"Url": "https://peerlytics.xyz/api/v1/mcp"
}
}
} assistant mcp add xyz-peerlytics-peerlytics -t streamable-http -u 'https://peerlytics.xyz/api/v1/mcp'
{
"mcpServers": {
"xyz-peerlytics-peerlytics": {
"type": "http",
"url": "https://peerlytics.xyz/api/v1/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Sept 26 −50
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 29 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “export_trade_log” rewrote its description, which is the text the model reads security
- Tool “plan_routes” rewrote its description, which is the text the model reads security
- “get_orderbook” reworded the description of “include_gated” cosmetic
- “get_orderbook” reworded the description of “taker” cosmetic
- “plan_routes” reworded the description of “taker” cosmetic
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 14 Aug 26 0
- Tool “list_deposits” rewrote its description, which is the text the model reads security
- Tool “list_intents” rewrote its description, which is the text the model reads security
- 13 Aug 26 0
- New tool “export_trade_log” functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 8 Aug 26 0
- “get_orderbook” added an optional parameter “include_gated” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Probed https://peerlytics.xyz/api/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=peerlytics.xyz | CN=WR3,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | RSA 2048 | SHA256-RSA | c507f3c1c7112bc60a6fd49626e94306 |
| SANs: peerlytics.xyz, *.peerlytics.xyz | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of peerlytics.xyz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | present | 3599, 18130 | 8, 8 | Verified |
| peerlytics.xyz. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 404 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://peerlytics.xyz/api/v1/mcp | HTTP error | 404 | |
| http (plaintext) | http://peerlytics.xyz/api/v1/mcp | HTTPS enforced | 301 | https://peerlytics.xyz:443/api/v1/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
export_trade_log ~196
Export wallet transaction events. API-key-only, 2,500-credit export of the canonical role-aware transaction classifier. `format=csv` (default) returns a cached signed download URL for up to 366 days. `format=json` returns inline `peerlytics.transaction-events.v2` data for up to 31 days. Stable event ids, classifications, signed USDC amounts, fiat values, role, counterparty, references, attribution, and flags are shared across both formats. x402 is not supported.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Delivery format. JSON is inline and capped at 31 days. |
| from | – | yes | Inclusive UTC range start. Date-only input opens at 00:00:00.000. |
| to | – | yes | Inclusive UTC range end. Date-only input closes at 23:59:59.999. |
| wallet | string | yes | Wallet to classify as maker, taker, or self. |
No output schema declared.
No examples provided.
get_address ~104
Unified address stats
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| cursor | string | – | Pass the previous page's `next_cursor` to walk forward without offset drift. This is the supported pagination path on every list endpoint. |
| limit | integer | – | Max results to return (default: 100). |
| offset | integer | – | Deprecated. Use `cursor` instead — offset pagination is fragile under concurrent writes and slow at scale. Still accepted for backwards compatibility while integrators migrate. |
No output schema declared.
No examples provided.
get_analytics_summary ~275
Investor summary metrics. Without params: cumulative MTD/QTD/YTD/all-time summary buckets. With `from`/`to`/`range`: returns a windowed `{ window, summary, composition, comparison }` payload computed live from the indexer. Optional `compare=prior_period|prior_year` adds a delta block. Hard cap: 400-day window.
| Name | Type | Req | Description |
|---|---|---|---|
| compare | string | – | Adds a `comparison` block computed against the prior period (same length, immediately preceding) or the prior year (shifted back 365 days). |
| from | string | – | Window lower bound (inclusive). ISO-8601 (`2026-04-01T00:00:00Z`) or unix-seconds. Optional when `range` is supplied. |
| range | string | – | Unified date-range shortcut shared across analytics + explorer endpoints. Hard cap: 400-day window. When set, takes precedence over `from`/`to`. Legacy values (`3mtd`, `q1`-`q4`, `custom`) were retir… |
| to | string | – | Window upper bound (exclusive). ISO-8601 or unix-seconds. Defaults to `now` when omitted but `from` is supplied. |
No output schema declared.
No examples provided.
get_delegate ~41
Delegate view. Deposits delegated to this address, liquidity under management, rate managers, success rate, and a full deposit list.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
No output schema declared.
No examples provided.
get_deposit ~104
Deposit detail
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Pass the previous page's `next_cursor` to walk forward without offset drift. This is the supported pagination path on every list endpoint. |
| id | string | yes | – |
| limit | integer | – | Max intents to return (default: 100). |
| offset | integer | – | Deprecated. Use `cursor` instead — offset pagination is fragile under concurrent writes and slow at scale. Still accepted for backwards compatibility while integrators migrate. |
No output schema declared.
No examples provided.
get_deposit_context ~49
Deposit agent context. Compact deposit workbench context for agents and integrators: route facts, trust signals, and next-action links without loading the full explorer payload.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_integrator ~93
Integrator view (ERC-8021 attribution). Aggregated activity for an ERC-8021 integrator code: deposits created, intents, volume, top makers, top markets, daily activity. Resolves attribution from calldata. Window is fixed at 90 days because that is the only window currently materialized — the legacy `windowDays` parameter (single-value enum) was retired.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | – |
No output schema declared.
No examples provided.
get_intent ~19
Intent detail
| Name | Type | Req | Description |
|---|---|---|---|
| hash | string | yes | – |
No output schema declared.
No examples provided.
get_leaderboard ~297
Maker/taker leaderboard. Without params: cumulative leaderboard backed by MakerStats/TakerStats. With `from`/`to`/`range`: per-window indexer compute. Hard cap: 400-day window.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Pass the previous page's `next_cursor` to walk forward without offset drift. This is the supported pagination path on every list endpoint. |
| from | string | – | Window lower bound (inclusive). ISO-8601 (`2026-04-01T00:00:00Z`) or unix-seconds. Optional when `range` is supplied. |
| limit | integer | – | Max results per list (default: 20, max: 100). |
| offset | integer | – | Deprecated. Use `cursor` instead — offset pagination is fragile under concurrent writes and slow at scale. Still accepted for backwards compatibility while integrators migrate. |
| range | string | – | Unified date-range shortcut shared across analytics + explorer endpoints. Hard cap: 400-day window. When set, takes precedence over `from`/`to`. Legacy values (`3mtd`, `q1`-`q4`, `custom`) were retir… |
| to | string | – | Window upper bound (exclusive). ISO-8601 or unix-seconds. Defaults to `now` when omitted but `from` is supplied. |
No output schema declared.
No examples provided.
get_maker ~19
Maker portfolio
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
No output schema declared.
No examples provided.
get_maker_history ~295
Maker history metrics. Without window params: lifetime aggregates and a `recent` window of 30 newest intents. With `from`/`to`/`range`: every metric recomputes for the period.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| cursor | string | – | Pass the previous page's `next_cursor` to walk forward without offset drift. This is the supported pagination path on every list endpoint. |
| from | string | – | Window lower bound (inclusive). ISO-8601 (`2026-04-01T00:00:00Z`) or unix-seconds. Optional when `range` is supplied. |
| limit | integer | – | Max number of results to return. |
| offset | integer | – | Deprecated. Use `cursor` instead — offset pagination is fragile under concurrent writes and slow at scale. Still accepted for backwards compatibility while integrators migrate. |
| range | string | – | Unified date-range shortcut shared across analytics + explorer endpoints. Hard cap: 400-day window. When set, takes precedence over `from`/`to`. Legacy values (`3mtd`, `q1`-`q4`, `custom`) were retir… |
| to | string | – | Window upper bound (exclusive). ISO-8601 or unix-seconds. Defaults to `now` when omitted but `from` is supplied. |
No output schema declared.
No examples provided.
get_market_summary ~149
Market intelligence snapshot
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | Repeatable or comma-separated currency codes. |
| cursor | string | – | Pass the previous page's `next_cursor` to walk forward without offset drift. This is the supported pagination path on every list endpoint. |
| include_rates | boolean | – | Include individual rate entries. |
| limit | integer | – | Max results to return (default: 200, max: 500). |
| offset | integer | – | Deprecated. Use `cursor` instead — offset pagination is fragile under concurrent writes and slow at scale. Still accepted for backwards compatibility while integrators migrate. |
| platform | string | – | Repeatable or comma-separated platform ids (analytics treats as verifier alias). |
No output schema declared.
No examples provided.
get_orderbook ~226
Network orderbook. Full orderbook with rate levels, exact per-deposit availability, intent bounds and payment pairs, 24h activity, global stats, FX mid-rates, and DRM-aware metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | Filter by fiat currency code (e.g. USD, GBP, EUR). Without filter, returns top 6 currencies by liquidity. |
| include_gated | string | – | Set to 1 to include restricted deposits in the book. Payment pairs report whether every taker can use the tuple; protected tuples may still require stake. Combined with taker, the payload adds method… |
| min_size | number | – | Minimum USD liquidity per orderbook level (default: 50). |
| platform | string | – | Filter by payment platform. |
| taker | string | – | Optional taker wallet address. Without include_gated, returns only restricted deposit/payment-method tuples that wallet can access. Default results without a taker include public liquidity only. |
No output schema declared.
No examples provided.
get_platform ~63
Payment platform view. Deposits, unique makers, unique takers, fulfilled intents, volume, and currency breakdown for a payment platform.
| Name | Type | Req | Description |
|---|---|---|---|
| platform | string | yes | – |
| window_days | integer | – | Lookback window in days (default 90, max 365). |
No output schema declared.
No examples provided.
get_protocol_overview ~233
Investor diligence overview. Investor-focused protocol diligence payload. Pass a `range` shortcut for cached buckets (`mtd`/`ytd`/`all`) or a non-default shortcut (`last_7d`, `qtd`, ..) for a live windowed compute. Includes growth, throughput, liquidity quality, concentration, and protocol mix.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Window lower bound (inclusive). ISO-8601 (`2026-04-01T00:00:00Z`) or unix-seconds. Optional when `range` is supplied. |
| range | string | – | Unified date-range shortcut shared across analytics + explorer endpoints. Hard cap: 400-day window. When set, takes precedence over `from`/`to`. Legacy values (`3mtd`, `q1`-`q4`, `custom`) were retir… |
| to | string | – | Window upper bound (exclusive). ISO-8601 or unix-seconds. Defaults to `now` when omitted but `from` is supplied. |
No output schema declared.
No examples provided.
get_taker ~43
Taker portfolio. Volume bought, fulfilled intents, currency and platform allocations, daily activity, and recent intents for a taker wallet.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
No output schema declared.
No examples provided.
get_taker_history ~307
Taker history metrics. Same window/pagination semantics as `/api/v1/makers/{address}/history`. Within a window `intents.{total,fulfilled,pruned,volume_usd}` reflect the period only; cumulative responses fall back to lifetime TakerStats.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| cursor | string | – | Pass the previous page's `next_cursor` to walk forward without offset drift. This is the supported pagination path on every list endpoint. |
| from | string | – | Window lower bound (inclusive). ISO-8601 (`2026-04-01T00:00:00Z`) or unix-seconds. Optional when `range` is supplied. |
| limit | integer | – | Max number of results to return. |
| offset | integer | – | Deprecated. Use `cursor` instead — offset pagination is fragile under concurrent writes and slow at scale. Still accepted for backwards compatibility while integrators migrate. |
| range | string | – | Unified date-range shortcut shared across analytics + explorer endpoints. Hard cap: 400-day window. When set, takes precedence over `from`/`to`. Legacy values (`3mtd`, `q1`-`q4`, `custom`) were retir… |
| to | string | – | Window upper bound (exclusive). ISO-8601 or unix-seconds. Defaults to `now` when omitted but `from` is supplied. |
No output schema declared.
No examples provided.
get_timeseries ~356
Historical time-series. Hour or day buckets of deposits created, intents signaled, or fulfilled volume. 60 credits per call. Pass `group_by=platform|currency|maker|verifier` to receive a multi-series payload (`series[]`) instead of a single global `buckets` array.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | Repeatable or comma-separated currency codes. |
| entity | string | yes | Which series to aggregate. |
| from | string | – | Window lower bound (inclusive). ISO-8601 (`2026-04-01T00:00:00Z`) or unix-seconds. Optional when `range` is supplied. |
| granularity | string | – | Bucket size (default: day). |
| group_by | string | – | Multi-series grouping. When set, the response returns `series[]` (up to 25 keys ordered by total value) instead of a single `buckets` array. |
| maker | string | – | Repeatable or comma-separated maker (depositor) addresses. |
| platform | string | – | Repeatable or comma-separated platform ids (analytics treats as verifier alias). |
| range | string | – | Unified date-range shortcut shared across analytics + explorer endpoints. Hard cap: 400-day window. When set, takes precedence over `from`/`to`. Legacy values (`3mtd`, `q1`-`q4`, `custom`) were retir… |
| to | string | – | Window upper bound (exclusive). ISO-8601 or unix-seconds. Defaults to `now` when omitted but `from` is supplied. |
| verifier | string | – | Repeatable or comma-separated verifier addresses. |
No output schema declared.
No examples provided.
get_vault ~75
Vault detail, delegated deposits, and config. Detailed rate-manager explorer view with delegated deposits, oracle configs, floor configs, and historical snapshots. Supports API key auth and x402.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Number of snapshot days to return (default: 30, max: 365). |
| id | string | yes | – |
No output schema declared.
No examples provided.
get_vault_analytics ~259
Vault and delegated liquidity overview. Without params: cumulative rate-manager analytics including delegated AUM, delegation adoption, fee volume, daily AUM/fee series, and per-vault summaries. With `from`/`to`/`range`: per-vault rollup (`fees_earned_usd`, `volume_routed_usd`, `aum_change_usd`, `delegator_change`) computed from daily snapshots inside the window. Supports API key auth and x402.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Window lower bound (inclusive). ISO-8601 (`2026-04-01T00:00:00Z`) or unix-seconds. Optional when `range` is supplied. |
| range | string | – | Unified date-range shortcut shared across analytics + explorer endpoints. Hard cap: 400-day window. When set, takes precedence over `from`/`to`. Legacy values (`3mtd`, `q1`-`q4`, `custom`) were retir… |
| to | string | – | Window upper bound (exclusive). ISO-8601 or unix-seconds. Defaults to `now` when omitted but `from` is supplied. |
No output schema declared.
No examples provided.
get_verifier ~105
Verifier stats
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| cursor | string | – | Pass the previous page's `next_cursor` to walk forward without offset drift. This is the supported pagination path on every list endpoint. |
| limit | integer | – | Max results to return (default: 50). |
| offset | integer | – | Deprecated. Use `cursor` instead — offset pagination is fragile under concurrent writes and slow at scale. Still accepted for backwards compatibility while integrators migrate. |
No output schema declared.
No examples provided.
list_activity ~355
Protocol activity feed. Recent protocol events. Pass `since` (lower bound) and `to` (upper bound) for an explicit window, or `range` for a shortcut. The response includes `next_cursor` whenever `has_more=true`; pass it back as `cursor` to walk older events without offset drift.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Filter by any address involved |
| cursor | string | – | Pass the previous page's `next_cursor` to walk forward without offset drift. This is the supported pagination path on every list endpoint. |
| deposit_id | string | – | – |
| depositor | string | – | – |
| intent_hash | string | – | – |
| limit | integer | – | Max number of results to return. |
| offset | integer | – | Deprecated. Use `cursor` instead — offset pagination is fragile under concurrent writes and slow at scale. Still accepted for backwards compatibility while integrators migrate. |
| range | string | – | Unified date-range shortcut shared across analytics + explorer endpoints. Hard cap: 400-day window. When set, takes precedence over `from`/`to`. Legacy values (`3mtd`, `q1`-`q4`, `custom`) were retir… |
| recipient | string | – | – |
| since | string | – | Lower bound for event timestamps (unix seconds, ms, or ISO). Replaces the legacy `after` alias. |
| taker | string | – | – |
| to | string | – | Window upper bound (exclusive). ISO-8601 or unix-seconds. Defaults to `now` when omitted but `from` is supplied. |
| type | string | – | Repeatable event types |
No output schema declared.
No examples provided.
list_currencies ~13
Supported currencies metadata
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_deposits ~483
Filtered deposit list. Deposit search. Filters are optional; an empty query returns a bounded page (default `limit=50`, max 200). Optional filters: `depositor`, `delegate`, `platform`, `currency`, and/or a date window (`from`/`to`/`range`). When a window is supplied the server filters on deposit creation `timestamp` and the response echoes a `window` block. Market rows include DRM and oracle pricing fields (`manager_rate`, `manager_fee`, `rate_source`, `rate_manager_id`, `oracle_rate`, `effective_oracle_rate`, `adapter`, `kind`, `is_oracle_backed`, `oracle_source`, `spread_bps`, `is_delegated`).
| Name | Type | Req | Description |
|---|---|---|---|
| accepting | boolean | – | Filter by accepting intents. |
| currency | string | – | Repeatable or comma-separated currency codes. |
| cursor | string | – | Pass the previous page's `next_cursor` to walk forward without offset drift. This is the supported pagination path on every list endpoint. |
| delegate | string | – | Delegate address. |
| depositor | string | – | Maker address. |
| from | string | – | Window lower bound (inclusive). ISO-8601 (`2026-04-01T00:00:00Z`) or unix-seconds. Optional when `range` is supplied. |
| limit | integer | – | Max number of results to return. |
| offset | integer | – | Deprecated. Use `cursor` instead — offset pagination is fragile under concurrent writes and slow at scale. Still accepted for backwards compatibility while integrators migrate. |
| platform | string | – | Repeatable or comma-separated platform ids (analytics treats as verifier alias). |
| range | string | – | Unified date-range shortcut shared across analytics + explorer endpoints. Hard cap: 400-day window. When set, takes precedence over `from`/`to`. Legacy values (`3mtd`, `q1`-`q4`, `custom`) were retir… |
| sort | string | – | Sort direction by canonical timestamp. Default: `desc`. |
| status | string | – | – |
| to | string | – | Window upper bound (exclusive). ISO-8601 or unix-seconds. Defaults to `now` when omitted but `from` is supplied. |
No output schema declared.
No examples provided.
list_intents ~454
Filtered intent list. Intent search. Filters are optional; an empty query returns a bounded page (default `limit=50`, max 200). Optional filters: `taker`, `recipient`, `verifier`, `deposit_id`, `status`, and/or a date window (`from`/`to`/`range`). Default sort is `signal_timestamp desc`. The legacy aliases (`owner` for `taker`, `to_address` for `recipient`) were retired on 2026-04-30 — use the canonical names.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Pass the previous page's `next_cursor` to walk forward without offset drift. This is the supported pagination path on every list endpoint. |
| deposit_id | string | – | Repeatable or comma-separated deposit IDs. |
| from | string | – | Window lower bound (inclusive). ISO-8601 (`2026-04-01T00:00:00Z`) or unix-seconds. Optional when `range` is supplied. |
| limit | integer | – | Max number of results to return. |
| offset | integer | – | Deprecated. Use `cursor` instead — offset pagination is fragile under concurrent writes and slow at scale. Still accepted for backwards compatibility while integrators migrate. |
| range | string | – | Unified date-range shortcut shared across analytics + explorer endpoints. Hard cap: 400-day window. When set, takes precedence over `from`/`to`. Legacy values (`3mtd`, `q1`-`q4`, `custom`) were retir… |
| recipient | string | – | Recipient address (replaces the legacy `to_address` alias). |
| sort | string | – | Sort direction by canonical timestamp. Default: `desc`. |
| status | string | – | Repeatable or comma-separated. Accepts fulfilled/completed/pruned/signaled. |
| taker | string | – | Taker address (replaces the legacy `owner` alias). |
| to | string | – | Window upper bound (exclusive). ISO-8601 or unix-seconds. Defaults to `now` when omitted but `from` is supplied. |
| verifier | string | – | – |
No output schema declared.
No examples provided.
list_platforms ~13
Payment platforms metadata
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
plan_routes ~244
Plan best routes. Ranks visible orderbook routes for a requested USDC amount using exact per-deposit availability and intent bounds. Returns deterministic single, multi_intent, or partial allocation legs. A generic take link exists only for a currently executable single leg and preserves the requested amount and payment pair. Single-leg routes include exact-pair trailing-30-day execution evidence. Historical execution evidence does not influence ranking until separately backtested and enabled.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_usd | number | – | Requested USDC amount. Routes that can fill the amount rank above partial routes. |
| currency | string | – | Filter by fiat currency code (e.g. USD, GBP, EUR). |
| limit | integer | – | Maximum planned routes to return (default: 5, max: 25). |
| min_size | number | – | Minimum USD liquidity per orderbook level (default: 50). |
| platform | string | – | Filter by payment platform. May be repeated. |
| taker | string | – | Optional taker wallet address. Scopes routes to exact payment-method access available to that wallet. Access-policy provenance is omitted, and a take link is present only when the selected tuple is e… |
No output schema declared.
No examples provided.
search_explorer ~141
Search intents, deposits, or addresses
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Pass the previous page's `next_cursor` to walk forward without offset drift. This is the supported pagination path on every list endpoint. |
| limit | integer | – | Max number of results to return. |
| offset | integer | – | Deprecated. Use `cursor` instead — offset pagination is fragile under concurrent writes and slow at scale. Still accepted for backwards compatibility while integrators migrate. |
| q | string | yes | – |
| role | string | – | Optional role filter: taker, recipient, verifier. |
| type | string | – | Optional override: tx_or_hash, address, deposit_id. |
No output schema declared.
No examples provided.
What is the xyz.peerlytics/peerlytics MCP server?
xyz.peerlytics/peerlytics is an MCP server listed in the public MCP registry as xyz.peerlytics/peerlytics. ZKP2P analytics on Base: live orderbook, route planning, explorer, and protocol market data. This page covers its hosted endpoint (https://peerlytics.xyz/api/v1/mcp).
Is the xyz.peerlytics/peerlytics MCP server safe to use?
xyz.peerlytics/peerlytics scores 25 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the xyz.peerlytics/peerlytics MCP server expose?
xyz.peerlytics/peerlytics exposes 28 tools: get_analytics_summary, get_protocol_overview, get_leaderboard, get_vault_analytics, get_timeseries, and 23 more. Their descriptions and schemas cost roughly 5,011 tokens of context every time the server is loaded.
Does the xyz.peerlytics/peerlytics MCP server require authentication?
No. We connected to xyz.peerlytics/peerlytics without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the xyz.peerlytics/peerlytics MCP server still maintained?
xyz.peerlytics/peerlytics is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.