Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@IPRout MCP Server look up 8.8.8.8"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
GeoIP and ASN intelligence for AI agents using the IPRout API.
This MCP server exposes IPRout lookup tools to MCP-compatible clients such as Claude Desktop and other agent runtimes.
Lookup GeoIP and ASN information for a specific IPv4 or IPv6 address.
Input:
{
"ip": "8.8.8.8"
}Lookup GeoIP and ASN information for the caller IP as detected by IPRout.
Input:
{}Related MCP server: The Aleph MCP
Node.js 18+
IPRout API key
npm installCreate a .env file:
IPROUT_API_KEY=your_api_key_here
IPROUT_API_BASE_URL=https://api.iprout.comIPROUT_API_BASE_URL is optional. It defaults to https://api.iprout.com.
npm startnpm run devUpdate your Claude Desktop MCP config:
{
"mcpServers": {
"iprout": {
"command": "node",
"args": [
"/absolute/path/to/iprout-mcp-server/src/index.js"
],
"env": {
"IPROUT_API_KEY": "your_api_key_here",
"IPROUT_API_BASE_URL": "https://api.iprout.com"
}
}
}
}Lookup 8.8.8.8 using IPRout.What country, ASN, and organization owns 1.1.1.1?Lookup my current IP using IPRout.The server sends your API key to IPRout using:
X-API-Key: YOUR_API_KEYWebsite: https://iprout.com
Documentation: https://iprout.com/docs
OpenAPI: https://iprout.com/docs/openapi.json
Postman: https://documenter.getpostman.com/view/55991899/2sBXwtrASm
Examples: https://github.com/IProut2026/examples
MIT
Lookup GeoIP and ASN information for the caller IP as detected by IPRout.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description must fully disclose behavior. It only mentions output type (GeoIP, ASN) but omits error handling, response format, or any side effects. For a zero-parameter tool, this is insufficient.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence with no wasted words. Could include more context, but meets conciseness standard.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema and no annotations, the description is minimal. It does not explain the output structure beyond 'GeoIP and ASN'. For a simple tool, it is adequate but could be improved with example output or data source mention.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters exist; schema coverage is 100%. Description adds no parameter details but is not needed. Baseline is high.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it looks up GeoIP and ASN for the caller IP as detected by IPRout. It distinguishes from the sibling tool 'lookup_ip' by specifying 'caller IP', implying this is for the current session's IP.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus the sibling 'lookup_ip'. Does not specify if this tool is for the current caller's IP only or if it can be used for other purposes.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Lookup GeoIP and ASN information for a specific IPv4 or IPv6 address.
| Name | Required | Description | Default |
|---|---|---|---|
| ip | Yes | IPv4 or IPv6 address to look up, for example 8.8.8.8 |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must fully disclose behavioral traits. It only states the basic function (lookup GeoIP and ASN) without mentioning any side effects, rate limits, data freshness, or that it may rely on external network calls. This is insufficient for a tool with no annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, well-structured sentence that immediately conveys the tool's action and scope. No filler or redundant information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simplicity of the tool (single parameter, no output schema), the description covers the essential aspects: what the tool does, what input it requires, and the type of information it returns. It does not describe the return structure, but that is partially implied by 'GeoIP and ASN information'.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema covers the parameter 'ip' with 100% description coverage, including an example. The description adds meaning by specifying 'GeoIP and ASN information', which is not in the schema, and reinforces the type of IP addresses accepted (IPv4 and IPv6).
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Lookup' and the resources 'GeoIP and ASN information for a specific IPv4 or IPv6 address'. It distinguishes from the sibling tool 'lookup_caller_ip' by indicating it works for any specified IP address, not just the caller's.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage: to get GeoIP and ASN for any IP. The sibling name 'lookup_caller_ip' provides context for when not to use this tool (i.e., for looking up the caller's own IP). However, no explicit when-not or alternative conditions are stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
v1.0.0lookup_caller_iplookup_ipThe 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.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
IP Geolocation: This API provides fast, reliable, and developer-friendly IP geolocation, ASN.
IP geolocation, ASN and network data, plus VPN, proxy and Tor detection. ASN tools need no key.
Free no-key IP intelligence: geolocation, VPN detection, DNS, WHOIS, blacklists, breach checks
Unlock the power of IP geolocation with our tool! Whether you're a developer needing location data
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/IProut2026/mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
