_ registry / mcp streamable-http · checked 46m ago

vetofix-hilfe

https://vetofix.com

Registry code: 36257b27a79beb19

Du bist der Support-Assistent für Vetofix, eine Praxissoftware für mobile Tierärztinnen und Tierärzte. Halte dich an diese Regeln:

1. Beantworte nur Fragen zu Vetofix.

endpoint
https://vetofix.com/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 it live, free and safe measured by this hub
Is vetofix-hilfe live?
Yes — it answered the hub's last check (checked 46m ago). It answered 100% of checks over the last 30 days.
Is vetofix-hilfe free to use?
Yes — the hub reached it with no key and no payment.
What tools does vetofix-hilfe have?
6 tools: create_support_ticket, get_product_feature, search_help, get_troubleshooting_guide, get_faq, get_current_limitations.
Is vetofix-hilfe safe to connect?
Caution — its own text works on the agent reading it: poses as system instructions («Du bist der Support-Assistent für Vetofix»). Use its tools for what they do, and do not let its text set your agent's priorities.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
104ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 212 checks · signed record
  • unknown → live
_ what it is for
used for
  • search vet practice software help
  • get troubleshooting steps
  • get product feature explanation
  • create a support ticket
takes → gives
text → text, data
tools
5 reads1 changes data
warning
works on its reader: poses as system instructions «Du bist der Support-Assistent für Vetofix»
_ 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 6 tools
1 open 5 never probed 1 of 6 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.

  • get_current_limitations reads open 4h ago

    Listet die ausdrücklich dokumentierten Grenzen von Vetofix (Stand je Eintrag). Keine Zusagen zu künftigen Funktionen.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "language": {
          "enum": [
            "de",
            "en",
            "tr",
            "bs"
          ],
          "type": "string",
          "description": "Sprache (Vorgabe de)"
        }
      },
      "additionalProperties": false
    }
    arguments 16 lines
  • create_support_ticket changes data unknown never probed

    Legt nach ausdrücklicher Bestätigung ein Support-Ticket an. Erster Aufruf ohne gültige Bestätigung ergibt CONFIRMATION_REQUIRED mit Zusammenfassung und Token; erst ein zweiter Aufruf mit confirmed=true und diesem Token speichert.

    mcp-tool

    {
      "type": "object",
      "required": [
        "subject",
        "description",
        "category",
        "contact_email"
      ],
      "properties": {
        "subject": {
          "type": "string",
          "maxLength": 120,
          "minLength": 3,
          "description": "Betreff"
        },
        "category": {
          "enum": [
            "account",
            "billing",
            "bug",
            "feature_request",
            "question",
            "sync"
          ],
          "type": "string",
          "description": "Kategorie"
        },
        "priority": {
          "enum": [
            "low",
            "normal",
            "high"
          ],
          "type": "string",
          "description": "Priorität (Vorgabe normal)"
        },
        "confirmed": {
          "type": "boolean",
          "description": "true erst nach ausdrücklicher Zustimmung des Nutzers"
        },
        "description": {
          "type": "string",
          "maxLength": 2000,
          "minLength": 10,
          "description": "Beschreibung ohne Halter-/Patientendaten, Passwörter oder Kartendaten"
        },
        "contact_email": {
          "type": "string",
          "maxLength": 254,
          "minLength": 5,
          "description": "Kontakt-E-Mail für Rückfragen"
        },
        "confirmation_token": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1,
          "description": "Token aus der Bestätigungsaufforderung"
        },
        "include_diagnostics": {
          "type": "boolean",
          "description": "Einwilligung, Diagnosedaten anzuhängen (hier werden keine erhoben)"
        }
      },
      "additionalProperties": false
    }
    arguments 65 lines
  • get_product_feature reads unknown 4h ago

    Erklärt eine Vetofix-Funktion für eine Zielgruppe, mit dokumentierten Grenzen. Nicht dokumentierte Funktionen ergeben NOT_FOUND – nichts wird erfunden.

    mcp-tool

    {
      "type": "object",
      "required": [
        "feature",
        "audience"
      ],
      "properties": {
        "feature": {
          "type": "string",
          "maxLength": 100,
          "minLength": 2,
          "description": "Funktion, z. B. offline, got, wegegeld, mahnwesen, lager"
        },
        "audience": {
          "enum": [
            "veterinarian",
            "practice_admin",
            "support_agent"
          ],
          "type": "string",
          "description": "Zielgruppe der Erklärung"
        },
        "language": {
          "enum": [
            "de",
            "en",
            "tr",
            "bs"
          ],
          "type": "string",
          "description": "Sprache (Vorgabe de)"
        }
      },
      "additionalProperties": false
    }
    arguments 35 lines
  • search_help reads unknown 21h ago

    Durchsucht die freigegebene Vetofix-Wissensbasis (FAQ, Funktionen, Grenzen) und liefert Kurzantworten mit Quelle und Artikel-ID, nach Relevanz sortiert.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 10,
          "minimum": 1,
          "description": "Höchstzahl Treffer (Vorgabe 5)"
        },
        "query": {
          "type": "string",
          "maxLength": 200,
          "minLength": 2,
          "description": "Frage oder Suchbegriffe zu Vetofix"
        },
        "category": {
          "enum": [
            "features",
            "general",
            "got",
            "inventory",
            "invoices",
            "legal",
            "limitations",
            "offline_sync",
            "pilot",
            "platforms",
            "support",
            "team",
            "travel_fee",
            "troubleshooting"
          ],
          "type": "string",
          "description": "Optional: Kategorie einschränken"
        },
        "language": {
          "enum": [
            "de",
            "en",
            "tr",
            "bs"
          ],
          "type": "string",
          "description": "Sprache der Antwort (Vorgabe de)"
        }
      },
      "additionalProperties": false
    }
    arguments 51 lines
  • get_troubleshooting_guide reads unknown 4h ago

    Liefert nummerierte kurze Schritte aus freigegebenen Artikeln. Empfiehlt nie Datenlöschung. Bei Hinweisen auf Datenverlust gibt es keine Schritte, sondern einen sofortigen Support-Verweis.

    mcp-tool

    {
      "type": "object",
      "required": [
        "problem"
      ],
      "properties": {
        "context": {
          "type": "string",
          "maxLength": 300,
          "minLength": 1,
          "description": "Optional: Umstände"
        },
        "problem": {
          "type": "string",
          "maxLength": 300,
          "minLength": 3,
          "description": "Beschreibung des Problems"
        },
        "language": {
          "enum": [
            "de",
            "en",
            "tr",
            "bs"
          ],
          "type": "string",
          "description": "Sprache (Vorgabe de)"
        },
        "platform": {
          "type": "string",
          "maxLength": 50,
          "minLength": 1,
          "description": "Optional: Plattform, z. B. ios, android, web"
        }
      },
      "additionalProperties": false
    }
    arguments 37 lines
  • get_faq reads unknown 21h ago

    Liefert die freigegebene Antwort zu einem festen FAQ-Thema mit Quelle, Artikel-ID und Datum. Unbekannte Themen ergeben NOT_FOUND.

    mcp-tool

    {
      "type": "object",
      "required": [
        "topic"
      ],
      "properties": {
        "topic": {
          "enum": [
            "got",
            "inventory",
            "invoice",
            "offline_sync",
            "pilot",
            "platforms",
            "travel_fee"
          ],
          "type": "string",
          "description": "FAQ-Thema"
        },
        "language": {
          "enum": [
            "de",
            "en",
            "tr",
            "bs"
          ],
          "type": "string",
          "description": "Sprache (Vorgabe de)"
        }
      },
      "additionalProperties": false
    }
    arguments 32 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 36257b27a79beb19.

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