NewAI assistants over MCP

Data infrastructure built on access, not copies.

Revoked keeps addresses, documents and passwords in one vault and gives everyone else a link instead of a copy. A change reaches every link at once. A revoked link stops working.

Experimental. Test server at api.revoked.link, or self-hosted under an own domain.

Built on open standards
  • OpenID Connect
  • Passkeys
  • SD-JWT VC
  • Token Status List
  • CardDAV
  • OpenAPI 3.1
How it works

Like sharing a document. For any data.

One original, many links, and a list of who can open it. Revoked applies that to addresses, bank details, passwords, files and sign-ins.

  1. 1

    Store it once

    Data lives in one vault, on a server under the owner’s or operator’s control.

  2. 2

    Share a link

    Recipients get a link, not a copy. Services can also request data or sign people in.

  3. 3

    Change or revoke

    A change appears behind every link at once. A revoked link returns nothing from then on.

Why a link

A copy can’t be taken back.

Email attachments, screenshots and database rows are copies. Once sent, they go out of date and stay wherever they landed.

A copyA Revoked link
The value changesStays outdatedShows the new value
Access should endDeletion has to be requestedRevoked at once
Who has itUnknownListed, with views
A database leaksThe data is out for goodLinks can be revoked
Use cases

Where copies cause trouble today.

Online shops

The delivery address is read at shipping time. No address table, no password table.

HR and payroll

Tax ID and bank details arrive through one request and stay current.

Rental applications

Payslips and ID in one watermarked link, revoked once the flat is let.

Contractor access

Server passwords shared as a link that ends with the job.

Age-restricted goods

A verified “over 18” instead of a stored ID scan.

Emergency cards

A QR code that shows today’s medication and contacts, until revoked.

For developers

A button and three server routes.

Sign-in is standard OpenID Connect, so any client library works. The API covers everything the app does, with no private endpoints.

  • 0passwords stored
  • 1ID per service and person
  • 100links read per call
<script type="module"
  src="/revoked/revoked-sign-in.js"></script>

<revoked-sign-in
  start="/auth/revoked/start"
  wait="/auth/revoked/wait">
</revoked-sign-in>
Security

Built so the server holds as little as possible.

Keys stay on the device

Private keys are generated on the device. The server receives only public keys.

Optional end-to-end encryption

Encrypted text records cannot be read by the server.

Senders checked against DNS

A request in someone else’s name is flagged before anything is answered.

Open source, self-hosted

The server and app are AGPL-3.0, the SDKs MPL-2.0. Data, keys and domain stay with the operator.

Access, not copies.

Experimental software. The test server is for test data.