A
licenseA
qualityA
maintenanceOfficial parseAPI MCP server providing IP/place data, email/phone/domain validation, weather, currency, timezone, and holiday lookups as tools for AI agents.
32
426 npm
MIT
perplexitybot
by com.seoapi
Server Details
Validate PerplexityBot IP addresses. Remote MCP validate_ip tool.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
TDQS
B3.4/5.0
Scored across 1 tool
Disambiguation5/5
Only one tool exists, so there is no possibility of confusion between tools.
Naming Consistency5/5
With a single tool, naming is inherently consistent; 'validate_ip' follows a clear verb_noun pattern.
Tool Count1/5
A single tool for a server named 'perplexitybot' is extremely thin; the purpose suggests a broader set of validation or query tools is missing.
Completeness2/5
The tool only validates IPs against a specific list; many other aspects of PerplexityBot identification (e.g., header checks, user-agent parsing) are absent, leaving significant gaps.
Available Tools
1 toolvalidate_ipValidate PerplexityBot IPAInspect
Check whether an IP address (IPv4 or IPv6) is a genuine PerplexityBot IP address, verified against PerplexityBot's published IP data on seoapi.com.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ip | Yes | The IPv4 or IPv6 address to validate |
TDQS
A3.5/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must fully disclose behavior. It fails to mention whether the operation is read-only, has side effects, or involves external calls. The return format or success/failure indicators are not described.
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 a single sentence that immediately states the purpose, scope, and verification source. It is front-loaded and contains no superfluous information.
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 one required parameter and no output schema. The description covers the core purpose and verification source but does not explain the output or any error conditions. For a simple validation tool, this is adequate but not fully complete.
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%, and the parameter description is adequate. The tool's main description adds context about the verification source but does not significantly enhance understanding of the parameter beyond the schema.
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 that the tool validates whether an IP address is a genuine PerplexityBot IP, specifying both IPv4 and IPv6, and references the verification source. This provides a specific verb-resource combination with clear scope.
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 guidance on when to use the tool versus alternatives is given. However, since there are no sibling tools, the implied usage is clear. The description lacks any when-not-to-use or prerequisite information.
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 tool update
- First observed
validate_ip
Related MCP Connectors
Validate ClaudeBot and Claude-SearchBot IP addresses. Remote MCP validate_ip tool.
Validate GPTBot and OAI-SearchBot IP addresses. Remote MCP validate_ip tool.
Validate DuckDuckBot IP addresses. Remote MCP validate_ip tool.
Validate Cốc Cốc Bot IP addresses. Remote MCP validate_ip tool.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables checking any IP address for VPN, proxy, Tor, datacenter hosting, anonymity, and fraud risk signals, plus API service status, directly from MCP-capable clients like Claude and Cursor.16 npm2MIT
- AlicenseNot gradedqualityCmaintenanceMCP server providing IP address lookup capabilities. Enables AI assistants to fetch details about public IP addresses or the user's current device IP.11 npmISC
- AlicenseNot gradedqualityCmaintenanceProvides a no-key IP intelligence API for MCP clients, enabling IP geolocation, VPN/datacenter detection, DNS, WHOIS, blacklist checks, security headers, port scanning, and more.MIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd
Glama MCP Gateway
Add one secure layer between your agents and this server.