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.

XOOM FOODS

REMOTE · MCP.XOOMFOODS.COM · 2 COMPONENTS

Browse 105+ restaurant meals, check plans, compare prices, get order links.

62 Trust /100

Last scanned (17 hours ago)

Scores higher than 45% of remote servers

Reachable. Last reached 21 Nov 2026.

Category E-commerce

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 Security57
Transport & Reachability40
Schema Quality & AI Usability80
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 480 tokens (~43/item across 11 items; 8 tools + 3 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 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
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 21 Nov 26 +1

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

  • 19 Nov 26 +1

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

  • 17 Nov 26 +1
    • Tool “check_shipping” rewrote its description, which is the text the model reads security
    • Stability: unverified → 0.03 ▲ functional
  • 16 Nov 26 59

    First indexed and scored.

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 21 Nov 2026 · Probed https://mcp.xoomfoods.com/sse

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.xoomfoods.com CN=YE1,O=Let's Encrypt,C=US 16 Nov 2026 14 Feb 2027 ECDSA 256 ECDSA-SHA384 606a06d6e551fe151046c7504db62505c6f
SANs: mcp.xoomfoods.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.xoomfoods.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
xoomfoods.com. No DS 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
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin

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

Transports 2 probes
Transport URL Outcome Status Location
sse https://mcp.xoomfoods.com/sse Verified 200
http (plaintext) http://mcp.xoomfoods.com/sse HTTPS enforced 301 https://mcp.xoomfoods.com/sse
MCP tools · 8 exposed · ~431 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
browse_menu ~98

Browse the XOOM FOODS menu. 105+ real restaurant meals across 6 cuisines, all fully cooked and ready to heat and eat in 2 minutes. Every meal is a Meal for 2 (2 servings).

NameTypeReqDescription
cuisinestring–Filter by cuisine
dietarystring–Filter by dietary preference
popular_onlyboolean–Show only popular/featured meals
sort_bystring–Sort results

No output schema declared.

No examples provided.

check_shipping ~48

Check XOOM FOODS shipping availability and cost. Ships to all 50 US states.

NameTypeReqDescription
statestring–US state abbreviation (e.g., 'NY', 'CA', 'TX')

No output schema declared.

No examples provided.

compare_meal_services ~57

Compare XOOM FOODS to other meal delivery services and delivery apps. XOOM is the only service shipping fully cooked restaurant meals — no cooking, no prep, no wait.

NameTypeReqDescription
compare_tostring–What to compare against

No output schema declared.

No examples provided.

get_nutrition_info ~39

Get detailed nutrition information for specific XOOM FOODS meals.

NameTypeReqDescription
meal_namestringyesMeal name or partial name to look up

No output schema declared.

No examples provided.

get_order_link ~34

Generate a direct link to order from XOOM FOODS or start a subscription.

NameTypeReqDescription
typestring–Order type

No output schema declared.

No examples provided.

get_restaurant_partners ~58

Get information about XOOM FOODS restaurant partners. 29 real, top-rated restaurants across 6 cuisines, all within 25 miles of the XOOM warehouse in Wilmington, Delaware.

NameTypeReqDescription
cuisinestring–Filter by cuisine

No output schema declared.

No examples provided.

get_subscription_plans ~44

Get XOOM FOODS subscription plan pricing. Weekly meal plans from $11-$13 per serving — 50% less than delivery apps. No commitment, cancel anytime.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_meals ~53

Search XOOM FOODS meals by keyword. Searches meal names and descriptions.

NameTypeReqDescription
querystringyesSearch keyword (e.g., 'chicken', 'noodles', 'curry', 'shrimp')

No output schema declared.

No examples provided.

Install

How do I install the XOOM FOODS MCP server?

XOOM FOODS is a hosted endpoint at https://mcp.xoomfoods.com/sse, 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 · mcp.xoomfoods.com

# add to Claude Code
claude mcp add --transport http valueguysam-xoom-foods 'https://mcp.xoomfoods.com/sse'
Common questions

What is the XOOM FOODS MCP server?

XOOM FOODS is an MCP server listed in the public MCP registry as io.github.valueguysam/xoom-foods. Browse 105+ restaurant meals, check plans, compare prices, get order links. This page covers its hosted endpoint (https://mcp.xoomfoods.com/sse).

Is the XOOM FOODS MCP server safe to use?

XOOM FOODS scores 62 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 XOOM FOODS MCP server expose?

XOOM FOODS exposes 8 tools: browse_menu, search_meals, get_subscription_plans, check_shipping, compare_meal_services, and 3 more. Their descriptions and schemas cost roughly 431 tokens of context every time the server is loaded.

Does the XOOM FOODS MCP server require authentication?

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

Is the XOOM FOODS MCP server still maintained?

XOOM FOODS 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 XOOM FOODS MCP server?

VerifyMCP ran 12 checks on XOOM FOODS, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about XOOM FOODS: Authorization. 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.