Peering MCP server
io.github.LeonardMichalas/peering-mcp·v0.1.1Who peers with whom, where they meet, and who an address range belongs to. PeeringDB and RDAP.
0 stars35 downloads/wk
Reviews
Write oneNobody has reviewed Peering yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Peering tools (5)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
find_at_exchangeList the networks present at one internet exchange.
find_common_presenceFind the internet exchanges and facilities several networks all share.
list_presenceList the internet exchanges and facilities one network is present at.
lookup_networkLook up a network on the internet by AS number or by name.
lookup_registrationLook up who an IP address, a prefix or an AS number is registered to.
Public scan report
scanner v0.1.10 · 2026-10-14 · same rubric, same numbers if you re-run it
- Code scan25 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 25 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Peering compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 83/100
- higher than 65% of 48,243 servers
- Tools
- 5
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Downloads a week
- 35
- more than 24% of 12,306 servers with a package
What its tools let an agent do: 5 read
Release history: 2 versions in the registry since 2026-09-19, latest 2026-09-19, typically several a day.
Install Peering in Claude Code, Cursor or VS Code
claude mcp add peering-mcp -- uvx peering-mcp
What the publisher says
From the Peering repository's README, as published. We do not edit it. Read it on GitHub
peering-mcp
<!-- mcp-name: io.github.LeonardMichalas/peering-mcp -->
An MCP server that lets an AI agent look up how the internet is actually wired together — which networks connect to each other, at which internet exchanges and facilities, under what peering policy, and who a given address range is registered to.
Five read-only tools over two public sources: PeeringDB for interconnection, and the regional internet registries over RDAP for registration. Upstream responses are validated and shaped, free text is stripped of structure before it reaches a model, requests are rate limited to what PeeringDB asks for, and answers are cached on disk between runs. Every response is held to a byte budget.
Install it with uvx peering-mcp. A personal project, MIT licensed.
Why this exists
The internet is roughly eighty thousand independent networks that agree to carry each other's traffic. Which networks connect to which, where they meet, and on what terms is public, free and well structured — published through stable APIs by PeeringDB and the regional internet registries.
None of it is reachable by an AI agent. Ask a coding assistant which internet exchanges a given carrier is present at and it will answer from memory: fluent, confident, and often wrong. It has no way to check, so it does not check.
This server is that way to check.
What it does
findcommonpresence is the tool that motivated the project. Working out where two or more networks could interconnect means looking each one up, listing everywhere it is present, and intersecting the results by hand. That is about an hour and a dozen browser tabs. It should be one question.
It takes two to five AS numbers and answers in four requests, whatever the number of networks. Shared exchanges come back widest bottleneck first — ordered by the smallest capacity any one network has there, because that is what a connection between them would be limited by.
It also returns how many locations each network has on its own, so an empty answer is explainable: either the networks genuinely do not overlap, or one of them has no records at all, which is a very different thing.
findatexchange asks it the other way round: who is already at DE-CIX Frankfurt, and which of them will peer with anyone. It takes an exchange name or its PeeringDB id, optionally keeps only the networks stating one peering policy, and returns them largest capacity first. A name matching several exchanges — ten of them are called LINX, on four continents — comes back as candidates to choose between, never a guess at which one was meant.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Peering: common questions
- Is Peering MCP server safe?
- Mostly: it is graded B (83/100). Read the Peering safety report
- How do I install Peering?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Peering need an API key?
- Yes. The registry entry asks for
PEERINGDB_API_KEY. - Is Peering maintained?
- The last commit was 47 days ago (2026-09-19). The latest release is v0.1.1.
- How does Peering compare with other MCP servers?
- safety score 83/100 (higher than 65% of 48,243 servers); tools 5 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.