World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Who peers with whom, where they meet, and who an address range belongs to. PeeringDB and RDAP.
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 0/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 7/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 7/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Peering MCP。按照 https://mcp.popnx.com/i/leonardmichalas-peering-mcp.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 3/3 项检查 · 在你的电脑上运行 · ✓ 命令已检查 2026年11月14日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
把这段话复制到 Claude 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude 安装 MCP server Peering MCP,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "peering": { "command": "uvx", "args": [ "peering-mcp" ], "env": { "PEERINGDB_API_KEY": "your-value" } } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) PEERINGDB_API_KEY 先保留 "your-value",请我自己把真实值粘贴到文件或应用的输入框里。不要让我在对话里输入密钥。5) 按约定执行,然后确认 Peering MCP 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
SettingsDeveloperEdit Config
{
"mcpServers": {
"peering": {
"command": "uvx",
"args": [
"peering-mcp"
],
"env": {
"PEERINGDB_API_KEY": "your-value"
}
}
}
}只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
用 Peering MCP 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Peering MCP,或回答中出现 Peering MCP 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
PEERING_MCP_CACHE_TTL 缓存的上游响应可继续使用的时长,单位为秒。 PEERING_MCP_CACHE_DIR 磁盘缓存所在的位置。默认为 $XDG_CACHE_HOME/peering-mcp。 PEERING_MCP_NO_CACHE 设置为 1 可禁用缓存。速度会变慢,并且对上游 API 造成更大负担。 PEERING_MCP_TIMEOUT 每个请求的超时时间,单位为秒。 PEERING_MCP_MAX_RETRIES Attempts before an upstream failure is reported. · 默认值 3说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 Peering MCP
Peering MCP 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
A · 使用能连接 Peering MCP 的应用
B · 其他 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
可连接 Claude Code,但需要先准备
需要 Peering MCP 的密钥(在开发者网站创建) · 需要先在电脑上安装 Python (uv)(只需一次)
把这段话复制到 Claude Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude Code 安装 MCP server Peering MCP,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):claude mcp add --scope user peering --env PEERINGDB_API_KEY=your-value -- uvx peering-mcp 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) PEERINGDB_API_KEY 先保留 "your-value",请我自己把真实值粘贴到文件或应用的输入框里。不要让我在对话里输入密钥。5) 按约定执行,然后确认 Peering MCP 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --scope user peering --env PEERINGDB_API_KEY=your-value -- uvx peering-mcp按 Enter 前,把“your-value”改成你的密钥
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
应能看到 Peering MCP 在列表中并显示已连接
用 Peering MCP 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Peering MCP,或回答中出现 Peering MCP 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
PEERING_MCP_CACHE_TTL 缓存的上游响应可继续使用的时长,单位为秒。 PEERING_MCP_CACHE_DIR 磁盘缓存所在的位置。默认为 $XDG_CACHE_HOME/peering-mcp。 PEERING_MCP_NO_CACHE 设置为 1 可禁用缓存。速度会变慢,并且对上游 API 造成更大负担。 PEERING_MCP_TIMEOUT 每个请求的超时时间,单位为秒。 PEERING_MCP_MAX_RETRIES Attempts before an upstream failure is reported. · 默认值 3说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor,但需要先准备
需要 Peering MCP 的密钥(在开发者网站创建) · 需要先在电脑上安装 Python (uv)(只需一次)
把这段话复制到 Cursor 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Cursor 安装 MCP server Peering MCP,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "peering": { "command": "uvx", "args": [ "peering-mcp" ], "env": { "PEERINGDB_API_KEY": "your-value" } } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) PEERINGDB_API_KEY 先保留 "your-value",请我自己把真实值粘贴到文件或应用的输入框里。不要让我在对话里输入密钥。5) 按约定执行,然后确认 Peering MCP 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
在 Peering MCP 的设置中,PEERINGDB_API_KEY 还是空的,填入你的密钥并保存
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
用 Peering MCP 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Peering MCP,或回答中出现 Peering MCP 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
PEERING_MCP_CACHE_TTL 缓存的上游响应可继续使用的时长,单位为秒。 PEERING_MCP_CACHE_DIR 磁盘缓存所在的位置。默认为 $XDG_CACHE_HOME/peering-mcp。 PEERING_MCP_NO_CACHE 设置为 1 可禁用缓存。速度会变慢,并且对上游 API 造成更大负担。 PEERING_MCP_TIMEOUT 每个请求的超时时间,单位为秒。 PEERING_MCP_MAX_RETRIES Attempts before an upstream failure is reported. · 默认值 3说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code,但需要先准备
需要 Peering MCP 的密钥(在开发者网站创建) · 需要先在电脑上安装 Python (uv)(只需一次)
把这段话复制到 VS Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 VS Code 安装 MCP server Peering MCP,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "servers": { "peering": { "type": "stdio", "command": "uvx", "args": [ "peering-mcp" ], "env": { "PEERINGDB_API_KEY": "your-value" } } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) PEERINGDB_API_KEY 先保留 "your-value",请我自己把真实值粘贴到文件或应用的输入框里。不要让我在对话里输入密钥。5) 按约定执行,然后确认 Peering MCP 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
在 Peering MCP 的设置中,PEERINGDB_API_KEY 还是空的,填入你的密钥并保存
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
用 Peering MCP 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Peering MCP,或回答中出现 Peering MCP 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
PEERING_MCP_CACHE_TTL 缓存的上游响应可继续使用的时长,单位为秒。 PEERING_MCP_CACHE_DIR 磁盘缓存所在的位置。默认为 $XDG_CACHE_HOME/peering-mcp。 PEERING_MCP_NO_CACHE 设置为 1 可禁用缓存。速度会变慢,并且对上游 API 造成更大负担。 PEERING_MCP_TIMEOUT 每个请求的超时时间,单位为秒。 PEERING_MCP_MAX_RETRIES Attempts before an upstream failure is reported. · 默认值 3说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
Claude Code
claude mcp add --scope user peering --env PEERINGDB_API_KEY=your-value -- uvx peering-mcpClaude 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"
}
}
}
}PEERINGDB_API_KEY 机密 必填 envPEERING_MCP_CACHE_TTL envPEERING_MCP_CACHE_DIR envPEERING_MCP_NO_CACHE envPEERING_MCP_TIMEOUT envPEERING_MCP_MAX_RETRIES env说明为自动翻译,变量名保持原样;不确定时请查看原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过 GitHub 账户 LeonardMichalas 验证,该账户拥有此仓库
代码最后更新于2个月前
使用 MIT
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
OSV.dev 中没有 peering-mcp@0.1.1 的记录
只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月16日
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/leonardmichalas-peering-mcp)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:PEERINGDB_API_KEY
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于2个月前,最新版本(0.1.1)于2个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。
同一分类中有:World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| 本项 Peering MCP | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 是 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 3/3 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| 许可证 | MIT | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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.
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.
| Tool | Question it answers |
|---|---|
lookup_network | Who is this network, and what is their peering policy? |
list_presence | Which internet exchanges and facilities are they present at? |
find_at_exchange | Who else is at this exchange, and would they peer? |
find_common_presence | Where can these networks meet each other? |
lookup_registration | Who 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.
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.
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.
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.
These are load-bearing rather than aspirational, and pull requests are reviewed against them.
GET is ever sent, enforced at the transport rather than by convention. The