Search public BGP MRT archives by time window and collector, and look up any IP address or ASN.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Autonomous System Number to analyze (1-4294967295). Examples: 15169 (Google), 7922 (Comcast), 13335 (Cloudflare), 32934 (Facebook). Returns organization details, network size metrics (customer cone, prefixes, ASN relationships), geographic presence, hegemony scores, and connectivity patterns - crucial for competitive intelligence, peering analysis, and Internet topology research. Omit to browse or filter all ASNs.
Page number for paginated results when browsing all ASNs or filtering by country/search. Starts from 0.
Search ASNs by name or organization (case-insensitive partial match). Examples: 'google', 'comcast', 'cloudflare'. Useful for finding ASNs when you don't know the exact number.
Filter ASNs by country code (ISO 3166-1 alpha-2, e.g., 'US', 'DE', 'JP'). Useful for finding all autonomous systems registered in a specific country.
Number of results per page (max 10000). Default: 100. Use for pagination when browsing large result sets.
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
Run in a terminal
claude mcp add --transport http bgpkit-api https://mcp.bgpkit.com/mcp
| Argument | Type | Description |
|---|---|---|
| asn | number | Autonomous System Number to analyze (1-4294967295). Examples: 15169 (Google), 7922 (Comcast), 13335 (Cloudflare), 32934 (Facebook). Returns organization details, network size metrics (customer cone, prefixes, ASN relationships), geographic presence, hegemony scores, and connectivity patterns - crucial for competitive intelligence, peering analysis, and Internet topology research. Omit to browse or filter all ASNs. |
| page | number | Page number for paginated results when browsing all ASNs or filtering by country/search. Starts from 0. |
| search | string | Search ASNs by name or organization (case-insensitive partial match). Examples: 'google', 'comcast', 'cloudflare'. Useful for finding ASNs when you don't know the exact number. |
| country | string | Filter ASNs by country code (ISO 3166-1 alpha-2, e.g., 'US', 'DE', 'JP'). Useful for finding all autonomous systems registered in a specific country. |
| page_size | number | Number of results per page (max 10000). Default: 100. Use for pagination when browsing large result sets. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"asn": {
"type": "number",
"description": "Autonomous System Number to analyze (1-4294967295). Examples: 15169 (Google), 7922 (Comcast), 13335 (Cloudflare), 32934 (Facebook). Returns organization details, network size metrics (customer cone, prefixes, ASN relationships), geographic presence, hegemony scores, and connectivity patterns - crucial for competitive intelligence, peering analysis, and Internet topology research. Omit to browse or filter all ASNs."
},
"page": {
"type": "number",
"description": "Page number for paginated results when browsing all ASNs or filtering by country/search. Starts from 0."
},
"search": {
"type": "string",
"description": "Search ASNs by name or organization (case-insensitive partial match). Examples: 'google', 'comcast', 'cloudflare'. Useful for finding ASNs when you don't know the exact number."
},
"country": {
"type": "string",
"description": "Filter ASNs by country code (ISO 3166-1 alpha-2, e.g., 'US', 'DE', 'JP'). Useful for finding all autonomous systems registered in a specific country."
},
"page_size": {
"type": "number",
"description": "Number of results per page (max 10000). Default: 100. Use for pagination when browsing large result sets."
}
},
"additionalProperties": false
}| Argument | Type | Description |
|---|---|---|
| asns* | array | Array of ASN numbers to analyze (max 10,000 per request). Examples: [15169, 7922, 13335]. More efficient than individual lookups for analyzing multiple networks simultaneously. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"asns"
],
"properties": {
"asns": {
"type": "array",
"items": {
"type": "number"
},
"maxItems": 10000,
"minItems": 1,
"description": "Array of ASN numbers to analyze (max 10,000 per request). Examples: [15169, 7922, 13335]. More efficient than individual lookups for analyzing multiple networks simultaneously."
}
},
"additionalProperties": false
}| Argument | Type | Description |
|---|---|---|
| active | boolean | Filter for active collectors only (not deactivated) |
| country | string | Filter by country code (e.g., 'US', 'DE', 'JP') |
| project | string | Filter by collector project: 'routeviews' or 'riperis' |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"active": {
"type": "boolean",
"description": "Filter for active collectors only (not deactivated)"
},
"country": {
"type": "string",
"description": "Filter by country code (e.g., 'US', 'DE', 'JP')"
},
"project": {
"enum": [
"routeviews",
"riperis"
],
"type": "string",
"description": "Filter by collector project: 'routeviews' or 'riperis'"
}
},
"additionalProperties": false
}No arguments.
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
}| Argument | Type | Description |
|---|---|---|
| project | string | Filter by data collection project. 'routeviews', 'riperis'. |
| data_type | string | Type of latest BGP data needed. 'rib' returns most recent routing table snapshots (best for current network topology analysis), 'updates' returns latest real-time routing changes (best for monitoring recent network events). Omit to get both types. |
| collector_id | string | Target specific route collector for latest data. Examples: 'route-views.linx', 'rrc01'. Omit to get latest files from all collectors. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"project": {
"type": "string",
"description": "Filter by data collection project. 'routeviews', 'riperis'."
},
"data_type": {
"type": "string",
"description": "Type of latest BGP data needed. 'rib' returns most recent routing table snapshots (best for current network topology analysis), 'updates' returns latest real-time routing changes (best for monitoring recent network events). Omit to get both types."
},
"collector_id": {
"type": "string",
"description": "Target specific route collector for latest data. Examples: 'route-views.linx', 'rrc01'. Omit to get latest files from all collectors."
}
},
"additionalProperties": false
}| Argument | Type | Description |
|---|---|---|
| asn | number | Filter for specific Autonomous System Number to see route collectors peers from a specific network |
| collector_id | string | Target route collector to analyze peer relationships. Examples: 'route-views.linx', 'rrc01' |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"asn": {
"type": "number",
"description": "Filter for specific Autonomous System Number to see route collectors peers from a specific network"
},
"collector_id": {
"type": "string",
"description": "Target route collector to analyze peer relationships. Examples: 'route-views.linx', 'rrc01'"
}
},
"additionalProperties": false
}| Argument | Type | Description |
|---|---|---|
| page | number | Page number for paginated results (starts from 1). Use for navigating large datasets when searching broad time periods or popular collectors. |
| ts_end | string | End timestamp for data collection period. Same format as ts_start. Combine with ts_start to define a specific time window for targeted BGP event analysis or research. |
| project | string | BGP data collection project. Options: 'routeviews' (University of Oregon RouteViews project) or 'riperis' (RIPE NCC Routing Information Service). Each has different collector locations and methodologies. |
| ts_start | string | Start timestamp for data collection period. Accepts ISO 8601 format (e.g., '2024-08-01T00:00:00Z') or Unix timestamp. Use to find data from a specific date onwards for historical analysis. |
| data_type | string | Type of BGP data to retrieve. 'rib' = Routing Information Base (periodic full routing table snapshots, typically every 2-8 hours, ideal for network topology analysis). 'updates' = real-time BGP routing updates (announcements/withdrawals, ideal for studying routing dynamics and outages). |
| page_size | number | Results per page. Range: 1-1000, default: 100. Use larger values (500-1000) for bulk data discovery, smaller values (10-50) for quick exploration. |
| collector_id | string | Specific route collector identifier. Examples: 'route-views.linx' (RouteViews LINX), 'rrc01' (Amsterdam). |
| Argument | Type | Description |
|---|---|---|
| ip* | string | IP address to analyze (IPv4 or IPv6 format). Examples: '8.8.8.8' (Google DNS), '2001:4860:4860::8888' (Google IPv6 DNS), '1.1.1.1' (Cloudflare DNS). Returns geolocation, ASN ownership, BGP prefix, and RPKI validation status - essential for security analysis, geoblocking, network forensics, and traffic analytics. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"ip"
],
"properties": {
"ip": {
"type": "string",
"description": "IP address to analyze (IPv4 or IPv6 format). Examples: '8.8.8.8' (Google DNS), '2001:4860:4860::8888' (Google IPv6 DNS), '1.1.1.1' (Cloudflare DNS). Returns geolocation, ASN ownership, BGP prefix, and RPKI validation status - essential for security analysis, geoblocking, network forensics, and traffic analytics."
}
},
"additionalProperties": false
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 19, 2026.
No readOnlyHint / destructiveHint annotations, so clients can't tell a read from a write without asking.
Fix: Add annotations to each tool, e.g. { readOnlyHint: true } for tools that only read.
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"page": {
"type": "number",
"description": "Page number for paginated results (starts from 1). Use for navigating large datasets when searching broad time periods or popular collectors."
},
"ts_end": {
"type": "string",
"description": "End timestamp for data collection period. Same format as ts_start. Combine with ts_start to define a specific time window for targeted BGP event analysis or research."
},
"project": {
"type": "string",
"description": "BGP data collection project. Options: 'routeviews' (University of Oregon RouteViews project) or 'riperis' (RIPE NCC Routing Information Service). Each has different collector locations and methodologies."
},
"ts_start": {
"type": "string",
"description": "Start timestamp for data collection period. Accepts ISO 8601 format (e.g., '2024-08-01T00:00:00Z') or Unix timestamp. Use to find data from a specific date onwards for historical analysis."
},
"data_type": {
"type": "string",
"description": "Type of BGP data to retrieve. 'rib' = Routing Information Base (periodic full routing table snapshots, typically every 2-8 hours, ideal for network topology analysis). 'updates' = real-time BGP routing updates (announcements/withdrawals, ideal for studying routing dynamics and outages)."
},
"page_size": {
"type": "number",
"description": "Results per page. Range: 1-1000, default: 100. Use larger values (500-1000) for bulk data discovery, smaller values (10-50) for quick exploration."
},
"collector_id": {
"type": "string",
"description": "Specific route collector identifier. Examples: 'route-views.linx' (RouteViews LINX), 'rrc01' (Amsterdam)."
}
},
"additionalProperties": false
}