Peerlytics MCP server

Which MCP servers are Peerlytics's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-27

← Back to Peerlytics

Whose server it is

Registry namexyz.peerlytics/peerlyticsverified in the MCP registry

The registry name sits under peerlytics.xyz. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-27

Stateanswerschecked 2026-10-27
Tools2
Server calls itselfxyz.peerlytics/peerlytics
Server version1.1.0
Protocol version2025-06-18

On 2026-10-27 the server answered initialize and tools/list without a sign-in. First answer in 109 ms.

Should an agent connect itConnect it

Its tools do every use case we checked: Review recent peer protocol fills and seller rates; Check intent and deposit receipts for settlement evidence.

Once connected

For "Review recent peer protocol fills and seller rates", the likely first call is peerlytics_activity.
For "Check intent and deposit receipts for settlement evidence", the likely first call is peerlytics_receipt.
Parameters are untyped or undescribed in 2 of 2 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 8, the first on 2026-10-27

INITE MCP score96 of 100answers 100 · does the job 100 · definitions 83 · context 100 · connects 100
What an agent can do with it2 of 2 use cases
Answered100% of days8 of 8 daily checks
Median first answer144 ms
Space in an agent's context≈ 227 tokensthe definitions of all its tools (2), which an agent carries on every turn
Tool definitionsB · 83 of 100
Typed results0 of 2 toolsdeclared outputSchema: results come typed, read once

Parameters without a description: in 2 of 2

What an agent can do with it

can do · Review recent peer protocol fills and seller rates
can do · Check intent and deposit receipts for settlement evidence
not sure · Query public onchain activity from an AI assistant

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers2 tools · read 2026-10-27

peerlytics_activity
Read recent public Peer protocol activity on Base and open its interactive receipt desk. Returns a bounded latest sample, never all-time totals.
peerlytics_receipt
Look up a public intent hash or chain-qualified deposit identifier. Preserves indexed settlement evidence, timestamps and provenance; never initiates a financial action or returns payee or payment identifiers.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "peerlytics": {
      "type": "http",
      "url": "https://peerlytics.xyz/api/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http peerlytics https://peerlytics.xyz/api/mcp

Add to Cursor Add to VS Code

claude.ai, ChatGPT and other clients: add https://peerlytics.xyz/api/mcp as a custom connector in the settings.

Other servers listed as Peerlytics's

xyz.peerlytics/peerlytics-dataanswers, 3 toolsverified in the MCP registry

OpenAPI spec

10 paths, read 2026-10-27. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.