MCP by Noir

NOTHING STORED

MODEL CONTEXT PROTOCOL

Every NOIR app, inside your AI assistant.

One address gives Claude — or any MCP client — MELTER, BITOW, DOPPLER and GATO as tools. No account, no key, nothing to install.

CONNECT

CLAUDE
Open Settings → Connectors, add a custom connector, name it NOIR, and paste the endpoint.
CLAUDE CODE
ANYTHING ELSE
Any client that speaks MCP over Streamable HTTP connects to the same address. There is nothing to authenticate.

TOOLS

MELTER

  • melter_transforms Every format it reads and transform it runs.
  • melter_detect What a piece of text is: JSON, YAML, a JWT, CSV…
  • melter_run A pipeline of its 28 transforms, in order.
  • melter_diff Two texts, compared line by line.

BITOW

  • bitow_validate A Bitcoin address, checked properly.
  • bitow_share Its QR code, link, bitcoin: URI and embed.

DOPPLER

  • doppler_events The biggest news right now, with places and sources.

GATO

  • gato_status How the cat is doing: its mood, how fed, what it last said.

The answers are the apps’ own: MCP runs the same code as MELTER and BITOW in your browser, reads the same file DOPPLER draws, and sees the same cat as GATO’s page. It can look at the cat, not feed it: that takes people.

YOUR DATA

MELTER and BITOW in your browser send nothing anywhere. MCP is different: your assistant sends us what it asks about. We answer each call in memory and forget it — nothing stored, and no record of what was asked, only the line every visit leaves in our web log. Your AI provider sees the whole conversation; their policy covers that part. Privacy has the detail.

Limits: 256 KB per call, a few calls a second from any one address, and no XML — MELTER parses XML with the browser’s own parser, so it stays in MELTER.