Skip to main content
Glama
BACH-AI-Tools

Email Social Media Checker

by BACH-AI-Tools
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

Email Social Media Checker MCP Server

English | 简体中文 | 繁體中文

用于访问 Email Social Media Checker API 的 MCP 服务器。

🚀 使用 EMCP 平台快速体验

EMCP 是一个强大的 MCP 服务器管理平台，让您无需手动配置即可快速使用各种 MCP 服务器！

快速开始：

  1. 🌐 访问 EMCP 平台

  2. 📝 注册并登录账号

  3. 🎯 进入 MCP 广场，浏览所有可用的 MCP 服务器

  4. 🔍 搜索或找到本服务器（bach-email_social_media_checker）

  5. 🎉 点击 "安装 MCP" 按钮

  6. ✅ 完成！即可在您的应用中使用

EMCP 平台优势：

  • ✨ 零配置：无需手动编辑配置文件

  • 🎨 可视化管理：图形界面轻松管理所有 MCP 服务器

  • 🔐 安全可靠：统一管理 API 密钥和认证信息

  • 🚀 一键安装：MCP 广场提供丰富的服务器选择

  • 📊 使用统计：实时查看服务调用情况

立即访问 EMCP 平台 开始您的 MCP 之旅！

Related MCP server: email-verify

简介

这是一个 MCP 服务器，用于访问 Email Social Media Checker API。

  • PyPI 包名: bach-email_social_media_checker

  • 版本: 1.0.0

  • 传输协议: stdio

安装

从 PyPI 安装:

pip install bach-email_social_media_checker

从源码安装:

pip install -e .

运行

方式 1: 使用 uvx（推荐，无需安装）

# 运行（uvx 会自动安装并运行）
uvx --from bach-email_social_media_checker bach_email_social_media_checker

# 或指定版本
uvx --from bach-email_social_media_checker@latest bach_email_social_media_checker

方式 2: 直接运行（开发模式）

python server.py

方式 3: 安装后作为命令运行

# 安装
pip install bach-email_social_media_checker

# 运行（命令名使用下划线）
bach_email_social_media_checker

配置

API 认证

此 API 需要认证。请设置环境变量:

export API_KEY="your_api_key_here"

环境变量

变量名

说明

必需

API_KEY

API 密钥

是

PORT

不适用

否

HOST

不适用

否

在 Cursor 中使用

编辑 Cursor MCP 配置文件 ~/.cursor/mcp.json:

{
  "mcpServers": {
    "bach-email_social_media_checker": {
      "command": "uvx",
      "args": ["--from", "bach-email_social_media_checker", "bach_email_social_media_checker"],
      "env": {
        "API_KEY": "your_api_key_here"
      }
    }
  }
}

在 Claude Desktop 中使用

编辑 Claude Desktop 配置文件 claude_desktop_config.json:

{
  "mcpServers": {
    "bach-email_social_media_checker": {
      "command": "uvx",
      "args": ["--from", "bach-email_social_media_checker", "bach_email_social_media_checker"],
      "env": {
        "API_KEY": "your_api_key_here"
      }
    }
  }
}

可用工具

此服务器提供以下工具:

check_email

Checks given email address.

端点: GET /check_email

参数:

技术栈

  • 传输协议: stdio

  • HTTP 客户端: httpx

许可证

MIT License - 详见 LICENSE 文件。

开发

此服务器由 API-to-MCP 工具生成。

版本: 1.0.0

Available Tools

1 tool
check_emailC

Checks given email address.

ParametersJSON Schema
NameRequiredDescriptionDefault
emailYesExample value: elonmusk@gmail.com

TDQS

C2.3/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of disclosing behavioral traits but fails entirely. It does not indicate whether this is a read-only validation, a network call to external services, potential rate limits, or what the return value indicates (boolean, string error message, object?).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely brief (4 words), which prevents verbosity, but it is under-specified rather than efficiently concise. It is front-loaded but fails to earn its place by providing actionable information about the tool's behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of output schema and annotations, the description should explain the check methodology and return behavior. For a single-parameter tool, it provides the bare minimum identification but leaves critical gaps in explaining what the tool actually returns or accomplishes.

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% (the parameter includes an example value). The description mentions 'email address' but adds no semantic value beyond the schema—no format requirements, validation rules, or domain constraints beyond what's implied by the parameter name and example.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Checks given email address' is essentially a tautology of the tool name 'check_email'. It fails to specify what 'checking' entails—whether it validates syntax, verifies existence via SMTP, checks MX records, or something else.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance provided on when to use this tool versus alternatives, prerequisites (like API keys for verification services), or when not to use it. The description is purely declarative with no contextual usage hints.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

C2.6/5.0
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 by default.

Naming Consistency5/5

A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The tool name 'check_email' follows a clear verb_noun pattern.

Tool Count2/5

One tool is too few for a server named 'Email Social Media Checker', which suggests a broader scope involving social media checks. A single tool cannot adequately cover the implied domain, leading to a significant mismatch.

Completeness1/5

The tool set is severely incomplete for the server's purpose. It only checks email addresses, missing obvious operations like checking social media platforms (e.g., Twitter, Facebook, LinkedIn) or providing comprehensive reports, which are implied by the server name.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/BACH-AI-Tools/bachai-email-social-media-checker'

If you have feedback or need assistance with the MCP directory API, please join our Discord server