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., "@Chaitin IP Intelligence Search Tool check the reputation of 192.168.1.100"
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.
长亭 IP 智能查询服务
依托 Chaitin 全球蜜罐网络及百万级节点构建的IP情报分析平台，为移动内容提供商（MCP）提供精准的IP画像与威胁预警服务。
Chaitin IP Intelligence Query Service
An IP intelligence analysis platform built on Chaitin's global honeypot network and millions of nodes, providing accurate IP profiling and threat alerts for Mobile Content Providers (MCP).
Related MCP server: IP-Search
• 蜜罐数据驱动：实时关联Chaitin蜜罐捕获的恶意IP行为特征库
• 百万节点协同：整合全球防御节点的攻击拦截数据进行风险评估
• 威胁情报聚合：融合公开威胁数据库与Chaitin私有情报源
• 动态响应机制：基于防御节点反馈实时更新IP信誉评分
• Honeypot-Driven Data: Real-time correlation with Chaitin honeypot-captured malicious IP behavior feature databases
• Million-Node Collaboration: Integrates attack interception data from global nodes for risk assessment
• Threat Intelligence Aggregation: Combines public threat databases with Chaitin's private intelligence sources
• Dynamic Response System: Real-time IP reputation scoring based on node feedback
{
"mcpServers": {
"chaitin-ip-intelligence": {
"isActive": true,
"name": "chaitin-ip-intelligence",
"description": "",
"command": "npx",
"args": [
"-y",
"chaitin-ip-intelligence-search-tool"
]
}
}
}MIT
基于长亭威胁情报，获取给定 IP 的威胁情报信息，包括 IP 地址、地理位置、ASN、历史恶意行为等信息
| Name | Required | Description | Default |
|---|---|---|---|
| ip | Yes | IP address |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description must fully convey behavioral traits. It implies a read-only query but does not explicitly state idempotency, side effects, or requirements (e.g., authentication, rate limits). The listed return types provide some transparency, but critical behavioral details are missing.
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, clear sentence that efficiently conveys the tool's function and output. It avoids unnecessary words and is well-structured for quick comprehension, though a slightly more structured format could improve scanability.
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?
For a simple tool with one parameter and no output schema, the description adequately explains the purpose and return value categories. It does not go into excessive detail, but covers the essential information an agent needs to decide whether to invoke it.
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 schema covers 100% of the single 'ip' parameter with a basic description. The tool's description adds no extra semantic value beyond what the schema already provides, so the baseline score of 3 is appropriate.
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 tool's purpose: querying threat intelligence for a given IP. It uses the verb '获取' and explicitly lists the types of information returned (IP, location, ASN, malicious behavior), making it specific and unambiguous.
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 provides no guidance on when to use this tool, prerequisites, or alternatives. Without sibling tools, the lack of usage context is less critical, but the description still fails to set expectations for typical use cases or limitations.
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.
v0.1.1长亭 IP 情报查询Only one tool exists, so there is no possibility of confusion or overlap.
With a single tool, naming conventions are not applicable; consistency is inherently perfect.
A single tool for IP intelligence lookup is borderline; while it directly serves the stated purpose, users may expect additional functionality like batch queries or cache management.
The tool fully covers the server's stated purpose of IP threat intelligence lookup, providing all necessary information (location, ASN, historical behavior).
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Free no-key IP intelligence: geolocation, VPN detection, DNS, WHOIS, blacklists, breach checks
AI-powered threat intelligence, smart contract auditing, and cybersecurity OSINT.
Free IPv4 lookups against a distributed attacker-observation corpus.
Security intelligence for AI agents. 27 x402 endpoints: honeypot, forensics, CAPTCHA, preflight.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/co0ontty/chaitin-ip-intelligence-search-tool'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
