Skip to main content
Glama

peerlytics

by xyz.peerlytics
OverviewDiscussionsAdmin

Server Details

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

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
20.2% over 37 days
Last Tested
Transport
Streamable HTTP
URL

TDQS

C2.8/5.0

Scored across 28 tools

Disambiguation3/5

Most get_* and list_* tools target distinct domain entities, but several high-level analytics endpoints overlap in purpose (get_analytics_summary, get_protocol_overview, get_market_summary, get_timeseries, get_leaderboard), and pairs like get_deposit/get_deposit_context and get_vault/get_vault_analytics create close boundaries. The descriptions clarify the differences, but an agent would need to read carefully to avoid misselection.

Naming Consistency5/5

The tool set follows a strong verb_noun pattern: get_ for single-entity or detail views, list_ for collections, plus explicit action endpoints like export_trade_log, plan_routes, and search_explorer. All names are snake_case and predictable, with no mixing of conventions.

Tool Count3/5

28 tools is on the heavy side for an MCP server, even for a broad analytics domain. Most tools map to real entities, but the surface is padded by overlapping summary/analytics endpoints and separate detail, context, and analytics variants for the same resources.

Completeness4/5

The server provides broad read-only coverage of the protocol domain: deposits, intents, makers, takers, vaults, delegates, verifiers, platforms, integrators, orderbook, routes, activity, and search. Minor gaps such as no list_vaults or list_integrators are workable via search/get endpoints, and mutating operations appear out of scope for an analytics-focused server.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updates
    • Changedget_orderbook2 fields changed
      • changedInput schema / properties / include_gated / description
        Previous value: -"Set to 1 to include group-gated deposits in the book, annotated per deposit with allowed_group_ids plus a top-level group_names map. Combined with taker, the payload adds taker_access (whitelisted deposit ids + group memberships) instead of scoping the book. Default (omitted) keeps the public-only book unchanged."New value: +"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-scoped taker_access instead of scoping the book. Default (omitted) keeps the public-only book unchanged."
      • changedInput schema / properties / taker / description
        Previous value: -"Optional taker wallet address. Scopes the book to deposits whitelisted for that taker; default orderbook results only include public liquidity."New value: +"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."
    • Changedplan_routes1 field changed
      • changedInput schema / properties / taker / description
        Previous value: -"Optional taker wallet address. Scopes the book to deposits whitelisted for that taker; generic take links are omitted for hooked private liquidity."New value: +"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 executable."
  2. 1 tool update
    • Addedexport_trade_log
  3. 1 tool update
    • Changedget_orderbook1 field changed
      • addedInput schema / properties / include_gated
        Added value: +{
+  "description": "Set to 1 to include group-gated deposits in the book, annotated per deposit with allowed_group_ids plus a top-level group_names map. Combined with taker, the payload adds taker_access (whitelisted deposit ids + group memberships) instead of scoping the book. Default (omitted) keeps the public-only book unchanged.",
+  "enum": [
+    "1",
+    "true"
+  ],
+  "type": "string"
+}
  4. 27 tool updates
    • First observedget_address
    • First observedget_analytics_summary
    • First observedget_delegate
    • First observedget_deposit
    • First observedget_deposit_context
    • First observedget_integrator
    • First observedget_intent
    • First observedget_leaderboard
    • First observedget_maker
    • First observedget_maker_history
    • First observedget_market_summary
    • First observedget_orderbook
    • First observedget_platform
    • First observedget_protocol_overview
    • First observedget_taker
    • First observedget_taker_history
    • First observedget_timeseries
    • First observedget_vault
    • First observedget_vault_analytics
    • First observedget_verifier
    • First observedlist_activity
    • First observedlist_currencies
    • First observedlist_deposits
    • First observedlist_intents
    • First observedlist_platforms
    • First observedplan_routes
    • First observedsearch_explorer

Related MCP Connectors

Related MCP Servers

Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources