# one.secureai/redaction (remote · secureai.one)

Takes the people out of text before a model sees it, and puts them back in the reply.

- Trust score: 36/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `secureai.one`: 36/100 (this document), [markdown](https://verifymcp.io/servers/one-secureai-redaction/secureai.md), [page](https://verifymcp.io/servers/one-secureai-redaction/secureai)

## Channel facts

- Endpoint: `https://secureai.one/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 91/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 0/100
  - Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- **Schema Quality & AI Usability**: 0/100
  - Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Tool Safety**: 0/100
  - Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Capabilities**: 0/100
  - Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http one-secureai-redaction 'https://secureai.one/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "one-secureai-redaction": {
      "url": "https://secureai.one/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "one-secureai-redaction": {
      "type": "http",
      "url": "https://secureai.one/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.one-secureai-redaction]
url = "https://secureai.one/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "one-secureai-redaction": {
      "type": "remote",
      "url": "https://secureai.one/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add one-secureai-redaction --url 'https://secureai.one/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  one-secureai-redaction:
    url: "https://secureai.one/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "one-secureai-redaction": {
      "Transport": "http",
      "Url": "https://secureai.one/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add one-secureai-redaction -t streamable-http -u 'https://secureai.one/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 36, −38)

- [security regression] Endpoint reachability: reachable → behind authorisation
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → unverified
- [security regression] Stability: 0.03 → unverified
- [security regression] Authorization: partial → fail
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-09-19 (score 74, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-18 (score 74)

First indexed and scored.

## MCP tools (2)

### `redact` (~144 tokens)

Redact personal details

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.

Input parameters:

- `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, required): The text to redact.

Output parameters:

- `map` (object): Stand-in to real value. Needed by restore, and stored nowhere else.
- `names_decided` (boolean): Whether the name check reached a decision. False means it could not run, not that no names were found.
- `redacted` (integer): How many values were replaced.
- `text` (string): The text with stand-ins in place of the real values.

### `restore` (~66 tokens)

Put the real details back

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.

Input parameters:

- `map` (object, required): The map returned by redact.
- `text` (string, required): Usually a model's reply, containing stand-ins.

Output parameters:

- `restored` (integer): How many values were replaced.
- `text` (string): The text with the real values put back.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/one-secureai-redaction/secureai#diagnostics

## Score history

- 2026-09-20: 36
- 2026-09-19: 74
- 2026-09-18: 74

## Common questions

### 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.

## Links

- Remote endpoint: https://secureai.one/mcp
- Authorisation metadata: https://secureai.one/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/secureaione-jpg/secure-ai-web
- Website: https://secureai.one/developers
- Changelog RSS feed: https://verifymcp.io/servers/one-secureai-redaction/secureai.xml
- Changelog JSON feed: https://verifymcp.io/servers/one-secureai-redaction/secureai.json
- HTML version of this page: https://verifymcp.io/servers/one-secureai-redaction/secureai