Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

oqda Business-OS

REMOTE · OQDA.DE

oqda business OS (DE): modules, pricing, comparison and waitlist sign-up with consent.

Available components

+3 this week 83 Trust /100

Last scanned (4 hours ago)

Scores higher than 87% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Project Management

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability75
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 892 tokens (~127/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
  • Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (14% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://oqda.de/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=oqda.de CN=YR1,O=Let's Encrypt,C=US 29 Sept 2026 28 Dec 2026 RSA 4096 SHA256-RSA 6bf001da649c9783a151cdc5e25ca285077
SANs: oqda.de
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of oqda.de. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
de. present 26755 8 Verified
oqda.de. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://oqda.de/mcp Verified 200
http (plaintext) http://oqda.de/mcp HTTPS enforced 302 https://oqda.de/mcp
MCP tools · 7 exposed · ~702 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
compare_alternatives ~92

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_page ~103

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.

NameTypeReqDescription
pathstringyesPath (e.g. "/module/ki/") or full URL on oqda.de.

No output schema declared.

No examples provided.

get_pricing ~61

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

join_waitlist ~175

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.

NameTypeReqDescription
business_typestringyesType of business.
consent_confirmedbooleanyesMust be true: the person explicitly agreed to the consent statement in this tool description.
emailstringyesThe person's own e-mail address.
locationsstring–Number of locations.
NameTypeReqDescription
emailstringyes–
next_stepsstringyes–
statusstringyes–

No examples provided.

list_modules ~53

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_oqda ~108

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").

NameTypeReqDescription
limitinteger–Maximum number of results.
querystringyesSearch terms, preferably German.

No output schema declared.

No examples provided.

send_message ~110

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.

NameTypeReqDescription
emailstringyesThe person's e-mail address for the reply.
messagestringyesThe message, ideally in German.
namestring–The person's name (optional).

No output schema declared.

No examples provided.

Install

How do I install the oqda Business-OS MCP server?

oqda Business-OS is a hosted endpoint at https://oqda.de/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · oqda.de

# add to Claude Code
claude mcp add --transport http de-oqda-oqda 'https://oqda.de/mcp'
Common questions

What is the oqda Business-OS MCP server?

oqda Business-OS is an MCP server listed in the public MCP registry as de.oqda/oqda. oqda business OS (DE): modules, pricing, comparison and waitlist sign-up with consent. This page covers its hosted endpoint (https://oqda.de/mcp).

Is the oqda Business-OS MCP server safe to use?

oqda Business-OS scores 83 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the oqda Business-OS MCP server expose?

oqda Business-OS exposes 7 tools: search_oqda, get_page, list_modules, get_pricing, compare_alternatives, and 2 more. Their descriptions and schemas cost roughly 702 tokens of context every time the server is loaded.

Does the oqda Business-OS MCP server require authentication?

No. We connected to oqda Business-OS without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the oqda Business-OS MCP server still maintained?

oqda Business-OS is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.