# Receipts Index (remote · api.receiptsindex.com)

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

- Trust score: 70/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `api.receiptsindex.com`: 70/100 (this document), [markdown](https://verifymcp.io/servers/mrcrtr1979-droid-receipts-index/api.md), [page](https://verifymcp.io/servers/mrcrtr1979-droid-receipts-index/api)
- npm · `receipts-index-mcp`: 83/100, [markdown](https://verifymcp.io/servers/mrcrtr1979-droid-receipts-index/receipts-index-mcp.md), [page](https://verifymcp.io/servers/mrcrtr1979-droid-receipts-index/receipts-index-mcp)

## Channel facts

- Endpoint: `https://api.receiptsindex.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.5`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 308 tokens (~102/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Receipts Index MCP server?

Receipts Index is a hosted endpoint at https://api.receiptsindex.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http mrcrtr1979-droid-receipts-index 'https://api.receiptsindex.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "mrcrtr1979-droid-receipts-index": {
      "url": "https://api.receiptsindex.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "mrcrtr1979-droid-receipts-index": {
      "type": "http",
      "url": "https://api.receiptsindex.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.mrcrtr1979-droid-receipts-index]
url = "https://api.receiptsindex.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mrcrtr1979-droid-receipts-index": {
      "type": "remote",
      "url": "https://api.receiptsindex.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mrcrtr1979-droid-receipts-index --url 'https://api.receiptsindex.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  mrcrtr1979-droid-receipts-index:
    url: "https://api.receiptsindex.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "mrcrtr1979-droid-receipts-index": {
      "Transport": "http",
      "Url": "https://api.receiptsindex.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add mrcrtr1979-droid-receipts-index -t streamable-http -u 'https://api.receiptsindex.com/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-03 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 67, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-28 (score 67)

First indexed and scored.

## MCP tools (3)

### `receipts_index` (~117 tokens)

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.

Input parameters:

- `limit` (integer): Rows per page, 1 to 500. The API default applies when omitted.
- `start` (integer): First row id of the page. Default 1.

### `receipts_sample` (~65 tokens)

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.

### `receipts_pricing` (~70 tokens)

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/mrcrtr1979-droid-receipts-index/api#diagnostics

## Score history

- 2026-11-05: 70
- 2026-11-04: 70
- 2026-11-03: 70
- 2026-11-02: 69
- 2026-11-01: 69
- 2026-10-31: 68
- 2026-10-30: 68
- 2026-10-29: 67
- 2026-10-28: 67

## Common questions

### What is the Receipts Index MCP server?

Receipts Index is an MCP server listed in the public MCP registry as io.github.mrcrtr1979-droid/receipts-index. Free index and sample of dated AI-engine answer rows; prices for paid x402 rows. Never pays. This page covers its hosted endpoint (https://api.receiptsindex.com/mcp).

### Is the Receipts Index MCP server safe to use?

Receipts Index scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Receipts Index MCP server expose?

Receipts Index exposes 3 tools: receipts_index, receipts_sample, receipts_pricing. Their descriptions and schemas cost roughly 252 tokens of context every time the server is loaded.

### Does the Receipts Index MCP server require authentication?

No. We connected to Receipts Index without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Receipts Index MCP server still maintained?

Receipts Index is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Receipts Index MCP server?

VerifyMCP ran 12 checks on Receipts Index, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Receipts Index: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://api.receiptsindex.com/mcp
- Repository: https://github.com/mrcrtr1979-droid/namebeam-visibility-index
- Website: https://api.receiptsindex.com/?utm_source=mcp-registry
- Changelog RSS feed: https://verifymcp.io/servers/mrcrtr1979-droid-receipts-index/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/mrcrtr1979-droid-receipts-index/api/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/mrcrtr1979-droid-receipts-index/api.json
- HTML version of this page: https://verifymcp.io/servers/mrcrtr1979-droid-receipts-index/api