# Foodly (remote · foodly.solutions)

Find Foodly restaurants, their menus and free tables; Foodly plans, prices and FAQ for businesses.

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

## Components

- remote · `foodly.solutions`: 74/100 (this document), [markdown](https://verifymcp.io/servers/solutions-foodly-foodly/foodly.md), [page](https://verifymcp.io/servers/solutions-foodly-foodly/foodly)

## Channel facts

- Endpoint: `https://foodly.solutions/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.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-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 73/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 878 tokens (~97/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 83% 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 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 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.

### Claude

```bash
claude mcp add --transport http solutions-foodly-foodly 'https://foodly.solutions/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "solutions-foodly-foodly": {
      "url": "https://foodly.solutions/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "solutions-foodly-foodly": {
      "type": "http",
      "url": "https://foodly.solutions/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.solutions-foodly-foodly]
url = "https://foodly.solutions/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "solutions-foodly-foodly": {
      "type": "remote",
      "url": "https://foodly.solutions/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add solutions-foodly-foodly --url 'https://foodly.solutions/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  solutions-foodly-foodly:
    url: "https://foodly.solutions/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "solutions-foodly-foodly": {
      "Transport": "http",
      "Url": "https://foodly.solutions/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add solutions-foodly-foodly -t streamable-http -u 'https://foodly.solutions/mcp'
```

### Other

```json
{
  "mcpServers": {
    "solutions-foodly-foodly": {
      "type": "http",
      "url": "https://foodly.solutions/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-05 (score 74, +2)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 83 → 97
- [functional improvement] 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”

### 2026-11-04 (score 72, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-03 (score 72)

First indexed and scored.

## MCP tools (9)

### `get_foodly_overview` (~33 tokens)

What Foodly is

What Foodly does for food businesses and diners, its web dashboard, and how payments work in each region.

### `find_foodly_region` (~52 tokens)

Foodly region for a country

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).

Input parameters:

- `country` (string, required)

### `get_foodly_plans` (~68 tokens)

Foodly plans and prices

Foodly's plans and prices for one region, with what each plan includes.

Input parameters:

- `region` (string, required): 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.

### `get_foodly_faq` (~69 tokens)

Foodly FAQ

The questions food businesses ask most about Foodly in one region, with the answers.

Input parameters:

- `region` (string, required): 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.

### `get_foodly_start` (~31 tokens)

How to start with Foodly

How a food business starts with Foodly: app download links, the web dashboard and how to subscribe.

### `find_restaurants` (~127 tokens)

Find restaurants near a place

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.

Input parameters:

- `latitude` (number, required): Latitude of the place the diner asks about (a city, a street or where they are).
- `longitude` (number, required)
- `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.

### `get_restaurant` (~60 tokens)

Restaurant details

One Foodly restaurant: what it is, where, opening hours, phone, rating, whether it takes table reservations, and the packages it sells (cakes, catering, events).

Input parameters:

- `restaurant_id` (string, required): The restaurant id from find_restaurants.

### `get_menu` (~54 tokens)

Restaurant menu

A Foodly restaurant's menu: sections, dishes and drinks available today, with prices, sizes and declared allergens. Names are in the restaurant's language.

Input parameters:

- `restaurant_id` (string, required): The restaurant id from find_restaurants.

### `get_table_times` (~104 tokens)

Free table times

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.

Input parameters:

- `date` (string, required): 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, required): The restaurant id from find_restaurants.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/solutions-foodly-foodly/foodly#diagnostics

## Score history

- 2026-11-05: 74
- 2026-11-04: 72
- 2026-11-03: 72

## Common questions

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

## Links

- Remote endpoint: https://foodly.solutions/mcp
- Website: https://foodly.solutions/en
- Changelog RSS feed: https://verifymcp.io/servers/solutions-foodly-foodly/foodly.xml
- Changelog JSON feed: https://verifymcp.io/servers/solutions-foodly-foodly/foodly/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/solutions-foodly-foodly/foodly.json
- HTML version of this page: https://verifymcp.io/servers/solutions-foodly-foodly/foodly