Mercedes-Benz Service Reminder – SilberArrows
REMOTE · SILBERARROWS-MCP.NETLIFY.APP
Mercedes-Benz Service A/B reminders, service explanations and warning-light guidance (Dubai).
Available components
Last scanned (20 hours ago)
Scores higher than 69% of remote servers
Reachable. Last reached 4 Nov 2026.
Category IoT and Hardware
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 Security63
- 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
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 290 tokens (~72/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
- Stability observed for 23 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 30 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.
- 28 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.
- 26 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.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
- The server changed its declared name: Mercedes-Benz Service Reminder – SilberArrows → Mercedes-Benz Service Reminder - SilberArrows security
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
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 4 Nov 2026 · Probed https://silberarrows-mcp.netlify.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.netlify.app,O=Netlify\, Inc,L=San Francisco,ST=California,C=US | CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1,O=DigiCert Inc,C=US | 16 Feb 2026 | 19 Mar 2027 | ECDSA 256 | SHA256-RSA | cd5d0afb0611b5bd9d692535c0ca7c4 |
| SANs: *.netlify.app, netlify.app | ||||||
| CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 30 Mar 2021 | 29 Mar 2031 | RSA 2048 | SHA256-RSA | cf5bd062b5602f47ab8502c23ccf066 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of silberarrows-mcp.netlify.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| netlify.app. | 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 |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| 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://silberarrows-mcp.netlify.app/mcp | Verified | 200 | |
| http (plaintext) | http://silberarrows-mcp.netlify.app/mcp | HTTPS enforced | 301 | https://silberarrows-mcp.netlify.app/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. 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 →
explain_service ~31
Explain what a Mercedes-Benz Service A or Service B typically includes.
| Name | Type | Req | Description |
|---|---|---|---|
| service | string | yes | A or B |
No output schema declared.
No examples provided.
find_specialist ~28
Contact details for SilberArrows, a Mercedes-Benz service centre in Al Quoz, Dubai.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_next_service ~164
Estimate the next Mercedes-Benz service (alternating Service A/B, ASSYST-style) from the last service type, date and mileage. Default interval: 15,000 km or 12 months, whichever comes first.
| Name | Type | Req | Description |
|---|---|---|---|
| current_km | number | – | Current odometer reading in km (optional; improves the estimate) |
| interval_km | integer | – | Override distance interval (default 15000) |
| interval_months | integer | – | Override time interval (default 12) |
| last_service_date | string | yes | Date of the last service, YYYY-MM-DD |
| last_service_km | number | yes | Odometer reading at the last service, in km |
| last_service_type | string | yes | Type of the last service: A or B |
No output schema declared.
No examples provided.
warning_light_info ~67
General guidance on common Mercedes-Benz warning lights and messages. Omit 'light' to list those covered.
| Name | Type | Req | Description |
|---|---|---|---|
| light | string | – | e.g. 'check engine', 'flashing check engine', 'limp mode', 'ABS', 'ESP', 'battery', 'service due' |
No output schema declared.
No examples provided.
How do I install the Mercedes-Benz Service Reminder – SilberArrows MCP server?
Mercedes-Benz Service Reminder – SilberArrows is a hosted endpoint at https://silberarrows-mcp.netlify.app/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 · silberarrows-mcp.netlify.app
claude mcp add --transport http gentlegiant96202-mercedes-benz-service-reminder 'https://silberarrows-mcp.netlify.app/mcp'
What is the Mercedes-Benz Service Reminder – SilberArrows MCP server?
Mercedes-Benz Service Reminder – SilberArrows is an MCP server listed in the public MCP registry as io.github.gentlegiant96202/mercedes-benz-service-reminder. Mercedes-Benz Service A/B reminders, service explanations and warning-light guidance (Dubai). This page covers its hosted endpoint (https://silberarrows-mcp.netlify.app/mcp).
Is the Mercedes-Benz Service Reminder – SilberArrows MCP server safe to use?
Mercedes-Benz Service Reminder – SilberArrows scores 77 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 Mercedes-Benz Service Reminder – SilberArrows MCP server expose?
Mercedes-Benz Service Reminder – SilberArrows exposes 4 tools: get_next_service, explain_service, warning_light_info, find_specialist. Their descriptions and schemas cost roughly 290 tokens of context every time the server is loaded.
Does the Mercedes-Benz Service Reminder – SilberArrows MCP server require authentication?
No. We connected to Mercedes-Benz Service Reminder – SilberArrows without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Mercedes-Benz Service Reminder – SilberArrows MCP server still maintained?
Mercedes-Benz Service Reminder – SilberArrows is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.