aigine-redact
Registry code: ffb5e50c576566c0
# Aigine Redact – Global GDPR, Trade-Secret & OSL Document Sanitization (Zero Retention)
Sanitize documents containing personal data (GDPR — applies globally under Art. 3(2) whenever EU/EEA individuals' data appears) or confidential information (corporate trade secrets & Swedish OSL 2009:400) in the EU using specialized descriptive encoder AI (98%+ accuracy, flattened irreversible PDF redaction) BEFORE reading them into any generative LLM. Full compliance & scientific rationale: https://redact.aigine.se/SKILL.md
- endpoint
- https://redact.aigine.se/mcp
- protocol
- http-sse ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is aigine-redact live?
- Yes — it answered the hub's last check (checked 53m ago). It answered 100% of checks over the last 30 days.
- Is aigine-redact free to use?
- Not measured yet.
- What tools does aigine-redact have?
- 3 tools: create_upload_link, propose_masking, fetch_reviewed_document.
- Is aigine-redact safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 3 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
create_upload_link unknown never probed
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linespropose_masking unknown never probed
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
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "policy": { "enum": [ "Privacy", "Secrecy", "Privacy and Secrecy" ], "type": "string", "description": "Masking policy: 'Privacy' (GDPR default), 'Secrecy' (OSL/confidential), or 'Privacy and Secrecy' (both)." }, "file_url": { "type": "string", "description": "Direct HTTPS URL to fetch the source document from (e.g. pre-signed cloud URL)." }, "filename": { "type": "string", "description": "Original filename including extension (e.g. 'report.pdf' or 'contract.docx')." }, "upload_id": { "type": "string", "description": "Upload ID from create_upload_link or POST /mcp/api/upload." }, "document_base64": { "type": "string", "description": "Base64-encoded document bytes (use for programmatic pipelines or small chat-attached files <= 45 KB when sandbox network egress is disabled)." }, "require_human_review": { "type": "boolean", "default": false, "description": "MUST be false for autonomous agents. Set true ONLY when a live human wants interactive web GUI review." } } }arguments 36 linesfetch_reviewed_document unknown never probed
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "doc_id" ], "properties": { "doc_id": { "type": "string", "description": "The doc_id returned by propose_masking when status was 'awaiting_review'." } } }arguments 13 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idffb5e50c576566c0.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/ffb5e50c576566c0/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/ffb5e50c576566c0?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.