Skip to main content
Glama
BACH-AI-Tools

ip_geolocation_find_ip_location_and_ip_info

by BACH-AI-Tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Ip Geolocation Find Ip Location And Ip Info MCP Server

English | 简体中文 | 繁體中文

🚀 使用 EMCP 平台快速体验

EMCP 是一个强大的 MCP 服务器管理平台，让您无需手动配置即可快速使用各种 MCP 服务器！

快速开始：

  1. 🌐 访问 EMCP 平台

  2. 📝 注册并登录账号

  3. 🎯 进入 MCP 广场，浏览所有可用的 MCP 服务器

  4. 🔍 搜索或找到本服务器（bach-ip_geolocation_find_ip_location_and_ip_info）

  5. 🎉 点击 "安装 MCP" 按钮

  6. ✅ 完成！即可在您的应用中使用

EMCP 平台优势：

  • ✨ 零配置：无需手动编辑配置文件

  • 🎨 可视化管理：图形界面轻松管理所有 MCP 服务器

  • 🔐 安全可靠：统一管理 API 密钥和认证信息

  • 🚀 一键安装：MCP 广场提供丰富的服务器选择

  • 📊 使用统计：实时查看服务调用情况

立即访问 EMCP 平台 开始您的 MCP 之旅！

Related MCP server: GeoIP MCP Server

简介

这是一个使用 FastMCP 自动生成的 MCP 服务器，用于访问 Ip Geolocation Find Ip Location And Ip Info API。

  • PyPI 包名: bach-ip_geolocation_find_ip_location_and_ip_info

  • 版本: 1.0.0

  • 传输协议: stdio

安装

从 PyPI 安装:

pip install bach-ip_geolocation_find_ip_location_and_ip_info

从源码安装:

pip install -e .

运行

方式 1: 使用 uvx（推荐，无需安装）

# 运行（uvx 会自动安装并运行）
uvx --from bach-ip_geolocation_find_ip_location_and_ip_info bach_ip_geolocation_find_ip_location_and_ip_info

# 或指定版本
uvx --from bach-ip_geolocation_find_ip_location_and_ip_info@latest bach_ip_geolocation_find_ip_location_and_ip_info

方式 2: 直接运行（开发模式）

python server.py

方式 3: 安装后作为命令运行

# 安装
pip install bach-ip_geolocation_find_ip_location_and_ip_info

# 运行（命令名使用下划线）
bach_ip_geolocation_find_ip_location_and_ip_info

配置

API 认证

此 API 需要认证。请设置环境变量:

export API_KEY="your_api_key_here"

环境变量

变量名

说明

必需

API_KEY

API 密钥

是

PORT

不适用

否

HOST

不适用

否

在 Claude Desktop 中使用

编辑 Claude Desktop 配置文件 claude_desktop_config.json:

{
  "mcpServers": {
    "ip_geolocation_find_ip_location_and_ip_info": {
      "command": "python",
      "args": ["E:\path\to\ip_geolocation_find_ip_location_and_ip_info\server.py"],
      "env": {
        "API_KEY": "your_api_key_here"
      }
    }
  }
}

注意: 请将 E:\path\to\ip_geolocation_find_ip_location_and_ip_info\server.py 替换为实际的服务器文件路径。

可用工具

此服务器提供以下工具:

get_ip_geolocation

This endpoint returns geolocation and other useful points from an IP Address. If IP address is provided as query parameter, geolocation is performed on that IP address. If IP address is left empty, geolocation data of client IP is returned.

端点: GET /backend/ipinfo/

参数:

  • ip (string): Example value: 206.71.50.230

技术栈

  • FastMCP: 快速、Pythonic 的 MCP 服务器框架

  • 传输协议: stdio

  • HTTP 客户端: httpx

开发

此服务器由 API-to-MCP 工具自动生成。

版本: 1.0.0

Available Tools

1 tool
get_ip_geolocationA

This endpoint returns geolocation and other useful points from an IP Address. If IP address is provided as query parameter, geolocation is performed on that IP address. If IP address is left empty, geolocation data of client IP is returned.

ParametersJSON Schema
NameRequiredDescriptionDefault
ipNoExample value: 206.71.50.230

TDQS

A3.9/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It discloses that the tool performs geolocation and returns data, and explains the behavior when IP is empty. However, it doesn't disclose rate limits, data freshness, error handling, or any permission requirements, leaving gaps for a scoring of 3.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise with three sentences, each adding distinct information. The first states purpose, the second explains the query parameter mode, the third explains the default behavior. No redundant or unnecessary text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has low complexity with one parameter and no output schema. The description explains the input and basic behavior, but lacks details on return format, possible errors, or data attributes. Since there's no output schema, the description should compensate more, but it remains somewhat incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% but the schema only provides an example value for the single parameter. The description adds meaning beyond the schema by explaining that the parameter is optional and that omitting it returns the client's IP geolocation. This add clarifies the parameter's role effectively.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool returns geolocation and other points from an IP address. It specifies two modes: query parameter IP or client IP if empty, which precisely describes the tool's action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains when to provide an IP and when not to, but there are no siblings or alternatives mentioned to guide selection. It implies usage context (providing vs leaving empty) but lacks explicit when-to-use or when-not-to-use guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev1.0.0
    • First observedget_ip_geolocation
Deploy Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion between tools. The tool's purpose is clearly defined and distinct.

Naming Consistency5/5

The single tool name 'get_ip_geolocation' follows a clear verb_noun pattern, consistent with itself. No inconsistency exists.

Tool Count3/5

A single tool feels thin for the server's stated purpose, which is finding IP location and info. While it covers the basic operation, the scope suggests more features could be included (e.g., bulk lookup, IP validation).

Completeness4/5

The tool provides the core functionality of IP geolocation, including automatic client IP detection. Minor gaps exist, such as no support for IPv6 or additional IP metadata, but the essential need is met.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • GeoIP MCP Server

    mamorett
    A
    license
    Not graded
    quality
    C
    maintenance
    An MCP server that provides IP geolocation services using MaxMind's GeoIP2 databases, allowing users to retrieve geographical information for single or multiple IP addresses including country, city, coordinates, and ASN details.
    GPL 3.0

  • Netdetective MCP Server

    BACH-AI-Tools
    A
    license
    B
    quality
    D
    maintenance
    An MCP server that provides access to the Netdetective API for querying information about IP addresses. It enables users to retrieve metadata for a specified IP address or the connecting client's default IP address.
    1
    MIT