Receipts Index

io.github.mrcrtr1979-droidPublished by GitHub account mrcrtr1979-droidv0.1.5Updated Oct 29, 2026

Free index and sample of dated AI-engine answer rows; prices for paid x402 rows. Never pays.

VerifiedStreamable HTTPWeb executableFinanceData & Analytics

Overview

AI-generated overview

Read-only MCP access to the Receipts Index API: browse free row ids and dates, view one sample row, and list paid x402 prices in USDC.

What you can do
  • List index rows: page through row ids and UTC dates, row count, first and last date, and dates that have rows
  • Read one sample record row, labeled as a sample, as fields and CSV, with its row id and paid route price
  • Read pricing: list the paid x402 endpoints with their USDC prices as the API reports them
  • No purchase or signing: the server only reads free routes and payment terms
When to use it
Use it when you want an assistant to explore the Receipts Index catalog of dated AI-engine answer rows for US local businesses, check the shape of a row, or find out what paid rows cost before buying them with a separate x402 client.
Requirements
Either the remote Streamable HTTP endpoint at api.receiptsindex.com/mcp, which needs no sign-in or key, or the local npm package run with npx, which needs Node.js 20.20 or newer (or 22.22 or newer). Network access to the Receipts API.
Before you install
Row content, day files and the corpus are paid and are bought separately over x402 in USDC on Base (0.27 per row, 1.81 per day file, 540 for the corpus); the server itself never pays or signs, so a separate wallet client is needed. The npm stdio server sends anonymous usage events to PostHog, including tool name, client name and version, duration, errors, and the agent's context reason; disable with RECEIPTS_INDEX_TELEMETRY=0 or DO_NOT_TRACK=1. The remote endpoint sends no telemetry.

Installation

In SourceWeft

  1. Open Receipts Index in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.mrcrtr1979-droid%2Freceipts-index/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "receipts-index": {
      "type": "http",
      "url": "https://api.receiptsindex.com/mcp"
    }
  }
}

README

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

ToolCallsCostReturns
receipts_indexGET /v1/indexfreeRow 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_sampleGET /v1/samplefreeOne 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_pricingGET /.well-known/x402, GET /v1/manifestfreeThe 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.

RoutePrice (USDC)Returns
GET /v1/row/{row_id}0.27One CSV row
GET /v1/day/{YYYY-MM-DD}1.81All rows for one UTC date
GET /v1/corpus540The full corpus as one CSV, per call
GET /v1/feed/founding-partner200The 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:

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

Claude Code:

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

Develop

npm installnpm 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.

Source: mcp/README.md at commit 0ae7baf

Tools

3

receipts_index

Receipts Index: free row index

Calls GET /v1/index on the Receipts API. Free. Returns row ids and UTC dates (no row content), the row count, the first and last dates, and the list of dates that have rows. Use start and limit to page through row ids. Row content is sold per call through x402 and is not returned here.

Parameterslimitstart

receipts_sample

Receipts Index: free sample row

Calls GET /v1/sample on the Receipts API. Free. Returns one real record row labeled as a sample, with its row id, the paid route and price for that row, and the row as fields and as CSV. It takes no parameters and is not a purchase.

Takes no parameters.

receipts_pricing

Receipts Index: paid endpoints and prices

Reads GET /.well-known/x402 (and /v1/manifest for the price text) on the Receipts API and returns the paid endpoints with their prices in USDC. Free to call. It never pays and never signs anything. Paying is done by an x402 client against the listed route.

Takes no parameters.

Version history

1
  1. v0.1.5LatestOct 29, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts