Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

Peering MCP

by LeonardMichalasversion 0.1.1i★ 0iRuns on your computerRepository ↗
Registry nameio.github.LeonardMichalas/peering-mcp

How to install

What it does

Who peers with whom, where they meet, and who an address range belongs to. PeeringDB and RDAP.

  • Connects Runs on your computer
  • Account or key Needs PEERINGDB_API_KEY
  • Category Other

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity0/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness7/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score7/100

Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Let your AI install it with one sentence

Please install Peering MCP. Follow https://mcp.popnx.com/i/leonardmichalas-peering-mcp.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude, with some setup first

You need a Peering MCP key (create it on the maker’s site) · Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

Let AI install it

Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Peering MCP for Claude on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "peering": { "command": "uvx", "args": [ "peering-mcp" ], "env": { "PEERINGDB_API_KEY": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For PEERINGDB_API_KEY, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Peering MCP tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install uv (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    uv --version
    • A version number such as uv … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required

    Open the uv download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version

    Install once; it works for everything that needs uv

  2. Sign up and create a Peering MCP key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Peering MCP site ↗

  3. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  4. Paste these settings and save the file

    {
      "mcpServers": {
        "peering": {
          "command": "uvx",
          "args": [
            "peering-mcp"
          ],
          "env": {
            "PEERINGDB_API_KEY": "your-value"
          }
        }
      }
    }

    Paste the key only into the app’s field, never into a chat or to anyone

  5. Quit Claude and open it again

  6. Try it

    Use Peering MCP and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using Peering MCP or shows a Peering MCP tool in the answer, you are connected

5 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • PEERING_MCP_CACHE_TTL How long a cached upstream response stays usable, in seconds. · default 86400
  • PEERING_MCP_CACHE_DIR Where the on-disk cache lives. Defaults to $XDG_CACHE_HOME/peering-mcp.
  • PEERING_MCP_NO_CACHE Set to 1 to disable caching. Slower, and harder on the upstream APIs.
  • PEERING_MCP_TIMEOUT Per-request timeout in seconds. · default 10
  • PEERING_MCP_MAX_RETRIES Attempts before an upstream failure is reported. · default 3

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect Peering MCP yet

Peering MCP runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect Peering MCP

  • You need a Peering MCP key (create it on the maker’s site) · Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
  • You need a Peering MCP key (create it on the maker’s site) · Install Python (uv) on your computer first (one time)
  • You need a Peering MCP key (create it on the maker’s site) · Install Python (uv) on your computer first (one time)
  • You need a Peering MCP key (create it on the maker’s site) · Install Python (uv) on your computer first (one time)

B · Others in Other that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Works with Claude Code, with some setup first

You need a Peering MCP key (create it on the maker’s site) · Install Python (uv) on your computer first (one time)

Let AI install it

Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Peering MCP for Claude Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user peering --env PEERINGDB_API_KEY=your-value -- uvx peering-mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For PEERINGDB_API_KEY, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Peering MCP tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install uv (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    uv --version
    • A version number such as uv … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required

    Open the uv download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version

    Install once; it works for everything that needs uv

  2. Sign up and create a Peering MCP key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Peering MCP site ↗

  3. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  4. Paste this command and press Enter

    claude mcp add --scope user peering --env PEERINGDB_API_KEY=your-value -- uvx peering-mcp

    Replace “your-value” with your key before pressing Enter

    Paste the key only into the app’s field, never into a chat or to anyone

  5. Type /mcp in Claude Code

    You should see Peering MCP listed as connected

  6. Try it

    Use Peering MCP and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using Peering MCP or shows a Peering MCP tool in the answer, you are connected

5 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • PEERING_MCP_CACHE_TTL How long a cached upstream response stays usable, in seconds. · default 86400
  • PEERING_MCP_CACHE_DIR Where the on-disk cache lives. Defaults to $XDG_CACHE_HOME/peering-mcp.
  • PEERING_MCP_NO_CACHE Set to 1 to disable caching. Slower, and harder on the upstream APIs.
  • PEERING_MCP_TIMEOUT Per-request timeout in seconds. · default 10
  • PEERING_MCP_MAX_RETRIES Attempts before an upstream failure is reported. · default 3

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

You need a Peering MCP key (create it on the maker’s site) · Install Python (uv) on your computer first (one time)

Let AI install it

Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Peering MCP for Cursor on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "peering": { "command": "uvx", "args": [ "peering-mcp" ], "env": { "PEERINGDB_API_KEY": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For PEERINGDB_API_KEY, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Peering MCP tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install uv (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    uv --version
    • A version number such as uv … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required

    Open the uv download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version

    Install once; it works for everything that needs uv

  2. Sign up and create a Peering MCP key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Peering MCP site ↗

  3. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  4. Fill in your key

    In the Peering MCP settings, PEERINGDB_API_KEY is empty; add your key and save

    Paste the key only into the app’s field, never into a chat or to anyone

  5. Open the AI chat in Cursor in Agent mode

  6. Try it

    Use Peering MCP and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using Peering MCP or shows a Peering MCP tool in the answer, you are connected

5 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • PEERING_MCP_CACHE_TTL How long a cached upstream response stays usable, in seconds. · default 86400
  • PEERING_MCP_CACHE_DIR Where the on-disk cache lives. Defaults to $XDG_CACHE_HOME/peering-mcp.
  • PEERING_MCP_NO_CACHE Set to 1 to disable caching. Slower, and harder on the upstream APIs.
  • PEERING_MCP_TIMEOUT Per-request timeout in seconds. · default 10
  • PEERING_MCP_MAX_RETRIES Attempts before an upstream failure is reported. · default 3

Descriptions are as written by the maker.

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

You need a Peering MCP key (create it on the maker’s site) · Install Python (uv) on your computer first (one time)

Let AI install it

Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Peering MCP for VS Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "peering": { "type": "stdio", "command": "uvx", "args": [ "peering-mcp" ], "env": { "PEERINGDB_API_KEY": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For PEERINGDB_API_KEY, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Peering MCP tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install uv (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    uv --version
    • A version number such as uv … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required

    Open the uv download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version

    Install once; it works for everything that needs uv

  2. Sign up and create a Peering MCP key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Peering MCP site ↗

  3. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  4. Fill in your key

    In the Peering MCP settings, PEERINGDB_API_KEY is empty; add your key and save

    Paste the key only into the app’s field, never into a chat or to anyone

  5. Open the AI chat in VS Code in Agent mode

  6. Try it

    Use Peering MCP and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using Peering MCP or shows a Peering MCP tool in the answer, you are connected

5 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • PEERING_MCP_CACHE_TTL How long a cached upstream response stays usable, in seconds. · default 86400
  • PEERING_MCP_CACHE_DIR Where the on-disk cache lives. Defaults to $XDG_CACHE_HOME/peering-mcp.
  • PEERING_MCP_NO_CACHE Set to 1 to disable caching. Slower, and harder on the upstream APIs.
  • PEERING_MCP_TIMEOUT Per-request timeout in seconds. · default 10
  • PEERING_MCP_MAX_RETRIES Attempts before an upstream failure is reported. · default 3

Descriptions are as written by the maker.

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use Peering MCP💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user peering --env PEERINGDB_API_KEY=your-value -- uvx peering-mcp

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "peering": {
      "command": "uvx",
      "args": [
        "peering-mcp"
      ],
      "env": {
        "PEERINGDB_API_KEY": "your-value"
      }
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "peering": {
      "command": "uvx",
      "args": [
        "peering-mcp"
      ],
      "env": {
        "PEERINGDB_API_KEY": "your-value"
      }
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "peering": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "peering-mcp"
      ],
      "env": {
        "PEERINGDB_API_KEY": "your-value"
      }
    }
  }
}

Values you fill in

  • PEERINGDB_API_KEY secret required env
    A free PeeringDB API key. Recommended, not required: it raises the rate limit, and every tool works without one.
  • PEERING_MCP_CACHE_TTL env
    How long a cached upstream response stays usable, in seconds.
  • PEERING_MCP_CACHE_DIR env
    Where the on-disk cache lives. Defaults to $XDG_CACHE_HOME/peering-mcp.
  • PEERING_MCP_NO_CACHE env
    Set to 1 to disable caching. Slower, and harder on the upstream APIs.
  • PEERING_MCP_TIMEOUT env
    Per-request timeout in seconds.
  • PEERING_MCP_MAX_RETRIES env
    Attempts before an upstream failure is reported.

Descriptions are as written by the maker.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
25/wk
Connection
Runs on your computer
Latest versioni
0.1.1
Categoryi
Other
Published to registryi
Sep 20, 2026
Code last changedi
Sep 20, 2026
Maker
LeonardMichalas
Packages
pypi: peering-mcp
Website
github.com
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account LeonardMichalas, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 2 months ago

  • ✓ Pass

    Has a licence

    Uses MIT

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

No entries on OSV.dev for peering-mcp@0.1.1

Checks only this package version, not every dependency · checked Nov 16, 2026

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/leonardmichalas-peering-mcp.svg)](https://mcp.popnx.com/en/servers/leonardmichalas-peering-mcp)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Otheri

  • More stars than 0% of the other 20653 servers in this category
  • Published to the registry more recently than 42% of the other 20653 servers in this category
  • Basic checks equal to or better than 99% of the other 20653 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Peering MCP safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: PEERINGDB_API_KEY

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed 2 months ago, and the latest version (0.1.1) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.

by koala73Widely used★ 90.9KUpdated 3 days ago

Runs in the cloud✓ service owner · worldmonitor.app

openstatus

Manage monitors, status pages, incidents and maintenances in your openstatus workspace.

by openstatusHQWidely used★ 9.3KUpdated 2 months ago

Runs in the cloud✓ service owner · openstatus.dev

Oh My Posh Validator

Validate oh-my-posh configurations and segment snippets against the official schema.

by JanDeDobbeleerWidely used★ 23.8K Stars for the whole repoUpdated 30 days ago

Runs in the cloud✓ service owner · ohmyposh.dev

Strata

MCP server for progressive tool usage at any scale (see https://klavis.ai)

by Klavis-AIGrowing★ 5.8KUpdated 14 months ago

Runs in the cloudRepo archived✓ klavis.ai

Jitsu

Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.

by jitsucomWidely used★ 5.1KUpdated 4 months ago

Runs in the cloud✓ service owner · jitsu.com
Compared with similar ones
This one
Peering MCP
World MonitoropenstatusOh My Posh ValidatorStrataJitsu
Runs whereInstalls on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyYesNoNoNoNoNo
Add with + in ClaudeNoNoNoNoNoNo
Basic checks3/34/44/44/41/44/4
LicenseMITAGPL-3.0AGPL-3.0MITApache-2.0MIT
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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

ToolQuestion it answers
lookup_networkWho is this network, and what is their peering policy?
list_presenceWhich internet exchanges and facilities are they present at?
find_at_exchangeWho else is at this exchange, and would they peer?
find_common_presenceWhere can these networks meet each other?
lookup_registrationWho is this IP range or AS number registered to?

find_common_presence 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.

find_at_exchange 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.

lookup_registration is the one tool here that does not read PeeringDB. It asks the registry that made the allocation — RIPE NCC, ARIN, APNIC, LACNIC or AFRINIC — and answers with the holder, the allocation date, the range the registration actually covers, and where to report abuse. Which registry to ask is itself a lookup, resolved from IANA's own bootstrap files rather than through a third-party redirector, so the answer can say who it came from.

Ask about one address and you get the block it sits in: 8.8.8.8 is answered with 8.8.8.0 - 8.8.8.255, registered to Google LLC. A range no registry is responsible for, such as 240.0.0.0/8, is answered without a request leaving the machine.

What an answer looks like

Every tool returns the same envelope, so a model learns one shape rather than five. Asking lookup_network for AS3320 returns this — the whole response, 854 bytes on the wire, against a 42-field upstream record:

{

"status": "ok", "data": { "network": { "asn": 3320, "name": "Deutsche Telekom", "long_name": "Deutsche Telekom AG", "website": "https://wholesale.telekom.com", "network_type": "NSP", "traffic_estimate": "50-100Tbps", "scope": "Global", "traffic_ratio": "Mostly Inbound", "ipv4_prefixes": 150000, "ipv6_prefixes": 40000, "exchange_count": 7, "facility_count": 53, "policy": { "general": "Restrictive", "locations": "Required - International", "ratio_required": true, "contract_required": "Required", "url": null }, "irr_as_set": "AS3320:AS-DTAG AS3320:AS-DTAG-V6", "looking_glass": "https://lg.telekom.com" }, "candidates": [] }, "note": "PeeringDB records are maintained by the networks themselves. Treat a missing field as unrecorded, not as evidence it is untrue.", "provenance": { "source": "peeringdb", "fetched_at": "2026-09-14T16:44:53.916085Z", "record_updated": "2026-08-31T13:30:19Z", "from_cache": false } }

The status field is the first thing to read, and ok means one thing only: the answer is in data. A name matching several networks returns ambiguous with the candidates to choose between, never a guess at which one was meant. An AS number that is not listed returns not_found, with a note saying a network can route traffic without being registered.

Three more, from the tools that do the work

Real responses, trimmed where marked. Nothing here is illustrative: each is what the tool returned on 2026-09-19.

"Where could Deutsche Telekom and Hurricane Electric peer with each other?" — one call to find_common_presence with [3320, 6939], four upstream requests:

{

"status": "ok", "data": { "networks": [ { "asn": 3320, "name": "Deutsche Telekom", "exchanges": 7, "facilities": 53 }, { "asn": 6939, "name": "Hurricane Electric", "exchanges": 335, "facilities": 342 } ], "exchanges": { "items": [ { "name": "NL-ix", "city": "Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt,…", "country": "NL", "networks": [ { "asn": 3320, "speed_mbps": 220000, "ports": 2, "route_server": false }, { "asn": 6939, "speed_mbps": 400000, "ports": 1, "route_server": true } ] }, { "name": "DE-CIX Frankfurt", "city": "Frankfurt", "country": "DE", "networks": [ { "asn": 3320, "speed_mbps": 110000, "ports": 1, "route_server": false }, { "asn": 6939, "speed_mbps": 800000, "ports": 1, "route_server": true } ] } ], "total": 6, "truncated": false } } }

Six shared exchanges, widest bottleneck first: NL-ix leads because the narrower of the two networks has 220 Gbps there, not because anyone has more in total. The per-network totals underneath are what make an empty answer readable — Deutsche Telekom records 7 exchanges in all, so "no overlap" would mean something different from Hurricane Electric's 335.

"Who is already at DE-CIX Frankfurt, and would they peer with anyone?" — find_at_exchange with policy: "Open":

{

"status": "ok", "data": { "exchange": { "exchange_id": 31, "name": "DE-CIX Frankfurt", "city": "Frankfurt", "country": "DE", "networks_recorded": 1020 }, "networks": { "items": [ { "asn": 24940, "name": "Hetzner Online", "speed_mbps": 2800000, "ports": 3, "route_server": true, "policy": "Open" }, { "asn": 20940, "name": "Akamai Technologies", "speed_mbps": 2100000, "ports": 4, "route_server": true, "policy": "Open" } ], "total": 649, "truncated": true } }, "note": "Participation is self-reported by each network in PeeringDB; a network missing here is unrecorded, not absent. Showing the 2 largest of the 649 networks (of 1020 here) stating policy Open; raise limit for more, at most 200." }

649 of the 1,020 networks there state an open policy. The filter applies to the exchange rather than to the page, so that is a count of the exchange — not "the open ones among the largest fifty".

"Who is 8.8.8.8 registered to, and where do I report abuse?" — lookup_registration, which reads the registry rather than PeeringDB:

{

"status": "ok", "data": { "target": "8.8.8.8", "kind": "address", "registry": "ARIN", "handle": "NET-8-8-8-0-2", "holder": "Google LLC", "covers": "8.8.8.0 - 8.8.8.255", "allocation_type": "DIRECT ALLOCATION", "registered": "2023-12-28T17:24:33-05:00", "abuse": { "name": "Abuse", "email": "network-abuse@google.com" } }, "note": "Registry data: it says who an allocation was made to, which is not always who operates the resource today.", "provenance": { "source": "rdap", "record_updated": "2023-12-28T17:24:56-05:00", "from_cache": true } }

The question was about one address and the answer covers the block it sits in, which is what covers is for.

How it works

The agent never reaches the internet itself. Everything goes through the server, which is the only place rate limiting, caching, validation and sanitisation can actually be enforced.

A request takes one of two paths:

That shaping step is not cosmetic. One network's raw presence records can exceed 130 KB, and returning that would flood the agent's context window and make it measurably worse at the actual task. list_presence turns Hurricane Electric's 336 exchange ports into a page of exchanges that fits 6 KB, largest capacity first, and says how many it left out — the page is cut to the budget rather than to a count, so the limit is a ceiling and the bytes are the guarantee. find_common_presence reads 225 KB across three networks and answers in under 4 KB.

Design principles

These are load-bearing rather than aspirational, and pull requests are reviewed against them.

  • Read-only, permanently. Only GET is ever sent, enforced at the transport rather than by convention. The

Only the beginning is shown; read the rest in the repo