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

oqda

https://oqda.de

Registry code: 19bb577058bc7963

api record

oqda is a business operating system (web app) for fitness studios, therapy and medical practices, agencies, offices and testing labs in Germany (B2B, German language): duty roster with an AI optimizer, online booking, team chat, processes, an AI agent, marketing, learning and controlling in one product. All site content is German.

Use search_oqda or get_page to answer questions with facts from oqda.de, list_modules for what oqda does, get_pricing for prices, compare_alternatives for how oqda differs from separate tools and when it is not a fit.

endpoint
https://oqda.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 it live, free and safe measured by this hub
Is oqda live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is oqda free to use?
Yes — the hub reached it with no key and no payment.
What tools does oqda have?
7 tools: search_oqda, get_pricing, join_waitlist, send_message, get_page, compare_alternatives, list_modules.
Is oqda 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
104ms

last good check

priced tools
0

of 7 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 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.

  • compare_alternatives open 1h ago

    Explains how oqda differs from running separate tools (roster spreadsheet, booking calendar, chat groups, learning platform, reporting): which tool each oqda feature replaces, how the modules work together, what it costs, and when oqda is NOT a fit (no patient records, no LIMS, no SMS, no payroll). Use it when a user asks for alternatives or whether oqda suits them.

    mcp-tool

    {
      "type": "object",
      "additionalProperties": false
    }
    arguments 4 lines
  • list_modules open 1h ago

    Lists all eight oqda modules (Dienstplan, Termine, Team, Prozesse, KI-Agent, Marketing, Lernen, Controlling) with their features, individual prices and page URLs, plus the platform core included in every module.

    mcp-tool

    {
      "type": "object",
      "additionalProperties": false
    }
    arguments 4 lines
  • search_oqda unknown never probed

    Full-text search over all pages of oqda.de (modules, features, pricing, industries, comparison, company, legal). Returns the best matching pages with URL and snippet; read a page in full with get_page. Content is German, so German search terms work best (e.g. "Dienstplan", "Zeiterfassung", "Praxis", "Preise").

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 5,
          "maximum": 10,
          "minimum": 1,
          "description": "Maximum number of results."
        },
        "query": {
          "type": "string",
          "maxLength": 200,
          "minLength": 2,
          "description": "Search terms, preferably German."
        }
      },
      "additionalProperties": false
    }
    arguments 22 lines
  • get_pricing unknown never probed

    Returns oqda pricing: packages (Single, Multi, Enterprise) per location and month, individual module prices, conditions (no setup fee, cancel monthly, no per-user pricing) and usage-based costs. Prices in EUR, excluding VAT, for businesses only.

    mcp-tool

    {
      "type": "object",
      "additionalProperties": false
    }
    arguments 4 lines
  • join_waitlist unknown never probed

    Puts a person on the oqda waitlist (free and non-binding; oqda contacts them personally when a spot opens, then they decide). Only call this when the person asked for it, with their own e-mail address, and only after they explicitly agreed to this consent statement (German, show it to them): "Ihr dürft mich per E-Mail kontaktieren, sobald ein Platz auf der Warteliste frei wird." Never guess or invent an e-mail address. Calling again with the same e-mail has no further effect.

    mcp-tool

    {
      "type": "object",
      "required": [
        "email",
        "business_type",
        "consent_confirmed"
      ],
      "properties": {
        "email": {
          "type": "string",
          "format": "email",
          "maxLength": 200,
          "description": "The person's own e-mail address."
        },
        "locations": {
          "enum": [
            "Einer",
            "2 bis 10",
            "Mehr als 10"
          ],
          "type": "string",
          "description": "Number of locations."
        },
        "business_type": {
          "enum": [
            "Fitnessstudio",
            "Praxis oder Gesundheit",
            "Büro oder Dienstleister",
            "Labor oder Prüfbetrieb",
            "Etwas anderes"
          ],
          "type": "string",
          "description": "Type of business."
        },
        "consent_confirmed": {
          "type": "boolean",
          "const": true,
          "description": "Must be true: the person explicitly agreed to the consent statement in this tool description."
        }
      },
      "additionalProperties": false
    }
    arguments 42 lines
  • send_message unknown never probed

    Forwards a question or request from the person to the oqda team (e.g. whether oqda fits their business, an Enterprise offer for 11+ locations, a data protection request). The team replies personally by e-mail. Only send on behalf of the person, with their own e-mail address.

    mcp-tool

    {
      "type": "object",
      "required": [
        "email",
        "message"
      ],
      "properties": {
        "name": {
          "type": "string",
          "maxLength": 120,
          "description": "The person's name (optional)."
        },
        "email": {
          "type": "string",
          "format": "email",
          "maxLength": 200,
          "description": "The person's e-mail address for the reply."
        },
        "message": {
          "type": "string",
          "maxLength": 4000,
          "minLength": 5,
          "description": "The message, ideally in German."
        }
      },
      "additionalProperties": false
    }
    arguments 27 lines
  • get_page unknown 1h ago

    Returns one page of oqda.de as Markdown. Pass a path or URL, e.g. "/", "/module/dienstplan/", "/module/termine/buchungsseite/", "/branchen/praxen/", "/preise/", "/vergleich/", "/ueber-uns/", "/datenschutz/". list_modules and search_oqda return valid paths.

    mcp-tool

    {
      "type": "object",
      "required": [
        "path"
      ],
      "properties": {
        "path": {
          "type": "string",
          "maxLength": 300,
          "minLength": 1,
          "description": "Path (e.g. \"/module/ki/\") or full URL on oqda.de."
        }
      },
      "additionalProperties": false
    }
    arguments 15 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 19bb577058bc7963.

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