READER.IIIK

A Markdown reader with a mission: to get out of the way.

Drop a file (.md / .txt / .markdown), paste copied Markdown or a URL from the clipboard to parse its contents directly in your browser.

Effortless annotation

Select a passage and start typing. Review, edit or delete your notes from the notes panel (press → to show it). Press ↑ and ↓ to navigate them, or use the mouse to go directly where you want.

Export anything

Download or copy a summary of your notes, the annotated document or the original. Everything exports as plain Markdown, and an annotated export can be reimported later with every note intact.

Account-less sharing

Easily share a document as an encrypted hosted copy you can delete at any time¹. A document seats up to six annotators: invite people and their notes appear beside yours, or hand out a view-only link that reads but doesn't allow annotation.

To avoid accounts, READER.IIIK relies on encryption keys generated on request: your browser tab is the authentication. Close the tab and the document can no longer be deleted on demand. Documents auto-delete from the server 30 days after creation.

Agents are first-class readers

The annotation format was designed for LLMs first: an agent shares a draft through the READER.IIIK MCP, you read it here and write your feedback, and when you are done, just ask your agent to pull your notes. Agents have a reserved user of their own to annotate with if needed (one agent per document).

claude mcp add reader3000 --scope user -- npx -y reader3000-mcp

For Codex and other agents, see the MCP repository.

Easy integration

Sending content into the reader from your agents, your scripts, or anything that can make a link is easy. The integration guide describes every way to do it.

Privacy stance

READER.IIIK makes a best effort to protect your privacy whenever possible: shared documents are stored encrypted, and the server never holds the key. Only you and the people you share the link with do. That means you must be careful about not losing it: close the tab that created a share without keeping its link, and the document is lost forever. The MCP for agents stores the keys for documents created with it, so an agent can delete them upon request, even from a different session.

Think of READER.IIIK sharing as a convenience with best-effort privacy: no accounts means that any person with the sharing link can see the document. You cannot revoke that access. You can only delete the entire document.

Documents shared through the MCP are briefly seen as plaintext by the READER.IIIK gateway (the server that provides the encryption). This is a transient step that happens each time an agent creates, reads or revises. Nothing is stored along the way, and what sits on the server is only the encrypted file. Documents shared from the browser are encrypted on your device, and no server ever sees them in plaintext.

The account-less nature of READER.IIIK sharing is a choice: we cannot lose information we don't have access to. Sharing is a privacy-aware, best-effort convenience, not a guarantee. It's good practice to never upload anything mission-critical to the internet, no matter how good the promises.