myflohmarkt-public-catalog
Registry code: 7f70b65c4c48abe1
Search German flea markets (Flohmarkt, Trödelmarkt) by city, PLZ, date range or radius.
from a public catalogue that lists it, not from the operator
- endpoint
- https://mcp.my-flohmarkt.de/mcp
- protocol
- http-sse ·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 myflohmarkt-public-catalog live?
- Yes — it answered the hub's last check (checked 56m ago). It answered 98% of checks over the last 30 days.
- Is myflohmarkt-public-catalog free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does myflohmarkt-public-catalog have?
- 3 tools: get_event, recently_updated_events, search_events.
- Is myflohmarkt-public-catalog 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 97.3%· all time 97.3%
last good check
of 3 tools
- degraded → live
- live → degraded· HTTP 503
- degraded → live
- live → degraded· HTTP 503
- degraded → live
- used for
- find flea markets in a german city
- search flea markets by date and radius
- get flea market details
- takes → gives
- text, data → data
- tools
- 3 reads
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.
search_events reads open 56m ago
Search German flea markets (Flohmarkt, Trödelmarkt, Hofflohmarkt, Kinderflohmarkt, Antik- und Sammlermarkt) from the public my-flohmarkt.de catalogue. Filter by free text, by city name or postal code (PLZ) via the city argument, by date range, or by radius around a coordinate. Radius searches require lat, lng, and radiusKm together (max 100 km). Each hit carries title, date, start and end time, PLZ, city, coordinates, market type and the public event URL. Returns at most 50 results plus a dataAsOf timestamp.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "lat": { "type": "number", "maximum": 90, "minimum": -90 }, "lng": { "type": "number", "maximum": 180, "minimum": -180 }, "city": { "type": "string", "maxLength": 100 }, "limit": { "type": "integer", "default": 10, "maximum": 50, "minimum": 1 }, "query": { "type": "string", "maxLength": 200 }, "dateTo": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$" }, "dateFrom": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$" }, "radiusKm": { "type": "number", "maximum": 100, "minimum": 1 } } }arguments 43 linesget_event reads unknown 56m ago
Get the full public details of one German flea market by its UUID, as returned in the id field of search_events or recently_updated_events: description text, street address, date and opening times, market type and topics, entrance fee and seller stand fee, stand sizes and table rental, whether sellers can still sign up, and the public my-flohmarkt.de event URL. Use it when a search hit is not enough to answer about price, address or what is sold. Unknown or non-public UUIDs return not_found.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "id" ], "properties": { "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)$" } } }arguments 14 linesrecently_updated_events reads unknown never probed
List the most recently added or updated German flea markets in the public my-flohmarkt.de catalogue, newest change first. Use this to see what is new without a search query; use search_events when you know the city, PLZ, date range or area.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "limit": { "type": "integer", "default": 10, "maximum": 50, "minimum": 1 } } }arguments 12 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 id7f70b65c4c48abe1.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/7f70b65c4c48abe1/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/7f70b65c4c48abe1?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.