# Aigine Redact (remote · redact.aigine.se)

Descriptive AI redaction for any file. GDPR + confidentiality. EU, zero retention, review optional.

- Trust score: 75/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `redact.aigine.se`: 75/100 (this document), [markdown](https://verifymcp.io/servers/se-aigine-redact/redact.md), [page](https://verifymcp.io/servers/se-aigine-redact/redact)

## Channel facts

- Endpoint: `https://redact.aigine.se/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.2`

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

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - 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**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1601 tokens (~320/item across 5 items; 3 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the Aigine Redact MCP server?

Aigine Redact is a hosted endpoint at https://redact.aigine.se/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 se-aigine-redact 'https://redact.aigine.se/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "se-aigine-redact": {
      "url": "https://redact.aigine.se/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "se-aigine-redact": {
      "type": "http",
      "url": "https://redact.aigine.se/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.se-aigine-redact]
url = "https://redact.aigine.se/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "se-aigine-redact": {
      "type": "remote",
      "url": "https://redact.aigine.se/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add se-aigine-redact --url 'https://redact.aigine.se/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  se-aigine-redact:
    url: "https://redact.aigine.se/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "se-aigine-redact": {
      "Transport": "http",
      "Url": "https://redact.aigine.se/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add se-aigine-redact -t streamable-http -u 'https://redact.aigine.se/mcp'
```

### Other

```json
{
  "mcpServers": {
    "se-aigine-redact": {
      "type": "http",
      "url": "https://redact.aigine.se/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-11-04 (score 75, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-03 (score 74)

First indexed and scored.

## MCP tools (3)

### `create_upload_link` (~68 tokens)

Open Aigine EU Upload Widget / Link

Opens an interactive inline Drag & Drop EU upload widget directly inside supporting chat clients (MCP Apps) AND returns a temporary zero-retention EU upload URL (upload_url) so a user can upload a PDF, DOCX, PPTX, or image directly to Aigine in the EU.

### `propose_masking` (~448 tokens)

Mask Document (GDPR / OSL)

Identify and mask personal data (GDPR direct, indirect, and sensitive Art. 9) and confidential information (OSL / trade secrets) in documents (PDF, DOCX, PPTX, images) in the EU using specialized descriptive encoder AI (98%+ accuracy, flattened irreversible PDF, strict zero retention). RULES: (1) AUTONOMOUS AGENTS: MUST set require_human_review=false and MUST NOT ask questions; default policy is 'Privacy'. Upload via POST /mcp/api/upload first to get upload_id, or pass file_url / document_base64. (2) CHAT ATTACHMENTS: If a human already attached a file in chat, try uploading it via POST /mcp/api/upload if outbound network works, or pass document_base64 if <= 45 KB; otherwise call create_upload_link to open the inline upload widget. (3) INTERACTIVE HUMAN CHAT: Ask policy (Privacy, Secrecy, or Privacy and Secrecy) and whether they want GUI validation (require_human_review=true, clicking 'Redact' then 'Open redacted PDF') or direct PDF (false), unless already stated. Guide: https://redact.aigine.se/SKILL.md | Terms: https://aigine.se/cloud-terms

Input parameters:

- `document_base64` (string): Base64-encoded document bytes (use for programmatic pipelines or small chat-attached files <= 45 KB when sandbox network egress is disabled).
- `file_url` (string): Direct HTTPS URL to fetch the source document from (e.g. pre-signed cloud URL).
- `filename` (string): Original filename including extension (e.g. 'report.pdf' or 'contract.docx').
- `policy` (string): Masking policy: 'Privacy' (GDPR default), 'Secrecy' (OSL/confidential), or 'Privacy and Secrecy' (both).
- `require_human_review` (boolean): MUST be false for autonomous agents. Set true ONLY when a live human wants interactive web GUI review.
- `upload_id` (string): Upload ID from create_upload_link or POST /mcp/api/upload.

### `fetch_reviewed_document` (~105 tokens)

Fetch Reviewed Masked Document

INTERACTIVE HUMAN MODE ONLY (autonomous agents must never call this tool). After a human finishes validating at review_url and clicks 'Redact' (where they can also click 'Open redacted PDF' directly in the browser), call this tool with doc_id to get a temporary download_url for the masked PDF and immediately delete the document from the processing server.

Input parameters:

- `doc_id` (string, required): The doc_id returned by propose_masking when status was 'awaiting_review'.

## Diagnostics

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

## Score history

- 2026-11-05: 75
- 2026-11-04: 75
- 2026-11-03: 74

## Common questions

### What is the Aigine Redact MCP server?

Aigine Redact is an MCP server listed in the public MCP registry as se.aigine/redact. Descriptive AI redaction for any file. GDPR + confidentiality. EU, zero retention, review optional. This page covers its hosted endpoint (https://redact.aigine.se/mcp).

### Is the Aigine Redact MCP server safe to use?

Aigine Redact scores 75 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 Aigine Redact MCP server expose?

Aigine Redact exposes 3 tools: create_upload_link, propose_masking, fetch_reviewed_document. Their descriptions and schemas cost roughly 621 tokens of context every time the server is loaded.

### Does the Aigine Redact MCP server require authentication?

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

### Is the Aigine Redact MCP server still maintained?

Aigine Redact is still listed as active in the MCP registry. We last reached this channel on 5 November 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://redact.aigine.se/mcp
- Website: https://aigine.se/en
- Changelog RSS feed: https://verifymcp.io/servers/se-aigine-redact/redact.xml
- Changelog JSON feed: https://verifymcp.io/servers/se-aigine-redact/redact.json
- HTML version of this page: https://verifymcp.io/servers/se-aigine-redact/redact