Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Spoon Scout - Food Contaminant Lookup

REMOTE · FOOD.AGENTLOOKUPS.AI

Lab results, FDA recalls and additive rules for US packaged foods, with sources; never a grade.

+3 this week 81 Trust /100

Last scanned (2 hours ago)

Scores higher than 83% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Health and Science

Trust breakdown (7 categories)

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 Security80
Transport & Reachability100
Schema Quality & AI Usability60
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1747 tokens (~291/item across 6 items; 6 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 Management87
  • Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Changelog

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.

  • 4 Nov 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.

  • 2 Nov 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.

  • 30 Oct 26 +1

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

  • 28 Oct 26 +1

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

  • 26 Oct 26 +1

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

  • 24 Oct 26 +1

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

  • 22 Oct 26 +1

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

  • 20 Oct 26 +1

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

Diagnostics

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 5 Nov 2026 · Probed https://food.agentlookups.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=food.agentlookups.ai CN=YR2,O=Let's Encrypt,C=US 7 Oct 2026 5 Jan 2027 RSA 2048 SHA256-RSA 659b04f4be26a849813b5637a99c52ba860
SANs: food.agentlookups.ai
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of food.agentlookups.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 1814, 3799 8, 8 Verified
agentlookups.ai. 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
Header Value
strict-transport-security max-age=300
referrer-policy no-referrer

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://food.agentlookups.ai/mcp Verified 200
http (plaintext) http://food.agentlookups.ai/mcp HTTPS enforced 301 https://food.agentlookups.ai/mcp
MCP tools · 6 exposed · ~1,603 tokens

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 →

Tool Tokens
additive_status ~86

Returns where an additive is allowed, restricted, banned or requires a warning (US FDA, EU, and US states such as California, West Virginia, Texas and Louisiana), each with its law and effective date, plus how many products list it and examples.

NameTypeReqDescription
additivestringyesAdditive name or slug, e.g. "titanium dioxide" or "red-3"

No output schema declared.

No examples provided.

check_product ~221

Looks up one US packaged food by barcode (UPC/EAN/GTIN), id, or name, and returns what is known about it: lab results by chemical (with kind of evidence, sample counts, median and highest values in ppb, lots, dates and sources), FDA recalls naming its barcode, restricted additives in its ingredients with each jurisdiction's rule, FDA's typical levels for its kind of food, same-brand products that were tested, the chemical families never tested in it, and a front-of-pack photo from Open Food Facts when one passed our checks (show it with its credit and CC BY-SA 3.0 licence). result_type is match (one product), candidates (a name fit several; call again with id), or no_match.

NameTypeReqDescription
barcodestring–UPC, EAN or GTIN digits, e.g. 070852000121
idstring–A product id from an earlier candidates result
querystring–Product name with brand, e.g. "clover organic whole milk"

No output schema declared.

No examples provided.

chemical_sources ~137

For one contaminant (lead, cadmium, mercury, arsenic-total, arsenic-inorganic, perchlorate, a phthalate such as dehp or dbp, a substitute such as deht, or a bisphenol such as bpa), returns the everyday foods where FDA's Total Diet Study found the highest typical levels (with samples, detections, averages and years), named products with lab results (highest median first), recent FDA recalls naming it, and a note on drinking water where it matters.

NameTypeReqDescription
chemicalstringyesChemical name or slug, e.g. "perchlorate" or "lead"

No output schema declared.

No examples provided.

compare_products ~70

Lines up two to five products (by id) chemical by chemical, using each product's own lab results where they exist and FDA's typical level for its kind of food otherwise (marked as typical), plus restricted additives and recall counts.

NameTypeReqDescription
idsstringyesComma-separated product ids from check_product

No output schema declared.

No examples provided.

food_category ~204

For a kind of food (a category slug such as milk, rice, baby-infant-foods-beverages, cereal, water), returns FDA's typical levels of metals and perchlorate, whether FDA's foods are a close or rough stand-in, and the products in that category with lab results: the 50 lowest in the most-tested chemical by default (products below the lab's limit first), with tested_total giving the full count. Pass sort to rank by another chemical, order=high for highest first, and all=true for every tested product.

NameTypeReqDescription
allboolean–Optional: true returns every tested product instead of the first 50
categorystringyesCategory slug, e.g. "milk"
orderstring–Optional: "high" for highest first (default lowest first)
sortstring–Optional chemical slug to rank by, e.g. "lead" (default: the chemical tested in the most products)

No output schema declared.

No examples provided.

interpret_test_result ~885

Places a person's urine or blood test result among CDC NHANES population percentiles (newest survey cycle loaded), for everyone or one age group, and says in words how high it is. tier.level is below_median, median_to_95th, top_5_percent or far_above (at least twice the 95th percentile; CDC's tables stop at the 95th, so times_95th_percentile gives the multiple); a far_above result carries clear_line, e.g. "This is far above typical. Talk to your clinician soon." ("right away" for blood lead at CDC's 45 ug/dL children's step, or OSHA's 50 for adults). unit_check is set when the value is more than 10 times the highest 95th percentile in CDC's tables, which can mean a unit mix-up (ug/L typed as ug/dL); show it to the person. For blood lead, official_guidance gives CDC's follow-up steps for children (2025) and, for adults (no CDC schedule), what NIOSH lists from agencies and medical groups (2024), each with its source; age 20+ returns only the adult guidance, under 12 only the children's. official_limits includes CDC's 3.5 ug/dL blood lead reference value. context gives cited lines on what the test shows, e.g. urine perchlorate reflects about the last day of food and water. Pass unit as printed on the report: ug/L (same as ng/mL), ug/dL, or ug/g creatinine for creatinine-adjusted urine results (CDC's creatinine tables); ug/L and ug/dL are converted into the table's unit and entered shows what was typed. Context only, not a diagnosis.

NameTypeReqDescription
agestring–Who to compare with: all (default), young (under 6), 6-11, 12-19, 20+, or an age in years
chemicalstringyesAnalyte key: a chemical slug for its first analyte, or chemical:NHANES code. Loaded keys: lead or lead:LBXBPB (Lead, µg/dL); mercury or mercury:LBXTHG (Total Mercury, µg/L); arsenic-total or arsenic-…
unitstring–Unit printed on the report: ug/L (or ng/mL), ug/dL, or ug/g creatinine (urine only). Omit to use the unit listed for the key.
valuenumberyesThe result as printed on the report (a number; a numeric string also works)

No output schema declared.

No examples provided.

Install

How do I install the Spoon Scout - Food Contaminant Lookup MCP server?

Spoon Scout - Food Contaminant Lookup is a hosted endpoint at https://food.agentlookups.ai/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.agentlookups.ai

# add to Claude Code
claude mcp add --transport http ai-agentlookups-spoon-scout 'https://food.agentlookups.ai/mcp'
Common questions

What is the Spoon Scout - Food Contaminant Lookup MCP server?

Spoon Scout - Food Contaminant Lookup is an MCP server listed in the public MCP registry as ai.agentlookups/spoon-scout. Lab results, FDA recalls and additive rules for US packaged foods, with sources; never a grade. This page covers its hosted endpoint (https://food.agentlookups.ai/mcp).

Is the Spoon Scout - Food Contaminant Lookup MCP server safe to use?

Spoon Scout - Food Contaminant Lookup scores 81 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 Spoon Scout - Food Contaminant Lookup MCP server expose?

Spoon Scout - Food Contaminant Lookup exposes 6 tools: check_product, chemical_sources, compare_products, food_category, additive_status, interpret_test_result. Their descriptions and schemas cost roughly 1,603 tokens of context every time the server is loaded.

Does the Spoon Scout - Food Contaminant Lookup MCP server require authentication?

No. We connected to Spoon Scout - Food Contaminant Lookup without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Spoon Scout - Food Contaminant Lookup MCP server still maintained?

Spoon Scout - Food Contaminant Lookup 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.