ullasopskrifter
Registry code: 73ba99ea3d6e306b
Read-only Danish recipes, ingredients and categories from ullasopskrifter.dk: search and browse.
from a public catalogue that lists it, not from the operator
- endpoint
- https://ullasopskrifter.dk/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 ullasopskrifter live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is ullasopskrifter free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does ullasopskrifter have?
- 6 tools: search_recipes, recipes_get, ingredients_search_recipes, categories_recipes, categories_list, recipes_list.
- Is ullasopskrifter 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.
90 days 100%· all time 100%
last good check
of 6 tools
- unknown → live
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.
through this hub
successful
what callers paid
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.
categories_list open 1h ago
List recipe categories as a tree with published recipe counts.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linesrecipes_list open 1h ago
List published recipes with pagination (title, slug, servings, image URL, and page URL).
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "page": { "type": "integer", "maximum": 9007199254740991, "minimum": 1, "description": "Page number (default 1)" }, "limit": { "type": "integer", "maximum": 100, "minimum": 1, "description": "Page size (default 20, max 100 on stdio; HTTP caps at 50)" } } }arguments 18 linessearch_recipes unknown never probed
Full-text search across published recipe titles, ingredients, and instructions.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "q" ], "properties": { "q": { "type": "string", "minLength": 1, "description": "Search query" } } }arguments 14 linesrecipes_get unknown never probed
Get one published recipe by numeric id or slug (ingredients, method, categories, image and page URL).
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "id_or_slug" ], "properties": { "id_or_slug": { "type": "string", "minLength": 1, "description": "Recipe id or slug" } } }arguments 14 linesingredients_search_recipes unknown never probed
Find published recipes whose ingredient list contains the given text.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "ingredient" ], "properties": { "ingredient": { "type": "string", "minLength": 1, "description": "Ingredient name or fragment to match" } } }arguments 14 linescategories_recipes unknown 1h ago
List published recipes in a category (includes child categories).
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "slug" ], "properties": { "slug": { "type": "string", "minLength": 1, "description": "Category slug" }, "sort": { "type": "string", "description": "Optional sort: title, newest, views, views30 (same as the website)" } } }arguments 18 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id73ba99ea3d6e306b.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/73ba99ea3d6e306b/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/73ba99ea3d6e306b?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.