# Fast Food Index (remote · api.fastfoodindex.com)

Live fast food prices from 10 US chains: Big Mac Index by state, chain medians & price changes.

- Trust score: 63/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `api.fastfoodindex.com`: 63/100 (this document), [markdown](https://verifymcp.io/servers/com-fastfoodindex-fast-food-index/api.md), [page](https://verifymcp.io/servers/com-fastfoodindex-fast-food-index/api)

## Channel facts

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

## 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-21.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - 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 481 tokens (~80/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 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 Fast Food Index MCP server?

Fast Food Index is a hosted endpoint at https://api.fastfoodindex.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 com-fastfoodindex-fast-food-index 'https://api.fastfoodindex.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-fastfoodindex-fast-food-index": {
      "url": "https://api.fastfoodindex.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-fastfoodindex-fast-food-index": {
      "type": "http",
      "url": "https://api.fastfoodindex.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-fastfoodindex-fast-food-index]
url = "https://api.fastfoodindex.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-fastfoodindex-fast-food-index": {
      "type": "remote",
      "url": "https://api.fastfoodindex.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-fastfoodindex-fast-food-index --url 'https://api.fastfoodindex.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-fastfoodindex-fast-food-index:
    url: "https://api.fastfoodindex.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-fastfoodindex-fast-food-index": {
      "Transport": "http",
      "Url": "https://api.fastfoodindex.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-fastfoodindex-fast-food-index -t streamable-http -u 'https://api.fastfoodindex.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-fastfoodindex-fast-food-index": {
      "type": "http",
      "url": "https://api.fastfoodindex.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-21 (score 63, +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-19 (score 62, +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-11-17 (score 61, +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-11-16 (score 60, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-15 (score 60)

First indexed and scored.

## MCP tools (6)

### `get_big_mac_index` (~59 tokens)

The Fast Food Index Big Mac index: the national median Big Mac price across priced US McDonald's restaurants, its range and extremes, and the median by state with each state vs the national figure. Data collected weekly from McDonald's own ordering system.

### `get_chain_overview` (~46 tokens)

Every chain Fast Food Index prices (10 US chains): flagship item, its national median price and range, and restaurants priced. Data collected weekly from the chains' own ordering systems.

### `get_item_price` (~107 tokens)

The price of one menu item at one chain: national median, typical range, restaurants priced, and the cheapest / priciest states (for flagship items) or stores. Chain accepts names like "McDonald's", "taco bell", "bk".

Input parameters:

- `chain` (string, required): Chain name or slug, e.g. "McDonald's" or "taco-bell".
- `item` (string, required): Menu item name, e.g. "Big Mac" or "Whopper".

### `get_state_prices` (~86 tokens)

One US state: its fast-food price index position (percent vs the national basket) and the flagship item medians in that state (Big Mac, Whopper, Chick-fil-A Chicken Sandwich, Crunchwrap Supreme where priced). Accepts a state name or abbreviation.

Input parameters:

- `state` (string, required): State name or 2-letter abbreviation, e.g. "Texas" or "TX".

### `get_price_changes` (~65 tokens)

The latest verified fast-food price changes: gated repricing events (same item, same old and new price, at 40+ restaurants) from the most recent weekly collection round.

Input parameters:

- `limit` (integer): How many events to return (1–25, default 10).

### `search_items` (~80 tokens)

Search priced menu items by name across all 10 chains (e.g. "nuggets", "frosty", "burrito"). Returns matching items with national medians and restaurant counts.

Input parameters:

- `chain` (string): Optional: restrict to one chain (name or slug).
- `query` (string, required): Item name or fragment to search for.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-fastfoodindex-fast-food-index/api#diagnostics

## Score history

- 2026-11-21: 63
- 2026-11-20: 62
- 2026-11-19: 62
- 2026-11-18: 61
- 2026-11-17: 61
- 2026-11-16: 60
- 2026-11-15: 60

## Common questions

### What is the Fast Food Index MCP server?

Fast Food Index is an MCP server listed in the public MCP registry as com.fastfoodindex/fast-food-index. Live fast food prices from 10 US chains: Big Mac Index by state, chain medians & price changes. This page covers its hosted endpoint (https://api.fastfoodindex.com/mcp).

### Is the Fast Food Index MCP server safe to use?

Fast Food Index scores 63 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 Fast Food Index MCP server expose?

Fast Food Index exposes 6 tools: get_big_mac_index, get_chain_overview, get_item_price, get_state_prices, get_price_changes, search_items. Their descriptions and schemas cost roughly 443 tokens of context every time the server is loaded.

### Does the Fast Food Index MCP server require authentication?

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

### Is the Fast Food Index MCP server still maintained?

Fast Food Index is still listed as active in the MCP registry. We last reached this channel on 21 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 Fast Food Index MCP server?

VerifyMCP ran 11 checks on Fast Food Index, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about Fast Food Index: Authorization and 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.fastfoodindex.com/mcp
- Website: https://fastfoodindex.com/api/
- Changelog RSS feed: https://verifymcp.io/servers/com-fastfoodindex-fast-food-index/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-fastfoodindex-fast-food-index/api/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-fastfoodindex-fast-food-index/api.json
- HTML version of this page: https://verifymcp.io/servers/com-fastfoodindex-fast-food-index/api
