Skip to main content
Glama
BACH-AI-Tools

Spamshieldpro MCP Server

by BACH-AI-Tools
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

Spamshieldpro MCP Server

English | 简体中文 | 繁體中文

用于访问 Spamshieldpro API 的 MCP 服务器。

🚀 使用 EMCP 平台快速体验

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

快速开始：

  1. 🌐 访问 EMCP 平台

  2. 📝 注册并登录账号

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

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

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

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

EMCP 平台优势：

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

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

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

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

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

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

Related MCP server: Malicious Scanner MCP Server

简介

这是一个 MCP 服务器，用于访问 Spamshieldpro API。

  • PyPI 包名: bach-spamshieldpro

  • 版本: 1.0.0

  • 传输协议: stdio

安装

从 PyPI 安装:

pip install bach-spamshieldpro

从源码安装:

pip install -e .

运行

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

# 运行（uvx 会自动安装并运行）
uvx --from bach-spamshieldpro bach_spamshieldpro

# 或指定版本
uvx --from bach-spamshieldpro@latest bach_spamshieldpro

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

python server.py

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

# 安装
pip install bach-spamshieldpro

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

配置

API 认证

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

export API_KEY="your_api_key_here"

环境变量

变量名

说明

必需

API_KEY

API 密钥

是

PORT

不适用

否

HOST

不适用

否

在 Cursor 中使用

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

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

在 Claude Desktop 中使用

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

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

可用工具

此服务器提供以下工具:

check_for_spam

endpoint for checking form content

端点: POST /

技术栈

  • 传输协议: stdio

  • HTTP 客户端: httpx

许可证

MIT License - 详见 LICENSE 文件。

开发

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

版本: 1.0.0

Available Tools

1 tool
check_for_spamC

endpoint for checking form content

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions 'checking' but does not disclose behavioral traits like whether it's read-only, what it returns (e.g., a score, boolean, details), error handling, or performance aspects. This leaves the agent with minimal insight into how the tool behaves beyond its basic purpose.

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

Conciseness4/5

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

The description is a single, efficient phrase ('endpoint for checking form content') that is front-loaded and wastes no words. However, it could be slightly more specific (e.g., 'Check form content for spam') to improve clarity without losing conciseness.

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 no annotations, no output schema, and a simple tool with 0 parameters, the description is incomplete. It states the purpose but lacks details on behavior, return values, or usage context, making it inadequate for an agent to fully understand how to invoke and interpret results effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and schema description coverage is 100%, so there are no parameters to document. The description does not add param info, but with no parameters, a baseline of 4 is appropriate as there is no gap to compensate for, and the description does not mislead about inputs.

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

Purpose3/5

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

The description 'endpoint for checking form content' states a general purpose (checking form content) but lacks specificity about what 'checking' entails (e.g., validation, spam detection, completeness). It does not distinguish from siblings as there are none, but the verb 'checking' is somewhat vague compared to more precise alternatives like 'validate' or 'scan for spam'.

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?

The description provides no guidance on when to use this tool, such as prerequisites, typical scenarios, or alternatives. With no sibling tools, it avoids confusion, but it fails to specify context like 'use this before submitting forms' or 'when user input is untrusted,' leaving usage unclear.

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. Dates show when Glama detected each change.

  1. 1 tool updatev1.0.0
    • First observedcheck_for_spam
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

C2.9/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'check_for_spam' has a singular, clear purpose that cannot be confused with any other tool in the set.

Naming Consistency5/5

The single tool name 'check_for_spam' follows a clear verb_noun pattern, and with only one tool, consistency is inherently perfect. There are no other tools to compare against, so no inconsistencies can arise.

Tool Count2/5

A single tool for a server named 'Spamshieldpro' suggests a very limited scope, likely insufficient for comprehensive spam detection or management tasks. This feels thin and may leave obvious gaps in functionality, such as updating spam lists or handling different types of spam checks.

Completeness1/5

The tool set is severely incomplete for a spam-related domain. With only a 'check_for_spam' tool, there are no operations for managing spam data (e.g., add to blacklist, remove false positives), configuring settings, or handling different spam types, leading to significant gaps that will hinder agent effectiveness.

Maintenance

ActivityInactive
ResponsivenessNo issues

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-spamshieldpro'

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