de.vorortai/vorortai
REMOTE · VORORTAI.DE · SCANNED AUG 20
Real-world tasks in Hamburg: quote, check service area, submit an enquiry for human review.
Available components
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 →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 746 tokens (~149/item across 5 items; 5 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 Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 95% of tool parameters carry a description.Partial
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · vorortai.de
claude mcp add --transport http de-vorortai-vorortai https://vorortai.de/api/mcp
[mcp_servers.de-vorortai-vorortai] url = "https://vorortai.de/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"de-vorortai-vorortai": {
"type": "remote",
"url": "https://vorortai.de/api/mcp",
"enabled": true
}
}
} openclaw mcp add de-vorortai-vorortai --url https://vorortai.de/api/mcp --transport streamable-http
mcp_servers:
de-vorortai-vorortai:
url: "https://vorortai.de/api/mcp" {
"mcpServers": {
"de-vorortai-vorortai": {
"type": "http",
"url": "https://vorortai.de/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 20 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 14 Aug 26 62
First indexed and scored.
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 20 Aug 2026 · Probed https://vorortai.de/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=vorortai.de | CN=WE1,O=Google Trust Services,C=US | 8 Aug 2026 | 6 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 9baa8ca339c7db31137450f6dab75146 |
| SANs: vorortai.de | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of vorortai.de. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| de. | present | 26755 | 8 | Verified |
| vorortai.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 |
|---|---|
| content-security-policy | default-src 'self'; base-uri 'self'; connect-src 'self'; font-src 'self' data:; form-action 'self'; frame-ancestors 'none'; img-src 'self' data: blob:; media-src 'self'; object-src 'none'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; worker-src 'self' blob: |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(self), payment=() |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://vorortai.de/api/mcp | Verified | 200 | |
| http (plaintext) | http://vorortai.de/api/mcp | HTTPS enforced | 302 | https://vorortai.de/api/mcp |
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.
check_service_area Check the service area ~50
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.
| Name | Type | Req | Description |
|---|---|---|---|
| location | string | yes | Address, postal code or district. |
No output schema declared.
No examples provided.
get_use_cases Get example tasks ~46
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_capabilities List capabilities ~39
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
quote_task Quote a real-world task ~185
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 immediately.
| Name | Type | Req | Description |
|---|---|---|---|
| capability | string | – | Optional capability id from `list_capabilities`; inferred from the text otherwise. |
| delivery | string | – | Restrict matching to on-site work (someone travels to a place) or remote work (someone tests software from wherever they are). Inferred from the description when omitted. |
| evidence | array | – | Evidence the requester wants back. |
| location | string | – | Address or district. Only used for on-site work, to confirm the service area. Ignored for remote work. |
| locations | integer | – | Number of locations, for capabilities priced per location. |
| task | string | yes | What should happen on site, in plain language. |
No output schema declared.
No examples provided.
submit_request Submit a request for human review ~263
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 contact details the user provided. Requires `consent: true`.
| Name | Type | Req | Description |
|---|---|---|---|
| budgetEur | number | – | Budget ceiling in euro. |
| capability | string | – | Capability id, if already known from a quote. |
| company | string | – | Organisation on whose behalf the request is made. |
| consent | boolean | yes | Must be true. Confirms the user agreed to be contacted about this request. |
| contactName | string | yes | Name of the person making the request. |
| deadline | string | – | Free text or ISO date. |
| string | yes | Address the answer is sent to. | |
| evidence | array | – | Evidence the requester wants back. |
| idempotencyKey | string | – | Stable key so a retry cannot queue the same request twice. |
| location | string | yes | Address in the service area. |
| locations | integer | – | – |
| source | string | – | How the requester found this service. |
| taskDescription | string | yes | What should happen on site, including anything a reviewer needs to judge it. |
No output schema declared.
No examples provided.