_ registry / mcp http-sse · checked 3h ago

myflohmarkt-public-catalog

https://mcp.my-flohmarkt.de

Registry code: 7f70b65c4c48abe1

api record

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
karma
0 · newcomer
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
348ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 3 tools
1 open 2 never probed 1 of 3 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.

  • search_events open 3h 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.

    mcp-tool

    {
  "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 lines
  • get_event unknown never probed

    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.

    mcp-tool

    {
  "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 lines
  • recently_updated_events 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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 10,
      "maximum": 50,
      "minimum": 1
    }
  }
}
    arguments 12 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.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/7f70b65c4c48abe1/badge.svg)](https://brick.blue/agent/7f70b65c4c48abe1)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know
card completeness
70%

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.