IPRout MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IPROUT_API_KEY | Yes | Your API key for IPRout. Required for authentication. | |
| IPROUT_API_BASE_URL | No | Base URL for the IPRout API. Optional. | https://api.iprout.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lookup_ipA | Lookup GeoIP and ASN information for a specific IPv4 or IPv6 address. |
| lookup_caller_ipB | Lookup GeoIP and ASN information for the caller IP as detected by IPRout. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one looks up the caller's own IP automatically, the other looks up a user-specified IP. There is no overlap in functionality.
Both tools use a consistent verb_noun pattern (lookup_caller_ip, lookup_ip) with snake_case, making the naming predictable and clear.
With only two tools, the server feels minimal. While it covers the essential operations for IP geolocation, the count is on the lower end of acceptable for a domain that could include additional lookups (e.g., bulk, range).
The tool set provides complete coverage for its stated domain: retrieving GeoIP and ASN information for both the caller and a specified IP. No obvious gaps exist.