Runnel MCP server gates share-link reads behind explicit consent, encrypts destinations client-side
FormalAct2203 · reddit · 2026-10-13
A developer launched an MCP server for Runnel, a share-link service, with a consent-first design: by default the assistant can mint and revoke links, but reading where links point is a separate, explicit consent step.
Runnel links act as kill switches — they can expire, stop after N opens, or be revoked in seconds. The browser encrypts destinations and the server stores only ciphertext it can't read (unless you pick proxy mode, which decrypts in memory to stream files). Four tools: mintlink, listlinks, revokelink, getusage.
Two modes:
- Remote (app.runnel.link/mcp) with OAuth 2.1; consent stores a view key encrypted under the issued access token, revocable in one step.
- Local via npx -y @runnel-link/cli mcp; the private half of the view key never leaves your machine.
Included in every plan, free tier onwards. The author asks MCP builders how they handle tools needing read access to sensitive data.
More from coding & agent
- Claude cut a 2.6-hour video export to 20 minutes — but only after being told to rebuild the server — byhewar · 2026-10-23
- 3 flight-booking rules my AI agent checks that I'd never do by hand — Efistoffeles · 2026-10-23
- OpenJet claims Qwen3.8-27B coding runs 1.9x faster than llama.cpp on one RTX 3090 — JeremyCMorgan · 2026-10-23
- Building an autonomous SEO agent in Hermes with three skills: programmatic pages, Keywords Everywhere, DataForSEO — EXM7777 · 2026-10-23
- Building a sports betting AI agent with onchain execution and human approval by default: architecture and lessons — Dry-Comfortable-2678 · 2026-10-23
- How do you audit AI agent decisions in regulated workflows? A field survey — Ok_Way_1993 · 2026-10-23