Receipts Index

receipts-index-mcp

An MCP server for the Receipts Index API (stdio through npm, and a remote Streamable HTTP endpoint) at https://api.receiptsindex.com/?utm_source=npm, published by Carter Enterprise LLC.

The Receipts Index is the Namebeam record of which US local businesses AI engines name for fixed buyer questions: one dated row per check, engine and UTC date (2,714 rows, 2026-07-29 to 2026-10-27 as read on 2026-10-27).

Start free: list row ids and dates with /v1/index and read one real row with /v1/sample. Published Namebeam answers can be checked by hash at https://namebeam.ai/verify/?utm_source=npm. Then buy rows over x402 in USDC on Base: 0.27 per row, 1.81 per day file.

This server reads the free routes and lists what the paid routes cost. It never pays and never signs anything.

Tools

Tool	Calls	Cost	Returns
receipts_index	GET /v1/index	free	Row ids and UTC dates (no row content), row count, first and last date, the dates that have rows. Optional start (integer, 1 or more) and limit (integer, 1 to 500) page through row ids.
receipts_sample	GET /v1/sample	free	One real record row labeled as a sample, its row id, the paid route and price for that row, the row as fields and as CSV. No parameters.
receipts_pricing	GET /.well-known/x402, GET /v1/manifest	free	The paid endpoints with prices in USDC, as the API lists them.

Paid endpoints (as listed by the API)

Paid routes use x402 with USDC on Base mainnet. Row and day files come back as CSV with a header line. A row id or date that does not exist returns 404 and is not charged.

Route	Price (USDC)	Returns
GET /v1/row/{row_id}	0.27	One CSV row
GET /v1/day/{YYYY-MM-DD}	1.81	All rows for one UTC date
GET /v1/corpus	540	The full corpus as one CSV, per call
GET /v1/feed/founding-partner	200	The full corpus per call. Listed at 200 USDC per month; access is priced per call

Use receipts_index to pick a valid row id or date, receipts_sample to see the row shape, then buy with any x402 client. This server does not include a wallet or a payment client. Prices are read from the API at call time, so receipts_pricing is the current source.

Row fields: date_utc, check_id, business, niche, market, engine, prompt_variant, run, business_mentioned, competitors_named, sources_cited, run_channel, flags.

Telemetry

From 0.1.1 the server sends anonymous usage events to PostHog (project of Carter Enterprise LLC) through PostHog MCP Analytics: one event per tool call (tool name, client name and version, duration, error), tool listings, the handshake, and the short reason the agent gives in the context argument. Only the start and limit argument values are recorded; nothing else you pass is recorded. With telemetry on, each tool takes a context argument and the server adds a get_more_tools tool where an agent can say what it needed and did not find.

Turn it off with RECEIPTS_INDEX_TELEMETRY=0 or DO_NOT_TRACK=1 in the server's environment. Off means no PostHog client is created and the tools are exactly the three above.

Remote endpoint (Streamable HTTP)

URL: https://api.receiptsindex.com/mcp. Live since 2026-10-28 (initialize, tools/list and all three tools answered). No sign-in, no key.

It exposes the same three tools as the stdio server, read-only, with no sign-in and no API key. receipts_index and receipts_sample return the free data. receipts_pricing returns the x402 payment terms for the paid routes (route, USDC price, network, pay-to address). The endpoint never pays and never signs anything; paying is done by an x402 client against the listed route.

Add it to any client that takes a remote MCP URL (Claude and ChatGPT custom connectors, or any assistant that can add an MCP server by URL):

https://api.receiptsindex.com/mcp

Protocol notes: stateless Streamable HTTP, JSON responses. POST a JSON-RPC message (initialize, ping, tools/list, tools/call); notifications get 202. GET and DELETE return 405 because there is no server-initiated stream and no session. Protocol versions 2025-11-25, 2025-06-18, 2025-03-26 and 2024-11-05 are accepted; an unsupported MCP-Protocol-Version header returns 400. CORS is open (Access-Control-Allow-Origin: *) because the endpoint takes no credentials and serves public data. The remote endpoint sends no telemetry.

curl -sS https://api.receiptsindex.com/mcp -H 'content-type: application/json' -H 'accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

The handler is src/remote.ts (no SDK dependency, Fetch API only). npm run build plus node scripts/build-worker-module.mjs writes dist/worker/mcp-remote.worker.js, the single-file form that is pasted into the Worker. test/remote.test.ts checks that its tool list matches the stdio server's field by field.

Install

Requires Node.js 20.20 or newer (or 22.22 or newer).

Claude Desktop or any client that reads an mcpServers block:

{
  "mcpServers": {
    "receipts-index": {
      "command": "npx",
      "args": ["-y", "receipts-index-mcp"]
    }
  }
}

Claude Code:

claude mcp add receipts-index -- npx -y receipts-index-mcp

Develop

npm install
npm test

The tests run against recorded fixtures in fixtures/ (see fixtures/PROVENANCE.txt) and make no network calls.

Limits

• Row content, day files and the corpus are paid. The free tools return ids, dates, one sample row and prices only.
• The data is a record of what the named AI engines answered on the dates shown. It makes no claim about why an engine answered as it did.
• Source and contact: Carter Enterprise LLC, https://api.receiptsindex.com/?utm_source=npm. License: MIT.

Namebeam, a Carter Enterprise property. This is the first leg.