one.secureai/redaction
REMOTE · SECUREAI.ONE · SCANNED SEP 20
Takes the people out of text before a model sees it, and puts them back in the reply.
Available components
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 Security91
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
How do I install the one.secureai/redaction MCP server?
one.secureai/redaction is a hosted endpoint at https://secureai.one/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 · secureai.one
claude mcp add --transport http one-secureai-redaction 'https://secureai.one/mcp'
{
"mcpServers": {
"one-secureai-redaction": {
"url": "https://secureai.one/mcp"
}
}
} {
"servers": {
"one-secureai-redaction": {
"type": "http",
"url": "https://secureai.one/mcp"
}
}
} [mcp_servers.one-secureai-redaction] url = "https://secureai.one/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"one-secureai-redaction": {
"type": "remote",
"url": "https://secureai.one/mcp",
"enabled": true
}
}
} openclaw mcp add one-secureai-redaction --url 'https://secureai.one/mcp' --transport streamable-http
mcp_servers:
one-secureai-redaction:
url: "https://secureai.one/mcp" {
"McpServers": {
"one-secureai-redaction": {
"Transport": "http",
"Url": "https://secureai.one/mcp"
}
}
} assistant mcp add one-secureai-redaction -t streamable-http -u 'https://secureai.one/mcp'
{
"mcpServers": {
"one-secureai-redaction": {
"type": "http",
"url": "https://secureai.one/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 20 Sept 26 −38
- Endpoint reachability: reachable → behind authorisation ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Stability: 0.03 → unverified ▼ security
- Authorization: partial → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 19 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 18 Sept 26 74
First indexed and scored.
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 20 Sept 2026 · Probed https://secureai.one/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=secureai.one | CN=YR2,O=Let's Encrypt,C=US | 9 Aug 2026 | 7 Nov 2026 | RSA 2048 | SHA256-RSA | 6a2e29b158c37efbdbf8865e613b2fd22c5 |
| SANs: secureai.one | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of secureai.one. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| one. | present | 64939 | 8 | Verified |
| secureai.one. | present | 881 | 13 | Verified |
| secureai.one. | Verified address RRset verified with the apex keys |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer realm="Secure AI"
Bearer realm="Secure AI"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| content-security-policy | default-src 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'self'; form-action 'self'; script-src 'self' 'nonce-1UXhDxFX4qHgZTU22DuDWg==' 'unsafe-inline' 'wasm-unsafe-eval' https://apis.google.com https://accounts.google.com https://js.stripe.com https://va.vercel-scripts.com https://www.googletagmanager.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https:; font-src 'self' data:; media-src 'self' blob: data:; connect-src 'self' data: https://*.googleapis.com wss://*.googleapis.com https://*.google.com https://*.firebaseapp.com https://*.firebaseio.com wss://*.firebaseio.com https://api.stripe.com https://secure-ai-worker.secureai-one.workers.dev https://enclave.secureaione.com https://va.vercel-scripts.com https://vitals.vercel-insights.com https://www.googletagmanager.com https://www.google-analytics.com https://*.google-analytics.com https://*.analytics.google.com; frame-src 'self' https://*.google.com https://*.firebaseapp.com https://js.stripe.com https://hooks.stripe.com |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(self), geolocation=(), payment=() |
| www-authenticate | Bearer realm="Secure AI" |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://secureai.one/mcp | Auth required | 401 | |
| http (plaintext) | http://secureai.one/mcp | HTTPS enforced | 308 | https://secureai.one/mcp |
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 →
redact Redact personal details ~144
Replace the people in a piece of text — names, emails, phone numbers, addresses, card and account numbers — with plausible stand-ins, before the text is sent to a model or a third party. Returns the redacted text and a map. Keep the map: it is the only way to put the real values back, and it is not stored anywhere.
| Name | Type | Req | Description |
|---|---|---|---|
| allow | array | – | Terms to leave as written — a shared mailbox, a product name a detector mistakes for a person. |
| strict | boolean | – | Refuse rather than proceed when the name check cannot run. Use for records rather than one person's messages. |
| text | string | yes | The text to redact. |
| Name | Type | Req | Description |
|---|---|---|---|
| map | object | yes | Stand-in to real value. Needed by restore, and stored nowhere else. |
| names_decided | boolean | yes | Whether the name check reached a decision. False means it could not run, not that no names were found. |
| redacted | integer | yes | How many values were replaced. |
| text | string | yes | The text with stand-ins in place of the real values. |
No examples provided.
restore Put the real details back ~66
Reverse a redaction using the map it returned. Use this on a model's reply so the reader sees what they actually wrote rather than the stand-ins.
| Name | Type | Req | Description |
|---|---|---|---|
| map | object | yes | The map returned by redact. |
| text | string | yes | Usually a model's reply, containing stand-ins. |
| Name | Type | Req | Description |
|---|---|---|---|
| restored | integer | yes | How many values were replaced. |
| text | string | yes | The text with the real values put back. |
No examples provided.
What is the one.secureai/redaction MCP server?
one.secureai/redaction is an MCP server listed in the public MCP registry as one.secureai/redaction. Takes the people out of text before a model sees it, and puts them back in the reply. This page covers its hosted endpoint (https://secureai.one/mcp).
Is the one.secureai/redaction MCP server safe to use?
one.secureai/redaction scores 36 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 one.secureai/redaction MCP server expose?
one.secureai/redaction exposes 2 tools: redact, restore. Their descriptions and schemas cost roughly 210 tokens of context every time the server is loaded.
Does the one.secureai/redaction MCP server require authentication?
Yes. one.secureai/redaction asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the one.secureai/redaction MCP server still maintained?
one.secureai/redaction is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.