Aigine Redact
REMOTE · REDACT.AIGINE.SE
Descriptive AI redaction for any file. GDPR + confidentiality. EU, zero retention, review optional.
Available components
Last scanned (just now)
Scores higher than 64% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Security
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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
- Supports UI / widget rendering.Pass
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.
- 4 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 3 Nov 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 5 Nov 2026 · Probed https://redact.aigine.se/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=redact.aigine.se | CN=YE1,O=Let's Encrypt,C=US | 3 Nov 2026 | 1 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 540ab0413ed0bc68b63c89c7e80040cd4a2 |
| SANs: redact.aigine.se | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of redact.aigine.se. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| se. | present | 59407 | 8 | Verified |
| aigine.se. | present | 47074 | 13 | Verified |
| redact.aigine.se. | Verified address RRset verified with the apex keys |
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=63072000; includeSubDomains |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://redact.aigine.se/mcp | Verified | 200 | |
| http (plaintext) | http://redact.aigine.se/mcp | HTTPS enforced | 301 | https://redact.aigine.se/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 →
create_upload_link Open Aigine EU Upload Widget / Link ~68
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
fetch_reviewed_document Fetch Reviewed Masked Document ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| doc_id | string | yes | The doc_id returned by propose_masking when status was 'awaiting_review'. |
No output schema declared.
No examples provided.
propose_masking Mask Document (GDPR / OSL) ~448
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
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
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.
remote · redact.aigine.se
claude mcp add --transport http se-aigine-redact 'https://redact.aigine.se/mcp'
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.