Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

MCP Security Sanitizer

REMOTE · MCP-SECURITY-SANITIZER-SERVER.ONRENDER.COM

Redacts common secrets, email addresses, and phone numbers.

+4 this week 59 Trust /100

Last scanned (20 hours ago)

Scores higher than 43% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Security

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability40
Schema Quality & AI Usability59
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 93 tokens (~31/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
  • Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 23 Oct 26 53

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Nov 2026 · Probed https://mcp-security-sanitizer-server.onrender.com/sse

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=onrender.com CN=WE1,O=Google Trust Services,C=US 21 Sept 2026 20 Dec 2026 ECDSA 256 ECDSA-SHA256 6eb1e3fe7d0631ea1337bfa4a321c137
SANs: onrender.com, *.onrender.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp-security-sanitizer-server.onrender.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
onrender.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
sse https://mcp-security-sanitizer-server.onrender.com/sse Verified 200
http (plaintext) http://mcp-security-sanitizer-server.onrender.com/sse HTTPS enforced 301 https://mcp-security-sanitizer-server.onrender.com/sse
MCP tools · 3 exposed · ~93 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
audit_text_for_risks ~30

Count recognizable secrets, email addresses, and phone numbers.

NameTypeReqDescription
textstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

mask_api_keys_and_secrets ~35

Redact OpenAI-style API keys, bearer tokens, and common named secrets.

NameTypeReqDescription
textstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

mask_pii_data ~28

Redact email addresses and common North American phone numbers.

NameTypeReqDescription
textstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

Install

How do I install the MCP Security Sanitizer server?

MCP Security Sanitizer is a hosted endpoint at https://mcp-security-sanitizer-server.onrender.com/sse, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp-security-sanitizer-server.onrender.com

# add to Claude Code
claude mcp add --transport http saurabhdrh-mcp-security-sanitizer 'https://mcp-security-sanitizer-server.onrender.com/sse'
Common questions

What is the MCP Security Sanitizer server?

MCP Security Sanitizer is listed in the public MCP registry as io.github.saurabhdrh/mcp-security-sanitizer. Redacts common secrets, email addresses, and phone numbers. This page covers its hosted endpoint (https://mcp-security-sanitizer-server.onrender.com/sse).

Is the MCP Security Sanitizer server safe to use?

MCP Security Sanitizer scores 59 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the MCP Security Sanitizer server expose?

MCP Security Sanitizer exposes 3 tools: mask_api_keys_and_secrets, mask_pii_data, audit_text_for_risks. Their descriptions and schemas cost roughly 93 tokens of context every time the server is loaded.

Does the MCP Security Sanitizer server require authentication?

No. We connected to MCP Security Sanitizer without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the MCP Security Sanitizer server still maintained?

MCP Security Sanitizer is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.