Skip to main content
Glama
BACH-AI-Tools

Netdetective MCP Server

by BACH-AI-Tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Netdetective MCP Server

English | 简体中文 | 繁體中文

用于访问 Netdetective API 的 MCP 服务器。

🚀 使用 EMCP 平台快速体验

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

快速开始：

  1. 🌐 访问 EMCP 平台

  2. 📝 注册并登录账号

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

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

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

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

EMCP 平台优势：

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

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

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

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

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

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

Related MCP server: GeoIP MCP Server

简介

这是一个 MCP 服务器，用于访问 Netdetective API。

  • PyPI 包名: bach-netdetective

  • 版本: 1.0.0

  • 传输协议: stdio

安装

从 PyPI 安装:

pip install bach-netdetective

从源码安装:

pip install -e .

运行

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

# 运行（uvx 会自动安装并运行）
uvx --from bach-netdetective bach_netdetective

# 或指定版本
uvx --from bach-netdetective@latest bach_netdetective

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

python server.py

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

# 安装
pip install bach-netdetective

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

配置

API 认证

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

export API_KEY="your_api_key_here"

环境变量

变量名

说明

必需

API_KEY

API 密钥

是

PORT

不适用

否

HOST

不适用

否

在 Cursor 中使用

编辑 Cursor MCP 配置文件 ~/.cursor/mcp.json:

{
  "mcpServers": {
    "bach-netdetective": {
      "command": "uvx",
      "args": ["--from", "bach-netdetective", "bach_netdetective"],
      "env": {
        "API_KEY": "your_api_key_here"
      }
    }
  }
}

在 Claude Desktop 中使用

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

{
  "mcpServers": {
    "bach-netdetective": {
      "command": "uvx",
      "args": ["--from", "bach-netdetective", "bach_netdetective"],
      "env": {
        "API_KEY": "your_api_key_here"
      }
    }
  }
}

可用工具

此服务器提供以下工具:

query

Query information about an IP address.

端点: GET /query

参数:

  • ipaddress (string): The IP address to use for the query. Defaults to the ip address of the connecting client

技术栈

  • 传输协议: stdio

  • HTTP 客户端: httpx

许可证

MIT License - 详见 LICENSE 文件。

开发

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

版本: 1.0.0

Available Tools

1 tool
queryC

Query information about an IP address.

ParametersJSON Schema
NameRequiredDescriptionDefault
ipaddressNoThe IP address to use for the query. Defaults to the ip address of the connecting client

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to indicate whether the operation is read-only, what happens with invalid IP formats, rate limits, or data source reliability.

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

Conciseness4/5

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

The description is a single, efficient sentence with no redundancy. However, its brevity contributes to underspecification—additional sentences explaining return value or usage context would earn their place.

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

Completeness2/5

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

Despite the tool's simplicity (one optional parameter, no nested objects), the description lacks critical context: what specific information the query returns and in what format. Without an output schema, this omission is significant.

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

Parameters3/5

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

Schema description coverage is 100% ('The IP address to use for the query. Defaults to the ip address of the connecting client'), establishing the baseline score. The description adds no further parameter semantics beyond the schema, but none are needed given the single, well-documented optional parameter.

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

Purpose3/5

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

The description identifies the resource (IP address) and action (query), but 'information' is vague—it doesn't specify what data is returned (geolocation, ownership, reputation, etc.). Without sibling tools, differentiation is moot, but the purpose remains under-specified.

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?

No explicit when/when-not guidance is provided, but usage is implied by the description (use when you need IP information). With no sibling tools to differentiate from, this represents minimal viable 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 observedquery
Deploy Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly defined as querying IP address information, leaving no ambiguity for an agent to misselect.

Naming Consistency5/5

A single tool named 'query' follows a consistent pattern by default. There are no other tools to compare against, so no inconsistency can exist in naming conventions.

Tool Count2/5

One tool is too few for a server named 'Netdetective MCP Server', which suggests a broader scope like network investigation. A single query tool feels thin and incomplete for such a domain, lacking operations like scanning, pinging, or analyzing multiple IPs.

Completeness2/5

The tool surface is severely incomplete for network detective work. It only provides IP address queries, missing essential operations such as port scanning, DNS lookups, traceroute, or bulk analysis, which are typical for this domain and would cause agent failures in complex tasks.

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

  • ip-geolocation-mcp

    Rumblingb
    A
    license
    Not graded
    quality
    F
    maintenance
    MCP server for IP geolocation lookups using ipinfo.io, with single, own, and batch queries.
    1
    MIT

  • personal-mcp-server

    jango-blockchained
    A
    license
    Not graded
    quality
    D
    maintenance
    MCP server providing IP address lookup capabilities. Enables AI assistants to fetch details about public IP addresses or the user's current device IP.
    228
    ISC