Foodly
REMOTE · FOODLY.SOLUTIONS
Find Foodly restaurants, their menus and free tables; Foodly plans, prices and FAQ for businesses.
Available components
Last scanned (17 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 5 Nov 2026.
Category E-commerce
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 878 tokens (~97/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 83% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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 →
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.
- 5 Nov 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 83 → 97 ▼ functional
- Tool coverage: 67% → 83% ▲ functional
- Server version: 1.0.0 → 1.1.0 functional
- New tool “find_restaurants” functional
- New tool “get_menu” functional
- New tool “get_restaurant” functional
- New tool “get_table_times” functional
- 4 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 3 Nov 26 72
First indexed and scored.
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://foodly.solutions/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=foodly.solutions | CN=WR3,O=Google Trust Services,C=US | 30 Oct 2026 | 28 Jan 2027 | RSA 2048 | SHA256-RSA | fe30cdfaf6a1fdb4129e3b601e300292 |
| SANs: foodly.solutions, app.foodly.solutions | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
| CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 1 Sept 1998 | 28 Jan 2028 | RSA 2048 | SHA1-RSA | 40000000001154b5ac394 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of foodly.solutions. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| solutions. | DS published | 23131 | 8 | Verified |
| foodly.solutions. | 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 |
|---|---|
| strict-transport-security | max-age=31556926 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://foodly.solutions/mcp | Verified | 200 | |
| http (plaintext) | http://foodly.solutions/mcp | HTTPS enforced | 301 | https://foodly.solutions/mcp |
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 →
find_foodly_region Foodly region for a country ~52
Which Foodly region, plans and page apply to a country. Accepts an ISO code (MX) or a name in English, Spanish or Portuguese (Mexico, México).
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | – |
No output schema declared.
No examples provided.
find_restaurants Find restaurants near a place ~127
Restaurants, bars, cafés and caterers on Foodly near a point, nearest first, optionally matching a dish, cuisine or name. Foodly is new, so there may be few or none.
| Name | Type | Req | Description |
|---|---|---|---|
| latitude | number | yes | Latitude of the place the diner asks about (a city, a street or where they are). |
| longitude | number | yes | – |
| query | string | – | A dish, a cuisine or a restaurant name: arepas, sushi, Arepate. |
| radius_km | number | – | How far to look, in km. Up to 25. |
No output schema declared.
No examples provided.
get_foodly_faq Foodly FAQ ~69
The questions food businesses ask most about Foodly in one region, with the answers.
| Name | Type | Req | Description |
|---|---|---|---|
| region | string | yes | Where the business is: europe = Portugal and Spain, latam = Latin America and the Caribbean, us = United States. Use find_foodly_region to map a country. |
No output schema declared.
No examples provided.
get_foodly_overview What Foodly is ~33
What Foodly does for food businesses and diners, its web dashboard, and how payments work in each region.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_foodly_plans Foodly plans and prices ~68
Foodly's plans and prices for one region, with what each plan includes.
| Name | Type | Req | Description |
|---|---|---|---|
| region | string | yes | Where the business is: europe = Portugal and Spain, latam = Latin America and the Caribbean, us = United States. Use find_foodly_region to map a country. |
No output schema declared.
No examples provided.
get_foodly_start How to start with Foodly ~31
How a food business starts with Foodly: app download links, the web dashboard and how to subscribe.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_menu Restaurant menu ~54
A Foodly restaurant's menu: sections, dishes and drinks available today, with prices, sizes and declared allergens. Names are in the restaurant's language.
| Name | Type | Req | Description |
|---|---|---|---|
| restaurant_id | string | yes | The restaurant id from find_restaurants. |
No output schema declared.
No examples provided.
get_restaurant Restaurant details ~60
One Foodly restaurant: what it is, where, opening hours, phone, rating, whether it takes table reservations, and the packages it sells (cakes, catering, events).
| Name | Type | Req | Description |
|---|---|---|---|
| restaurant_id | string | yes | The restaurant id from find_restaurants. |
No output schema declared.
No examples provided.
get_table_times Free table times ~104
The times a Foodly restaurant has free for a table on one day, in the restaurant's local time. Booking is done in the Foodly app and the restaurant confirms it.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | The day, as YYYY-MM-DD, in the restaurant's calendar. |
| party_size | integer | – | How many people. With it, times without room for the group show as full. |
| restaurant_id | string | yes | The restaurant id from find_restaurants. |
No output schema declared.
No examples provided.
How do I install the Foodly MCP server?
Foodly is a hosted endpoint at https://foodly.solutions/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 · foodly.solutions
claude mcp add --transport http solutions-foodly-foodly 'https://foodly.solutions/mcp'
What is the Foodly MCP server?
Foodly is an MCP server listed in the public MCP registry as solutions.foodly/foodly. Find Foodly restaurants, their menus and free tables; Foodly plans, prices and FAQ for businesses. This page covers its hosted endpoint (https://foodly.solutions/mcp).
Is the Foodly MCP server safe to use?
Foodly 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 Foodly MCP server expose?
Foodly exposes 9 tools: get_foodly_overview, find_foodly_region, get_foodly_plans, get_foodly_faq, get_foodly_start, and 4 more. Their descriptions and schemas cost roughly 598 tokens of context every time the server is loaded.
Does the Foodly MCP server require authentication?
No. We connected to Foodly without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Foodly MCP server still maintained?
Foodly 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 Foodly MCP server?
VerifyMCP ran 13 checks on Foodly, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.