_ registry / mcp streamable-http · checked 1h ago

solutions.foodly/foodly

https://foodly.solutions

Registry code: b8bde431bb531fc7

api record

Facts about Foodly (https://foodly.solutions), the app for restaurants, bars, cafés, food trucks, caterers and private chefs. How to use them:

1. Find out the country first: plans, prices and payments differ between Portugal and Spain, Latin America and the Caribbean, and the United States.

endpoint
https://foodly.solutions/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is solutions.foodly/foodly live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is solutions.foodly/foodly free to use?
Yes — the hub reached it with no key and no payment.
What tools does solutions.foodly/foodly have?
9 tools: get_foodly_faq, get_foodly_plans, find_restaurants, get_restaurant, get_menu, get_table_times, find_foodly_region, get_foodly_overview, ….
Is solutions.foodly/foodly safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
112ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 9 tools
2 open 7 never probed 2 of 9 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_foodly_overview open 1h ago

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

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_foodly_start open 1h ago

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

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_foodly_faq unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "region"
  ],
  "properties": {
    "region": {
      "enum": [
        "europe",
        "latam",
        "us"
      ],
      "type": "string",
      "description": "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."
    }
  }
}
    arguments 18 lines
  • get_foodly_plans unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "region"
  ],
  "properties": {
    "region": {
      "enum": [
        "europe",
        "latam",
        "us"
      ],
      "type": "string",
      "description": "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."
    }
  }
}
    arguments 18 lines
  • find_restaurants unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "latitude",
    "longitude"
  ],
  "properties": {
    "query": {
      "type": "string",
      "maxLength": 100,
      "minLength": 2,
      "description": "A dish, a cuisine or a restaurant name: arepas, sushi, Arepate."
    },
    "latitude": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Latitude of the place the diner asks about (a city, a street or where they are)."
    },
    "longitude": {
      "type": "number",
      "maximum": 180,
      "minimum": -180
    },
    "radius_km": {
      "type": "number",
      "default": 10,
      "maximum": 25,
      "minimum": 1,
      "description": "How far to look, in km. Up to 25."
    }
  }
}
    arguments 34 lines
  • get_restaurant unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "restaurant_id"
  ],
  "properties": {
    "restaurant_id": {
      "type": "string",
      "format": "uuid",
      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
      "description": "The restaurant id from find_restaurants."
    }
  }
}
    arguments 15 lines
  • get_menu unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "restaurant_id"
  ],
  "properties": {
    "restaurant_id": {
      "type": "string",
      "format": "uuid",
      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
      "description": "The restaurant id from find_restaurants."
    }
  }
}
    arguments 15 lines
  • get_table_times unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "restaurant_id",
    "date"
  ],
  "properties": {
    "date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "The day, as YYYY-MM-DD, in the restaurant's calendar."
    },
    "party_size": {
      "type": "integer",
      "maximum": 100,
      "minimum": 1,
      "description": "How many people. With it, times without room for the group show as full."
    },
    "restaurant_id": {
      "type": "string",
      "format": "uuid",
      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
      "description": "The restaurant id from find_restaurants."
    }
  }
}
    arguments 27 lines
  • find_foodly_region unknown 1h ago

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "country"
  ],
  "properties": {
    "country": {
      "type": "string",
      "maxLength": 60,
      "minLength": 2
    }
  }
}
    arguments 14 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id b8bde431bb531fc7.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/b8bde431bb531fc7/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/b8bde431bb531fc7/badge.svg)](https://brick.blue/agent/b8bde431bb531fc7?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.