home / mcp / spamshieldpro mcp server

Spamshieldpro MCP Server

Provides an MCP interface to check form content via the Spamshieldpro API using a stdio-based server.

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "bach-ai-tools-bachai-spamshieldpro": {
      "command": "uvx",
      "args": [
        "--from",
        "bach-spamshieldpro",
        "bach_spamshieldpro"
      ],
      "env": {
        "API_KEY": "YOUR_API_KEY_HERE"
      }
    }
  }
}

You deploy and run the Spamshieldpro MCP Server to access the Spamshieldpro API from your applications. It runs via stdio and is configured through environment variables and MCP client configurations, letting you securely authenticate and perform the check_for_spam operation from your codebase.

How to use

You connect to this MCP server using an MCP client that supports stdio. Ensure you have your API key ready and a client that can start the MCP server process with the correct environment. You can run the server locally and point your MCP client to it, then call the available endpoint to verify form content for spam checks.

Key usage patterns include starting the MCP server with your API key and then invoking the check_for_spam tool via the MCP client. The server exposes a single endpoint for checking form content, which you can call from your application to validate user input before submission.

How to install

# Prerequisites
# - Python 3.x
# - pip

# Option A: Install from PyPI
pip install bach-spamshieldpro

# Option B: Install from source (editable)
pip install -e .

# After installation, you can start using the MCP command via uvx or direct Python entry

Run the MCP server using one of the provided methods. Choose the method that fits your workflow.

Additional configuration and notes

API authentication is required. Set your API key in the environment before starting the server.

Environment variables you will use: - API_KEY: Your Spamshieldpro API key (required)

Example MCP client configuration snippets show how to start the server with the required environment variable. Use the same approach in your own MCP client to reliably pass the API key to the server.

Cursor and Claude Desktop configurations are provided to integrate the MCP server into common tooling environments. They should reference the uvx runtime with the appropriate arguments and the API_KEY env var.

Security considerations

Keep your API_KEY secret. Do not embed it in client-side code or publicly shared configuration. Use secure storage for credentials and rotate keys periodically as part of your security hygiene.

Troubleshooting tips

If you encounter authentication errors, recheck that API_KEY is correctly exported in the environment where the MCP server is running. Verify that the MCP client is configured to pass the same key to the server.

Available tools

check_for_spam

Endpoint for checking form content via a POST request to the root endpoint.