Skip to content
MCP server

MCP Tool Poisoning Scanner

Read-only scanner that checks remote MCP servers for tool poisoning and silent changes

Install
Pricing
Paid
Platforms
API, Web
Runs
Remotely
Version
1.1.0
Listing updated
1 day ago

About MCP Tool Poisoning Scanner

MCP Tool Poisoning Scanner is a paid MCP server for security. It runs as a hosted remote server, so there is nothing to install locally.

Before an agent trusts a new MCP server, this Actor connects to it the way an agent would and reads every tool, prompt and resource definition. It then looks for hidden instructions in that metadata: tags telling the model to read SSH keys or config files, cross-tool shadowing such as forcing a BCC on emails, secrecy phrases, side-channel parameters that leak history, invisible Unicode, whitespace padding and prompt injection in ten languages.

It only calls initialize, tools/list, prompts/list and resources/list and never runs a tool. Each server gets a risk level of none, low, medium or high, a list of risky tools and findings with the exact text. With change tracking on and a schedule, it reports tools that were modified since the last scan, the so-called rug pull. Local stdio servers can be checked by pasting their tools/list JSON.

The author is clear that it is a static rule-based scanner: a server that misbehaves only at runtime will not be caught.

Install

Run in a terminal

claude mcp add --transport http mcp-poisoning-scanner 'https://mcp.apify.com/?tools=bigochelo/mcp-poisoning-scanner'

Add to Settings → Connectors → Add custom connector

https://mcp.apify.com/?tools=bigochelo/mcp-poisoning-scanner
Install in CursorOpens Cursor, which asks you to confirm. Or add it by hand:

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "mcp-poisoning-scanner": {
      "url": "https://mcp.apify.com/?tools=bigochelo/mcp-poisoning-scanner"
    }
  }
}
Install in VS CodeOpens VS Code, which asks you to confirm. Or add it by hand:

Add to .vscode/mcp.json

{
  "servers": {
    "mcp-poisoning-scanner": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=bigochelo/mcp-poisoning-scanner"
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "mcp-poisoning-scanner": {
      "serverUrl": "https://mcp.apify.com/?tools=bigochelo/mcp-poisoning-scanner"
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "mcp-poisoning-scanner": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=bigochelo/mcp-poisoning-scanner"
    }
  }
}

What it does

Poisoning detection
Flags hidden instructions, credential access and shadowing.
Rug-pull tracking
Reports tools that changed since the previous scan.
Invisible text checks
Decodes zero-width characters and Unicode tag smuggling.
Local server support
Accepts pasted tools/list JSON for stdio servers.
Read-only
Never executes a tool on the scanned server.
Risk levels
Per-server riskLevel with located findings.

Good for

  • Vet a new MCP server before adding it to Cursor or Claude
  • Monitor dependencies for silent tool changes
  • Audit your own server before publishing
  • Gate a CI pipeline on the risk level

Pricing

Paid

Pay per event: $0.01 per server scanned plus $0.003 per run, via Apify

Prices change. Check apify.com before you buy.

MCP Tool Poisoning Scanner FAQ

What does it cost?

About $0.01 per server scanned plus $0.003 per run; servers that cannot be scanned are not charged.

Does it run my tools?

No, it only lists tools, prompts and resources.

What can it miss?

Runtime behaviour that the server's metadata does not reveal.

Can it scan local servers?

Yes, by pasting the tools/list result.

Is MCP Tool Poisoning Scanner free?

No. MCP Tool Poisoning Scanner is a paid product.

How do I add MCP Tool Poisoning Scanner to Claude Code?

Run this command in your terminal: claude mcp add --transport http mcp-poisoning-scanner 'https://mcp.apify.com/?tools=bigochelo/mcp-poisoning-scanner'

What are the best alternatives to MCP Tool Poisoning Scanner?

The closest alternatives to MCP Tool Poisoning Scanner are REA, Codebase Memory, GitHub, Serena MCP: the IDE for your agent and XERJ.

Alternatives to MCP Tool Poisoning Scanner

  1. REA

    MCP server

    CLI and MCP server that lets coding agents reverse engineer apps and binaries

    Runs locally
    • Open source
    • 464K GitHub stars
    • Developer tools
  2. Codebase Memory

    MCP server

    Local MCP server that builds a code knowledge graph for AI coding agents

    Runs locally
    • Open source
    • 48.7K GitHub stars
    • Knowledge and memory
  3. GitHub

    MCP server

    Official MCP server connecting AI assistants to GitHub repos, issues and workflows

    Not checked yet
    • Remote
    • Open source
    • 34.5K GitHub stars
    • Developer tools
  4. MCP toolkit giving coding agents symbol-level code retrieval and editing

    Runs locally
    • Open source
    • 31.5K GitHub stars
    • Developer tools
  5. XERJ

    MCP server

    Local search engine for AI agents with cited answers over your code and docs

    Runs locally
    • Open source
    • 19.2K GitHub stars
    • Knowledge and memory
  6. Ouroboros

    MCP server

    Spec-first layer that pins requirements and verifies results of AI coding agent work

    Runs locally
    • Open source
    • 6.4K GitHub stars
    • Developer tools