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

Rohrreinigung in meiner Nähe

https://rohrreinigunginmeinernaehe.de

Registry code: 249f8ebbf2abfa53

api record

Verzeichnis für Rohrreinigungs-Dienste in Deutschland (rohrreinigunginmeinernaehe.de). find_nearby für die Umkreissuche mit Öffnungsstatus, get_business für Details. Daten sind öffentliche Verzeichnisdaten (OSM/Overture) und nicht vom Betrieb bestätigt - das dem Nutzer so sagen. Echte Termine können NICHT gebucht werden; sandbox_* Tools arbeiten nur mit fiktiven Beispiel-Betrieben. sandbox_request_appointment erst nach ausdrücklicher Zustimmung des Nutzers aufrufen.

endpoint
https://rohrreinigunginmeinernaehe.de/mcp
door code
c4a83ac60e3407e7
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 it live, free and safe measured by this hub
Is Rohrreinigung in meiner Nähe live?
Yes — it answered the hub's last check (checked 3h ago). It answered 99% of checks over the last 30 days.
Is Rohrreinigung in meiner Nähe free to use?
Yes — the hub reached it with no key and no payment.
What tools does Rohrreinigung in meiner Nähe have?
7 tools: find_nearby, get_business, sandbox_request_appointment, sandbox_my_bookings, sandbox_hold_slot, search_rohrreinigung, sandbox_list_sample_businesses.
Is Rohrreinigung in meiner Nähe 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
99.4%

90 days 99.1%· all time 99.5%

latency
152ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 691 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
maps travel & places places & venues
used for
  • find drain cleaning services nearby in germany
  • get business opening hours and contact
takes → gives
text → data
tools
5 reads2 changes data
_ 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 7 tools
2 open 5 never probed 2 of 7 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_rohrreinigung reads open 10h ago

    Legacy-Suche nach Rohrreinigungs-Dienste per PLZ, lat/lon oder q - für neue Integrationen find_nearby nutzen.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "q": {
      "type": "string"
    },
    "lat": {
      "type": "number"
    },
    "lon": {
      "type": "number"
    },
    "plz": {
      "type": "string"
    },
    "limit": {
      "type": "integer"
    },
    "booking": {
      "type": "boolean"
    }
  }
}
    arguments 23 lines
  • sandbox_list_sample_businesses reads open 10h ago

    SANDBOX: listet fiktive Beispiel-Betriebe mit freien Terminslots für ein Datum. Zum Testen des Terminflows - echte Betriebe sind nicht buchbar.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "date": {
      "type": "string",
      "description": "YYYY-MM-DD, Standard: morgen"
    }
  }
}
    arguments 9 lines
  • find_nearby reads unknown 10h ago

    Findet Rohrreinigungs-Dienste in Deutschland im Umkreis einer PLZ, Koordinate oder eines Orts, sortiert nach Entfernung, mit Öffnungsstatus zum gewünschten Zeitpunkt (open/closed/unknown). Echte öffentliche Verzeichnisdaten (OpenStreetMap/Overture), nicht vom Betrieb bestätigt. Keine Anmeldung nötig.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "q": {
      "type": "string",
      "description": "Namensfilter (Teilstring)"
    },
    "at": {
      "type": "string",
      "description": "Zeitpunkt ISO 8601 (Europe/Berlin, wenn ohne Zone). Standard: jetzt"
    },
    "lat": {
      "type": "number",
      "description": "Breitengrad (zusammen mit lon), WGS84"
    },
    "lon": {
      "type": "number",
      "description": "Längengrad (zusammen mit lat), WGS84"
    },
    "plz": {
      "type": "string",
      "pattern": "^[0-9]{5}$",
      "description": "Deutsche Postleitzahl, z. B. 10115"
    },
    "city": {
      "type": "string",
      "description": "Ortsname, z. B. Berlin (ungenauer als plz/lat/lon)"
    },
    "limit": {
      "type": "integer",
      "default": 10,
      "maximum": 50,
      "minimum": 1
    },
    "service": {
      "enum": [
        "rohrreinigung",
        "abflussreinigung",
        "kanalreinigung"
      ],
      "type": "string",
      "description": "Nur nach belegter Erwähnung auf einer Website; unvollständige Stichprobe."
    },
    "has_phone": {
      "type": "boolean"
    },
    "open_only": {
      "type": "boolean",
      "description": "Streng: nur Einträge mit auswertbaren Öffnungszeiten und Status open"
    },
    "radius_km": {
      "type": "number",
      "default": 5,
      "maximum": 50,
      "minimum": 0.1,
      "description": "Suchradius in km"
    },
    "has_website": {
      "type": "boolean"
    },
    "open_at_time": {
      "type": "boolean",
      "description": "Nur Einträge, die zum Zeitpunkt nicht sicher geschlossen sind"
    },
    "booking_capable": {
      "type": "boolean",
      "description": "Nur Einträge mit bekannter Online-Buchungsseite"
    },
    "has_booking_url": {
      "type": "boolean",
      "description": "Nur Datensätze mit tatsächlich vorhandener Buchungs-URL"
    }
  }
}
    arguments 74 lines
  • get_business reads unknown 3h ago

    Liefert Adresse, Kontakt, Öffnungszeiten und Öffnungsstatus zu einer ID aus find_nearby.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "at": {
      "type": "string",
      "description": "Zeitpunkt ISO 8601 für den Öffnungsstatus"
    },
    "id": {
      "type": "string",
      "description": "ID aus find_nearby, z. B. osm/node/123"
    }
  }
}
    arguments 16 lines
  • sandbox_request_appointment changes data unknown never probed

    SANDBOX, Anmeldung nötig: wandelt einen Hold in einen Sandbox-Termin um. Erst aufrufen, nachdem der Nutzer ausdrücklich zugestimmt hat (user_approved=true). idempotency_key verhindert Doppelbuchungen: gleicher Key liefert denselben Termin. Kein echter Betrieb wird kontaktiert.

    mcp-tool

    {
  "type": "object",
  "required": [
    "hold_id",
    "user_approved",
    "idempotency_key"
  ],
  "properties": {
    "hold_id": {
      "type": "string"
    },
    "user_approved": {
      "type": "boolean",
      "description": "Nur true, wenn der Nutzer ausdrücklich bestätigt hat"
    },
    "idempotency_key": {
      "type": "string",
      "maxLength": 128,
      "minLength": 8,
      "description": "Eindeutiger Key pro Anfrage, bei Wiederholung identisch"
    }
  }
}
    arguments 23 lines
  • sandbox_my_bookings reads unknown never probed

    SANDBOX, Anmeldung nötig: zeigt eigene Holds und Sandbox-Termine (nur die des angemeldeten Nutzers).

    mcp-tool

    {
  "type": "object",
  "properties": {
    "hold_id": {
      "type": "string"
    },
    "appointment_id": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • sandbox_hold_slot changes data unknown never probed

    SANDBOX, Anmeldung nötig: merkt einen Slot bei einem fiktiven Beispiel-Betrieb für 15 Minuten vor. Liefert hold_id und Ablaufzeit. Es fällt kein Preis an, niemand wird kontaktiert.

    mcp-tool

    {
  "type": "object",
  "required": [
    "business_id",
    "date",
    "start_time",
    "topic"
  ],
  "properties": {
    "date": {
      "type": "string",
      "description": "YYYY-MM-DD"
    },
    "topic": {
      "type": "string",
      "maxLength": 200,
      "description": "Anliegen, z. B. Allgemeine Beratung"
    },
    "start_time": {
      "type": "string",
      "description": "HH:MM im 30-Minuten-Raster"
    },
    "business_id": {
      "type": "string",
      "description": "ID aus sandbox_list_sample_businesses (sample/...)"
    },
    "duration_minutes": {
      "enum": [
        30,
        60,
        90,
        120
      ],
      "type": "integer",
      "default": 30
    }
  }
}
    arguments 38 lines
_ try it over mcp 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 249f8ebbf2abfa53.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/249f8ebbf2abfa53/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/249f8ebbf2abfa53/badge.svg)](https://brick.blue/agent/249f8ebbf2abfa53?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 knowoff the mcp door
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.