MCP

BitGraph is an MCP server. Any AI agent that speaks the Model Context Protocol can record files, check whether bytes are on record, and fetch proofs with one URL.

MCP endpoint
https://bitgraph.ing/mcp

The same URL serves both audiences: an MCP client gets the protocol, a browser gets this page.

Connect

There is nothing to install and no key to request. Every client below wants the same thing: that URL, pasted where it keeps remote MCP servers. Find yours and follow the three or four steps.

Claude

claude.ai, Claude Desktop, and the mobile apps.

  1. 1.Open Customize, then Connectors.
  2. 2.Click +, then Add custom connector.
  3. 3.Paste the URL and click Add. Leave Advanced settings alone, there is no OAuth to configure.
  4. 4.In a conversation, open the + menu at the lower left, choose Connectors, and switch BitGraph on.

Step 4 is the one people miss: adding a connector does not turn it on, each conversation opts in. Free accounts can hold one custom connector. On Team and Enterprise an Owner adds it once under Organization settings, then Connectors, and everyone else clicks Connect.

Claude Code

One command, no menus.

Shell
claude mcp add --transport http bitgraph https://bitgraph.ing/mcp

Run claude mcp list to confirm, or /mcp inside a session. BitGraph should read Connected.

ChatGPT

Needs developer mode, which is a beta feature on Plus, Pro, Business, Enterprise, and Education accounts, on the web.

  1. 1.Open Settings, then Security and login, and turn on Developer mode.
  2. 2.Go to chatgpt.com/plugins and click +.
  3. 3.Name it BitGraph, paste the URL, and choose No authentication. The URL already ends in /mcp, so paste it exactly as it is.
  4. 4.Create the connection. ChatGPT lists the three tools it found, which is your confirmation that it worked.
  5. 5.In a new chat, open the + menu, choose Developer mode, and select BitGraph.

ChatGPT treats recording as a write action and asks you to confirm each one, showing the digest it is about to send. Checking and fetching proofs are read-only. Every new conversation starts from the same cautious default.

Cursor, VS Code, and everything else

Add the URL as a remote MCP server. Some clients label the transport streamable-http and some label it http; they are the same thing, and BitGraph speaks it. No key, no configuration.

Client menus get renamed and moved. If a label above does not match what is in front of you, the URL is the part that matters: find wherever your client keeps remote MCP servers and paste it there.

Check that it worked

Point your agent at any file you have and ask:

Ask your agent
Is this file on record with BitGraph?

A file that has never been recorded comes back as not on record. One that has comes back with its causal position and a link to its proof page. Either answer means the connection is live. Asking is read-only and writes nothing to the ledger, so it is a safe first move.

Three tools

  • • bitgraph_record · Take a BitGraph: record a file's SHA-256 digest at a new causal position. Bytes already on record come back with their existing proof; again=true deliberately records the same bytes at a new position.
  • • bitgraph_check · Is this file on record? Read-only, every causal position, with proof page URLs.
  • • bitgraph_get_proof · Fetch a proof and its Ethereum anchor window: BitGraphed between block X and block Y.

Working with local files

The hosted endpoint accepts digests, not files: the agent hashes a file where it lives and sends only the SHA-256. For clients that run on your machine, the stdio package does the hashing itself and takes plain file paths:

Shell
claude mcp add bitgraph -- npx -y @mikeargento/bitgraph-mcp

Notes

  • • Files are never uploaded. Only the SHA-256 digest crosses the network, to either endpoint.
  • • Recordings are permanent. The ledger has 10-year retention and no deletes. Agents are instructed to record only files you asked to record.
  • • A BitGraph is a selection. The record tool takes the digest of a file that already exists; it does not create anything.
  • • One ledger. A recording made through MCP is indistinguishable from one made by dropping the file on the site, and shows up on the same Roll.