IP Geolocation MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IPINFO_API_TOKEN | Yes | IPInfo API token for premium features. Required for batch lookups and residential proxy info. | |
| IPINFO_CACHE_TTL | No | Cache TTL in seconds | 3600 |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ipinfo_lookup_my_ipA | Geolocate the calling client's own IP. No arguments. On stdio transports the result is this server's outbound IP, not the
end user's. Use |
| ipinfo_lookup_ipsA | Geolocate one or more IPs and return ISP/ASN details. Returns a list in input order (after dedup and invalid-IP filtering); match
results back to your input via the |
| ipinfo_summarize_ipsA | Aggregate one or more IP lookups into counts and percentages. Uses the same validation, deduplication, cache, and upstream batch lookup
path as |
| ipinfo_check_residential_proxyA | Classify whether an IP is a known residential-proxy exit node. Returns ResidentialProxyDetails with |
| ipinfo_generate_map_urlA | Build an interactive ipinfo.io map for a set of IPs. Returns MapResult{url, mapped_ip_count, skipped_ips, skipped_count,
truncated}. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| capabilities | Structured capability summary: surface fingerprint, negative scope, plan tiers, error-code catalog, cache and long-running behavior, and the per-tool contract. Read this to plan calls without parsing the server instructions prose. |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/briandconnelly/mcp-server-ipinfo'
If you have feedback or need assistance with the MCP directory API, please join our Discord server