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.

PII Shield

REMOTE · PIISHIELD.AI

Redact names, IDs, emails, phones and card numbers before they reach the model; restore them after.

Available components

+3 this week 71 Trust /100

Last scanned (14 hours ago)

Scores higher than 56% of remote servers

Reachable. Last reached 21 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 Security63
Transport & Reachability100
Schema Quality & AI Usability72
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 760 tokens (~126/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 74% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 19 Nov 26 +1

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

  • 17 Nov 26 +1

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

  • 15 Nov 26 +1

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

  • 13 Nov 26 +1

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

  • 11 Nov 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.

  • 9 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 8 Nov 26 65

    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 21 Nov 2026 · Probed https://piishield.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=piishield.ai CN=WE1,O=Google Trust Services,C=US 2 Nov 2026 31 Jan 2027 ECDSA 256 ECDSA-SHA256 9e4ade1c96a0faec130838fef5ce90f7
SANs: piishield.ai
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 piishield.ai. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814 8 Verified
piishield.ai. No DS 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
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src 'self' data: https:; connect-src 'self'; frame-ancestors 'none'; base-uri 'self'; form-action 'self'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://piishield.ai/mcp Verified 200
http (plaintext) http://piishield.ai/mcp HTTPS enforced 301 https://piishield.ai/mcp
MCP tools · 6 exposed · ~710 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
detect_pii ~69

Report what personal data appears in text (counts by type) without returning the raw values. Use to check whether text is safe to share. NOTE: detection is automated and is not a guarantee; a clean result does not prove the text is free of personal data.

NameTypeReqDescription
textstringyes–

No output schema declared.

No examples provided.

get_coverage ~57

Show your workspace's current PII coverage (which detectors are on, custom terms, custom patterns). Uses the workspace key from your MCP server URL.

NameTypeReqDescription
shield_keystring–optional — only if not already in the server URL

No output schema declared.

No examples provided.

list_detectors ~37

List the PII types this shield can mask, and confirm custom regex/terms are supported. Call this to see what coverage is available.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

redact ~224

Redact personal data (email, phone, cards, SA ID, SSN, IP, IBAN, names, custom terms) from text, replacing each value with a stable token like [EMAIL_1]. Call this before putting sensitive text into a prompt or context. NOTE: detection is automated and is not a guarantee; it can miss personal data. Review the output before relying on it.

NameTypeReqDescription
customPatternsarray–Custom PII as regexes, e.g. {type:'EMPID', pattern:'EMP-\\d{5}'}.
customTermsarray–Extra literal terms to always mask (custom PII).
detectorsobject–Optional map of detector→bool to override defaults.
previewboolean–Dry run: return what WOULD be redacted (type, confidence, rationale) without changing the text or consuming quota.
rejectarray–Finding ids (from a preview) to leave unredacted — a human said 'not PII here'.
textstringyesThe text to redact.

No output schema declared.

No examples provided.

redact_document ~189

Redact PII from an uploaded file or document before sharing it with an AI. Works on PDFs, Word (.docx), Excel (.xlsx), and text-based files (txt, csv, json, code, transcripts, logs). Pass base64 file data with media_type/filename, OR raw text. Returns the redacted text and counts. Requires your workspace key (via the MCP server URL). NOTE: detection is automated and is not a guarantee; it can miss personal data. Review the file yourself before sharing it.

NameTypeReqDescription
base64string–base64-encoded file bytes
customPatternsarray––
customTermsarray––
detectorsobject––
filenamestring––
media_typestring–e.g. application/pdf, text/csv
textstring–or raw text instead of a file

No output schema declared.

No examples provided.

set_coverage ~134

Change what this workspace masks, right from your chat. Turn detectors on/off (e.g. enable PERSON name masking), add always-mask terms, or add custom PII as regex (e.g. employee IDs 'EMP-\\d{5}'). Uses the workspace key from your MCP server URL.

NameTypeReqDescription
customPatternsarray–custom PII as regex
customTermsarray–literal terms to always mask
detectorsobject–map of detector→bool, e.g. {"PERSON":true}
shield_keystring–optional — only if not already in the server URL

No output schema declared.

No examples provided.

Install

How do I install the PII Shield MCP server?

PII Shield is a hosted endpoint at https://piishield.ai/mcp, 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 · piishield.ai

# add to Claude Code
claude mcp add --transport http ai-piishield-pii-shield 'https://piishield.ai/mcp'
Common questions

What is the PII Shield MCP server?

PII Shield is an MCP server listed in the public MCP registry as ai.piishield/pii-shield. Redact names, IDs, emails, phones and card numbers before they reach the model; restore them after. This page covers its hosted endpoint (https://piishield.ai/mcp).

Is the PII Shield MCP server safe to use?

PII Shield scores 71 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 PII Shield MCP server expose?

PII Shield exposes 6 tools: redact, detect_pii, redact_document, list_detectors, get_coverage, set_coverage. Their descriptions and schemas cost roughly 710 tokens of context every time the server is loaded.

Does the PII Shield MCP server require authentication?

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

Is the PII Shield MCP server still maintained?

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

What did VerifyMCP test on the PII Shield MCP server?

VerifyMCP ran 12 checks on PII Shield, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about PII Shield: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.