A
licenseA
qualityB
maintenanceEmail validation MCP server using MailboxValidator API to determine validity of an email address.
3
35
1
MIT
yandexbot
by com.seoapi
Server Details
Validate whether an IP address belongs to YandexBot. Remote MCP server exposing a validate_ip tool.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4/5.0
Tool DescriptionsA
Average 3.8/5 across 1 of 1 tools scored.
Server CoherenceA
Disambiguation5/5
Only one tool exists, so there is no risk of confusion or ambiguity between tools.
Naming Consistency5/5
The single tool follows a clear verb_noun pattern (validate_ip), consistent with good naming practices.
Tool Count3/5
While a single tool is minimal, it serves a very narrow and specific purpose (validating YandexBot IPs), so it is borderline appropriate but feels thin.
Completeness5/5
For the stated purpose of verifying YandexBot IPs, the single tool fully covers the required functionality.
Available Tools
1 toolvalidate_ipValidate YandexBot IPAInspect
Check whether an IP address (IPv4 or IPv6) is a genuine YandexBot IP address, verified against YandexBot's published IP data on seoapi.com.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ip | Yes | The IPv4 or IPv6 address to validate |
Tool Definition Quality
A3.8/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 states the action (check against published data) but does not disclose return format (e.g., boolean), error handling, rate limits, or external dependency behavior. For a simple validation, the information is minimally adequate.
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, well-structured sentence that front-loads the key action and source. Every word adds value, and there is no redundant information. Excellent conciseness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (one required parameter, no output schema, no sibling tools), the description is largely complete: it specifies input type and verification source. Minor gaps include missing details on return type and error behavior, but these are not critical for basic usage.
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?
The input schema itself has 100% description coverage (the 'ip' parameter is described as 'The IPv4 or IPv6 address to validate'). The tool description adds no additional semantic value beyond what the schema already provides, so the baseline score applies.
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 validates IP addresses (IPv4 or IPv6) against YandexBot's published IP data, specifying both the resource (IP) and the specific verification source (seoapi.com). This precisely defines the tool's purpose and distinguishes it from generic IP validation tools.
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 implies usage when needing to confirm an IP is a genuine YandexBot IP, but no explicit guidance on when to use or avoid this tool versus alternatives is provided. Since there are no sibling tools, the lack of comparative context reduces the score.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- Alicense-qualityDmaintenanceMCP server providing IP address lookup capabilities. Enables AI assistants to fetch details about public IP addresses or the user's current device IP.98ISC
- Flicense-qualityCmaintenanceOfficial parseAPI MCP server providing IP/place data, email/phone/domain validation, weather, currency, timezone, and holiday lookups as tools for AI agents.
- Flicense-qualityCmaintenanceRemote MCP server for company tech profiling. It exposes tools for DNS, domain registration, SSL, website fingerprinting, IP/cloud provider, subdomains, and company analysis using public data without API keys.