Execute data-poisoning-detector-mcp

io.github.EvozimPublished by GitHub account Evozimv2.0.0Updated Oct 24, 2026

Premium agentic endpoint for data-poisoning-detector-mcp.

VerifiedSSEWeb executableSecurity & Monitoring

Overview

AI-generated overview

A remote MCP endpoint for a data-poisoning detector, reached over SSE and paid per use through an x402 USDC settlement signature.

What you can do
Connects an assistant to a hosted data-poisoning detection service over SSE, with no tools listed in the manifest. The provider describes it as a premium agentic endpoint for data-poisoning detection. Access is metered: each request is settled on-chain in USDC on Base Mainnet through an x402 V2 payment signature.
When to use it
Consider it when you want an assistant to check data for poisoning through a hosted service and are willing to pay per request in USDC on Base Mainnet. It is not suitable if you need a free, self-hosted, or tool-documented server.
Requirements
A remote SSE endpoint at the provider's host; nothing is installed locally. A wallet able to produce an EIP-3009 TransferWithAuthorization signature, supplied in the Payment-Signature header, plus USDC on Base Mainnet for settlement. No account or API key is declared.
Before you install
Every use costs money: the Payment-Signature header carries a signed authorization to transfer 0.22 USDC on Base Mainnet, so treat it as a spending credential and set limits. The signature is a wallet authorization and should not be shared or logged. No tools are listed, so what the endpoint actually does with your data is unverified.

Installation

In SourceWeft

  1. Open Execute data-poisoning-detector-mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Evozim%2Fdata-poisoning-detector-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "execute-data-poisoning-detector": {
      "type": "sse",
      "url": "https://api.m2mcent.com/data-poisoning-detector-mcp/sse"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v2.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.