Tracepiishield MCP

What tracepiishield-mcp MCP server does

The tracepiishield-mcp MCP server provides hosted tools for reviewing sensitive information in LLM traces and tool payloads. Its scope covers PII scanning, payload redaction, sensitive-field classification, privacy receipts, and trace audit exports.

The service is intended for workflows where trace content or tool inputs need to be checked and potentially redacted before they leave review. It is a paid remote service rather than a package whose production implementation is included in this repository.

How it works

Clients connect to the hosted MCP endpoint at https://tracepiishield.clauxel.com/mcp. The endpoint uses Streamable HTTP, and clients send MCP JSON-RPC requests to invoke the available tools. Production calls must include a bearer token in the request header:

Authorization: Bearer <token>

The token is obtained through the product website after selecting a plan and creating or requesting access. Browser requests without authentication return a JSON error rather than internal service details.

Setup and configuration

To use the tracepiishield-mcp MCP server, open the product website, choose a plan, and obtain an API token. Add the MCP endpoint to a client that supports Streamable HTTP remote servers, then configure that client to send the bearer token with requests.

The repository does not provide a local installation path or production source code. It serves as public documentation and a directory-submission reference for the hosted service. The README does not specify environment variable names, a local command, or client-specific configuration files.

Tools and capabilities

The service exposes these MCP tools:

• scan_trace_pii for scanning trace content for PII.
• redact_tool_payload for redacting tool payload content.
• classify_sensitive_field for classifying a field’s sensitivity.
• issue_pii_receipt for issuing a PII-related privacy receipt.
• export_trace_audit for exporting a trace audit.

Together, these operations cover detection, redaction, field classification, receipt generation, and audit export. The provided material does not define each tool’s input schema, output schema, detection categories, or redaction rules, so those details should be confirmed from the hosted service.

Limitations and notes

The tracepiishield-mcp MCP server is paid and hosted remotely. A production bearer token is required, and the README does not describe an offline mode or self-hosted deployment. The repository also does not contain the private production source code.

No particular MCP client is named in the README. Compatibility therefore depends on whether the chosen client supports Streamable HTTP remote MCP servers and bearer-token configuration. Pricing and access are managed through the product website.