A
licenseA
qualityB
maintenanceEmail validation MCP server using MailboxValidator API to determine validity of an email address.
3
35
1
MIT
naverbot
by com.seoapi
Server Details
Validate Naver Yeti IP addresses. Remote MCP validate_ip tool.
- Status
- Healthy
- 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
A3.8/5.0
Tool DescriptionsA
Average 3.7/5 across 1 of 1 tools scored.
Server CoherenceA
Disambiguation5/5
With only one tool, there is no possibility of confusion or overlap. The tool's purpose is clear and distinct.
Naming Consistency5/5
The single tool 'validate_ip' follows a consistent verb_noun naming pattern using snake_case, which is clear and standard.
Tool Count2/5
A single tool server is very minimal. While it may be appropriate for a narrow utility, most servers benefit from multiple related tools to provide a more complete interface.
Completeness4/5
The tool accurately fulfills its described purpose of validating IP addresses against Naver Yeti's published data. No obvious gaps in that specific task, but the domain could support additional related tools.
Available Tools
1 toolvalidate_ipValidate Naver Yeti IPAInspect
Check whether an IP address (IPv4 or IPv6) is a genuine Naver Yeti IP address, verified against Naver Yeti'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.7/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description hints at an external dependency ('verified against... published IP data on seoapi.com') but does not explicitly state that a network call is required, nor does it disclose potential issues like rate limits, latency, or error handling. Without annotations, the description carries the full burden and falls short.
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-formed sentence that conveys all necessary information without any extraneous words. It is concise and front-loaded.
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?
For a simple validation tool with one parameter and no output schema, the description is mostly complete in explaining the input and validation source. However, it fails to specify the return format (e.g., boolean, details), which is important context for the agent.
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 covers 100% of the parameter with a description that already includes 'IPv4 or IPv6'. The tool description adds no additional meaning beyond what the schema 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.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: to check whether an IP address (IPv4 or IPv6) is a genuine Naver Yeti IP address, verified against published data. The verb 'Check' and the resource 'Naver Yeti IP address' are specific and unambiguous, even without sibling differentiation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies when to use the tool (when verification of Naver Yeti IP is needed) but does not provide explicit 'when not to use' or alternative tools. Since no sibling tools are listed, the lack of exclusions is acceptable, but explicit guidance would be better.
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-qualityBmaintenanceProvides MCP tools for IP threat intelligence lookup and enrichment, including single IP lookup, bulk hunting, ASN expansion, and feed status queries.MIT
- Flicense-qualityDmaintenanceComprehensive email validation MCP server that checks syntax, MX records, disposable domains, role-based accounts, SPF/DKIM, typo suggestions, and risk scoring.
- 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