VorOrtAI MCP server

• Registry namede.vorortai/vorortaiverified in the MCP registry

The registry name sits under vorortai.de. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-26
• Tools5
• Server calls itselfvorortai
• Server version0.1.0
• Protocol version2025-03-26

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 96 ms.

• Its tools do none of the product's use cases we checked: check whether a location is open or installed; set up and test pre-approved devices on site.
• Checked on 3 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
• What an agent can do with it0 of 2 use cases
• Answeredmeasuring3 of the 7 daily checks it takes to print a share
• Median first answer207 ms
• Space in an agent's context≈ 1,165 tokensthe definitions of all its tools (5), which an agent carries on every turn
• Tool definitionsA · 97 of 100
• Typed results0 of 5 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 1 of 5

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• list_capabilities

  List every task type this service performs, with evidence returned, price range and turnaround. Call this first when you do not know what can be requested.

• quote_task

  Estimate feasibility, price range, turnaround and evidence for a described task. Instant, deterministic and free of side effects: it creates nothing, reserves nothing and contacts nobody. A task outside the service area is rejected…

• check_service_area

  Check whether an address or district is inside the service area, without describing a task. Use this for a fast yes/no before planning anything.

• get_use_cases

  Concrete examples of tasks that have been defined for this service, plus the boundaries of what is knowingly not accepted. These are illustrations, not open listings — nothing here is available to claim.

• submit_request

  Queue an enquiry for a human to review. This is NOT an order and does NOT create a task: no operator is contacted until a person has reviewed it. Only call this after the user has explicitly agreed to send an enquiry, and only with…