Skip to main content
Glama
ravinahp

Email Checker MCP Server

by ravinahp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
verify_emailB
Verify an email address using the 2ip.me API.

Args:
    email (str): The email address to verify

Returns:
    str: "true" or "false" indicating if the email is valid

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
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

TDQS

B3.3/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined and distinct.

Naming Consistency5/5

Since there is only one tool, naming consistency is inherently perfect. The tool name 'verify_email' follows a clear verb_noun pattern.

Tool Count2/5

A single tool is too few for a server named 'Email Checker MCP Server', which suggests a broader scope. This minimal set feels thin and underdeveloped for the domain.

Completeness2/5

The server is severely incomplete for email checking. It only verifies email validity, missing obvious operations like checking email deliverability, domain reputation, or spam score, which are typical in this domain.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources