MCPFax Food Facts
REMOTE · FOOD-FACTS.BOWLING-ANTHONY.WORKERS.DEV · SCANNED SEP 26
Can this person eat this? Allergens, additives and nutrition from a barcode.
Available components
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. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 431 tokens (~143/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the MCPFax Food Facts MCP server?
MCPFax Food Facts is a hosted endpoint at https://food-facts.bowling-anthony.workers.dev/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.
remote · food-facts.bowling-anthony.workers.dev
claude mcp add --transport http com-mcpscores-food-facts 'https://food-facts.bowling-anthony.workers.dev/mcp'
{
"mcpServers": {
"com-mcpscores-food-facts": {
"url": "https://food-facts.bowling-anthony.workers.dev/mcp"
}
}
} {
"servers": {
"com-mcpscores-food-facts": {
"type": "http",
"url": "https://food-facts.bowling-anthony.workers.dev/mcp"
}
}
} [mcp_servers.com-mcpscores-food-facts] url = "https://food-facts.bowling-anthony.workers.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mcpscores-food-facts": {
"type": "remote",
"url": "https://food-facts.bowling-anthony.workers.dev/mcp",
"enabled": true
}
}
} openclaw mcp add com-mcpscores-food-facts --url 'https://food-facts.bowling-anthony.workers.dev/mcp' --transport streamable-http
mcp_servers:
com-mcpscores-food-facts:
url: "https://food-facts.bowling-anthony.workers.dev/mcp" {
"McpServers": {
"com-mcpscores-food-facts": {
"Transport": "http",
"Url": "https://food-facts.bowling-anthony.workers.dev/mcp"
}
}
} assistant mcp add com-mcpscores-food-facts -t streamable-http -u 'https://food-facts.bowling-anthony.workers.dev/mcp'
{
"mcpServers": {
"com-mcpscores-food-facts": {
"type": "http",
"url": "https://food-facts.bowling-anthony.workers.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
- Stability: 0.97 → pass security
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 26 Sept 2026 · Probed https://food-facts.bowling-anthony.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=bowling-anthony.workers.dev | CN=WE1,O=Google Trust Services,C=US | 22 Sept 2026 | 21 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 99977672261024f133ad95ab21127b5 |
| SANs: bowling-anthony.workers.dev, *.bowling-anthony.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of food-facts.bowling-anthony.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://food-facts.bowling-anthony.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://food-facts.bowling-anthony.workers.dev/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
demand_report What agents are asking for most (free) ~57
FREE, no payment. The aggregate of what agents have told us they are looking for, most-requested first, with the categories nothing available yet serves.
| Name | Type | Req | Description |
|---|---|---|---|
| days | string | – | Window in days, default 30, max 90. |
No output schema declared.
No examples provided.
food_by_barcode Packaged food facts by barcode ~156
Look up a packaged food by its barcode and get the fields that answer "can this person eat this?" — ingredients, allergens, traces, additives, Nutri-Score, NOVA processing group and per-100g nutrition. Data is from Open Food Facts, which is crowd-sourced and openly licensed: coverage is uneven by country and a product can be listed with most nutrition empty, so every response carries a completeness flag and missing values are null rather than estimated. A barcode not in the database returns not_found and is NOT charged. Costs $0.005 USDC per call via x402 on Base.
| Name | Type | Req | Description |
|---|---|---|---|
| barcode | string | yes | 6-14 digit product barcode, e.g. '737628064502'. |
No output schema declared.
No examples provided.
request_data Tell us what data you are looking for (free) ~88
FREE, no payment. Describe in your own words the data you are trying to buy — anything, not just food — and get back whether we operate a service that supplies it, with the MCP endpoint if so. Every request is catalogued so repeatedly-requested data gets built. Nothing identifying is stored, only the words of the request.
| Name | Type | Req | Description |
|---|---|---|---|
| need | string | yes | What you are looking for. |
No output schema declared.
No examples provided.
What is the MCPFax Food Facts MCP server?
MCPFax Food Facts is an MCP server listed in the public MCP registry as com.mcpscores/food-facts. Can this person eat this? Allergens, additives and nutrition from a barcode. This page covers its hosted endpoint (https://food-facts.bowling-anthony.workers.dev/mcp).
Is the MCPFax Food Facts MCP server safe to use?
MCPFax Food Facts scores 74 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 MCPFax Food Facts MCP server expose?
MCPFax Food Facts exposes 3 tools: request_data, demand_report, food_by_barcode. Their descriptions and schemas cost roughly 301 tokens of context every time the server is loaded.
Does the MCPFax Food Facts MCP server require authentication?
No. We connected to MCPFax Food Facts without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the MCPFax Food Facts MCP server still maintained?
MCPFax Food Facts is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.