de.roboterradar/radarscore
REMOTE · ROBOTERRADAR.DE · SCANNED AUG 20
Evidence-based humanoid robot data: RadarScore ratings, evidence grades A-D, prices, EU availability
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 5 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 Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 839 tokens (~167/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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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 · roboterradar.de
claude mcp add --transport http de-roboterradar-radarscore https://roboterradar.de/mcp
[mcp_servers.de-roboterradar-radarscore] url = "https://roboterradar.de/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"de-roboterradar-radarscore": {
"type": "remote",
"url": "https://roboterradar.de/mcp",
"enabled": true
}
}
} openclaw mcp add de-roboterradar-radarscore --url https://roboterradar.de/mcp --transport streamable-http
mcp_servers:
de-roboterradar-radarscore:
url: "https://roboterradar.de/mcp" {
"mcpServers": {
"de-roboterradar-radarscore": {
"type": "http",
"url": "https://roboterradar.de/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 60
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://roboterradar.de/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=roboterradar.de | CN=WE1,O=Google Trust Services,C=US | 4 Jul 2026 | 3 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | d8177e1210b705a1311e1a3cbd005e1 |
| SANs: roboterradar.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 roboterradar.de. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| de. | present | 26755 | 8 | Verified |
| roboterradar.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 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://roboterradar.de/mcp | Verified | 200 | |
| http (plaintext) | http://roboterradar.de/mcp | HTTPS enforced | 301 | https://roboterradar.de/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.
compare_robots Roboter vergleichen ~80
Stellt 2–4 Modelle nebeneinander: Preise, Verfügbarkeit, Technik-Eckdaten und alle RadarScore-Achsen mit Evidenzgraden. / Side-by-side comparison of 2–4 robots.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | yes | Modell-Schlüssel, z. B. ["unitree-g1", "unitree-r1"] |
No output schema declared.
No examples provided.
dataset_info Datensatz-Metadaten ~66
Version, Datenstand, Lizenz (CC BY 4.0), Zitiervorschlag, Methodik-Link, Modell-/Bewertungszahlen und die stabilen Download-URLs (CSV/JSON) des RadarScore-Datensatzes. / Dataset metadata, license and citation.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_robot Roboter-Akte abrufen ~142
Vollständiger Datensatz-Eintrag eines Modells: Preise mit Provenienz, Technik, alle 6 RadarScore-Achsen, Autonomie-Ampel, Evidenz-Zusammenfassung je Achse und Prüfdaten. Mit include_belege=true zusätzlich jeder Einzelbeleg (Zitat, Quelle, Archivlink). / Full record for one robot by id.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Modell-Schlüssel (Slug) aus search_robots, z. B. "unitree-g1" |
| include_belege | boolean | – | true = alle Einzelbelege mit Zitaten statt nur der Evidenz-Zusammenfassung (deutlich größere Antwort) |
No output schema declared.
No examples provided.
import_cost DE-Importkosten rechnen ~183
Rechnet die Import-Faustregel für den Direktimport eines Roboters aus China/USA nach Deutschland: Warenwert (USD×Kurs) + Versand + 2,7 % Zoll + 19 % Einfuhrumsatzsteuer. Entweder modell_id (nutzt den dokumentierten US-Listenpreis) oder preis_usd frei angeben. / German landed-cost estimate for importing a robot from China/US.
| Name | Type | Req | Description |
|---|---|---|---|
| modell_id | string | – | Modell-Schlüssel eines CN/US-Modells mit realem Listenpreis (z. B. "unitree-g1") |
| preis_usd | number | – | Alternativ: freier US-Listenpreis in USD |
| versand_eur | number | – | Luftfracht/Spedition in EUR; Default nach Gewichtsklasse (250 / 800 / 1.500 €) |
No output schema declared.
No examples provided.
search_robots Roboter suchen & filtern ~247
Durchsucht den RadarScore-Datensatz (humanoide Roboter + Quadrupeds) mit Filtern für Kategorie, DACH-Verfügbarkeit, Herkunftsland und Maximalpreis. Liefert Kompakt-Zeilen mit Preisen, Gesamtscore und Autonomie-Ampel. / Search the evidence-based humanoid-robot dataset with filters.
| Name | Type | Req | Description |
|---|---|---|---|
| herkunftsland | string | – | ISO-Ländercode des Herstellers, z. B. DE, US, CN, NO, CH |
| kategorie | string | – | Nur eine Kategorie |
| max_preis_eur | number | – | Nur Modelle mit dokumentiertem EUR-Listenpreis bis zu diesem Betrag |
| query | string | – | Freitext über Name/Hersteller, z. B. "unitree" oder "neo" |
| sort | string | – | Sortierung: RadarScore gesamt (absteigend, Default) · EUR-Preis (aufsteigend, Modelle ohne EUR-Preis zuletzt) · Name |
| verfuegbar_dach | boolean | – | true = nur Modelle, die in Deutschland real bestellbar sind (status.dach = "ja") |
No output schema declared.
No examples provided.