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

vonfrauen

https://www.vonfrauen.de

Registry code: ad651a5e5251fe3c

api record

Finde öffentliche Anbieterinnen und Leistungen bei vonFrauen. Buchung bedeutet zunächst eine von der Kundin selbst bestätigte Anfrage auf vonfrauen.de; der Vertrag entsteht erst mit Annahme des Angebots. Erfinde nie Kontaktdaten und kontaktiere Anbieterinnen nicht privat. Zusammenfassungen für Anfragelinks dürfen keine Namen, Telefonnummern, Adressen oder E-Mails enthalten.

endpoint
https://www.vonfrauen.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 it live, free and safe measured by this hub
Is vonfrauen live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is vonfrauen free to use?
Yes — the hub reached it with no key and no payment.
What tools does vonfrauen have?
4 tools: get_provider, prepare_inquiry, search_providers, list_categories.
Is vonfrauen 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
100%

90 days 100%· all time 100%

latency
162ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 4 tools
2 open 2 never probed 2 of 4 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_providers open 1h ago

    Suche in den öffentlichen Profilen mit denselben Such- und Stadtregeln wie im Verzeichnis. category ist ein Branchen-Slug aus list_categories. Beispielprofile sind nicht direkt anfragbar; vonFrauen-Vermittlung ist die plattformeigene persönliche Suche. Ergebnisse garantieren keine Verfügbarkeit.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "city": {
          "enum": [
            "Berlin",
            "Bremen",
            "Dresden",
            "Düsseldorf",
            "Frankfurt a.M.",
            "Hamburg",
            "Köln",
            "Leipzig",
            "München",
            "Stuttgart",
            "Deutschlandweit"
          ],
          "type": "string"
        },
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 20,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "maxLength": 80
        },
        "category": {
          "type": "string",
          "pattern": "^[a-z0-9]+(?:-[a-z0-9]+)*$",
          "maxLength": 160,
          "minLength": 1
        }
      },
      "additionalProperties": false
    }
    arguments 39 lines
  • list_categories open 1h ago

    Liste Branchen mit Slug und Namen sowie Städte aus dem aktuellen öffentlichen Anbieterinnenbestand. Beispielprofile und die plattformeigene vonFrauen-Vermittlung zählen nicht als Fachanbieterinnen; leere Branchen und Städte werden nicht behauptet.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {},
      "additionalProperties": false
    }
    arguments 6 lines
  • get_provider unknown 1h ago

    Lies ein öffentliches Profil anhand seines kanonischen Profil-Slugs, einschließlich öffentlicher Leistungen, Preise und Anfragelinks. Beispielprofile sind nicht direkt anfragbar. Private Kontakt- und Kontodaten werden nicht ausgegeben.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "pattern": "^[a-z0-9]+(?:-[a-z0-9]+)*$",
          "maxLength": 160,
          "minLength": 1
        }
      },
      "additionalProperties": false
    }
    arguments 16 lines
  • prepare_inquiry unknown never probed

    Bereite ausschließlich einen Anfragelink vor, ohne eine Anfrage zu senden oder Daten zu speichern. summary ist eine knappe Zusammenfassung des Anliegens in 2–5 Sätzen, höchstens 800 Zeichen, ohne Namen, Telefonnummern, Adressen, E-Mails oder andere personenbezogene Angaben. Die Nutzerin sieht und bearbeitet den Text vor dem Absenden. need ist ausschließlich ein Branchen-Slug aus list_categories, kein Freitext. Für Direktanfragen providerSlug und optional eine zugehörige serviceSlug aus dem öffentlichen Profil verwenden; ohne providerSlug startet die persönliche Vermittlung.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "summary"
      ],
      "properties": {
        "city": {
          "enum": [
            "Berlin",
            "Bremen",
            "Dresden",
            "Düsseldorf",
            "Frankfurt a.M.",
            "Hamburg",
            "Köln",
            "Leipzig",
            "München",
            "Stuttgart",
            "Deutschlandweit"
          ],
          "type": "string"
        },
        "need": {
          "type": "string",
          "pattern": "^[a-z0-9]+(?:-[a-z0-9]+)*$",
          "maxLength": 160,
          "minLength": 1
        },
        "summary": {
          "type": "string",
          "maxLength": 800,
          "minLength": 1,
          "description": "Knappe Zusammenfassung in 2–5 Sätzen ohne personenbezogene Angaben, insbesondere ohne Namen, Telefonnummern, Adressen oder E-Mails; höchstens 800 Zeichen."
        },
        "serviceSlug": {
          "type": "string",
          "pattern": "^[a-z0-9]+(?:-[a-z0-9]+)*$",
          "maxLength": 160,
          "minLength": 1
        },
        "providerSlug": {
          "type": "string",
          "pattern": "^[a-z0-9]+(?:-[a-z0-9]+)*$",
          "maxLength": 160,
          "minLength": 1
        }
      },
      "additionalProperties": false
    }
    arguments 50 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.

_ 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 ad651a5e5251fe3c.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/ad651a5e5251fe3c/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/ad651a5e5251fe3c/badge.svg)](https://brick.blue/agent/ad651a5e5251fe3c?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 know
card completeness
80%

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.