die-partei-reutlingen
https://www.die-partei-reutlingen.de
Registry code: c717763850a99400
Nur öffentliche Lesefunktionen. search/fetch sind kompakte Such-/Lesealiase mit stabilen IDs. Für den nächsten lokalen Termin termine_suchen mit {} aufrufen und next_event oder next_event_message nutzen. Für Ansprechpartner inhalte_suchen mit der Frage „Wer ist Ansprechpartner?“ aufrufen. Quellen-URL und Datum zitieren; information_status für die zeitliche Einordnung beachten. Keine Redaktion, Entwürfe oder Schreibfunktionen.
- endpoint
- https://www.die-partei-reutlingen.de/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 die-partei-reutlingen live?
- Yes — it answered the hub's last check (checked 19h ago). It answered 100% of checks over the last 30 days.
- Is die-partei-reutlingen free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does die-partei-reutlingen have?
- 6 tools: fetch, inhalt_lesen, search, beitraege_suchen, inhalte_suchen, termine_suchen.
- Is die-partei-reutlingen 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.
beitraege_suchen open 19h ago
Sucht veröffentlichte Nachrichten, z. B. mit {"thema":"Gemeinderat"}. Nutze url als Quelle und published_at sowie information_status zur zeitlichen Einordnung.
{ "type": "object", "required": [], "properties": { "q": { "type": "string", "maxLength": 100, "description": "Suchtext; leer oder weggelassen liefert die neuesten Ergebnisse." }, "jahr": { "type": "integer", "maximum": 2100, "minimum": 2000, "description": "Veröffentlichungsjahr." }, "seite": { "type": "integer", "maximum": 10000, "minimum": 1, "description": "Ergebnisseite ab 1; zehn Einträge je Seite. Seiten hinter dem Ende liefern eine leere data-Liste." }, "thema": { "type": "string", "maxLength": 100, "description": "Exakter öffentlicher Themenname, beispielsweise Gemeinderat." } }, "additionalProperties": false }arguments 29 linesinhalte_suchen open 19h ago
Für Ansprechpartner z. B. {"q":"Wer ist Ansprechpartner?"}, für Positionen nach dem konkreten Thema suchen. Zitiere url und published_at. Verwende information_status zur Einordnung: current ist redaktionell aktuell, historical historisch, null ungeprüft. Für Veranstaltungen verwende termine_suchen.
{ "type": "object", "required": [], "properties": { "q": { "type": "string", "maxLength": 200, "minLength": 2, "description": "Suchbegriff oder frei formulierte Frage." }, "typ": { "enum": [ "post", "page" ], "type": "string" }, "jahr": { "type": "integer", "maximum": 2100, "minimum": 1900 }, "page": { "type": "integer", "maximum": 10000, "minimum": 1 } }, "additionalProperties": false }arguments 30 linestermine_suchen open 19h ago
Wann ist der nächste lokale Termin? Rufe dieses Werkzeug mit {} auf und verwende next_event mit url und event.starts_at. Bei null verwende next_event_message. Für frühere Termine nutze {"vergangen":true}. In data zeigt event.time_state die zeitliche Lage und event.status eine Absage oder Verschiebung.
{ "type": "object", "required": [], "properties": { "q": { "type": "string", "maxLength": 100, "description": "Suchtext im Titel, Text oder der Ortsangabe." }, "seite": { "type": "integer", "maximum": 10000, "minimum": 1, "description": "Ergebnisseite ab 1; zehn Einträge je Seite. Seiten hinter dem Ende liefern eine leere data-Liste." }, "vergangen": { "type": "boolean", "description": "true für vergangene Veranstaltungen, sonst kommende und laufende Termine." } }, "additionalProperties": false }arguments 22 linesfetch unknown never probed
Read one published source by its stable ID from search. Returns full Markdown, canonical URL, dates and editorial information status.
{ "type": "object", "required": [ "id" ], "properties": { "id": { "type": "string", "pattern": "^[0-9]+$", "maxLength": 20, "minLength": 1 } }, "additionalProperties": false }arguments 15 linesinhalt_lesen unknown never probed
Liest eine veröffentlichte Quelle vollständig, z. B. {"slug":"kontakt"}. Zitiere die kanonische url und beachte published_at und information_status.
{ "type": "object", "required": [ "slug" ], "properties": { "slug": { "type": "string", "pattern": "^[a-z0-9]+(?:-[a-z0-9]+)*$", "maxLength": 190, "minLength": 1, "description": "Letzter Pfadteil der kanonischen Inhaltsadresse, beispielsweise kreisverband." } }, "additionalProperties": false }arguments 16 linessearch unknown never probed
Search public articles and information pages. Returns stable IDs and canonical URLs; use fetch to read a result. For a contact, try {"query":"Wer ist Ansprechpartner?"}. For the next local event, call termine_suchen with {} and read next_event or next_event_message. Use {"vergangen":true} for past events.
{ "type": "object", "required": [ "query" ], "properties": { "query": { "type": "string", "maxLength": 200, "minLength": 2 } }, "additionalProperties": false }arguments 14 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 idc717763850a99400.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/c717763850a99400/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/c717763850a99400?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.