Rush SR Maintenance
REMOTE · MAINTENANCE.MCP.RUSH.SR
Rush SR owner's manual: diagnose a symptom, find service intervals and repair procedures.
Available components
Last scanned (16 minutes ago)
Scores higher than 85% of remote servers
Reachable. Last reached 5 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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 (good).Pass
- Tool/resource definitions use about 261 tokens (~87/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% 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
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
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.
- 31 Oct 26 +1
- Stability: 0.97 → pass security
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 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 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.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 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 5 Nov 2026 · Probed https://maintenance.mcp.rush.sr/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=laps.mcp.rush.sr | CN=Amazon RSA 2048 M01,O=Amazon,C=US | 1 Oct 2026 | 16 Apr 2027 | RSA 2048 | SHA256-RSA | 2123f9c3f60b9d16802cdbe8a7d0088 |
| SANs: laps.mcp.rush.sr, maintenance.mcp.rush.sr | ||||||
| CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 77312380b9d6688a33b1ed9bf9ccda68e0e0f |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of maintenance.mcp.rush.sr. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| sr. | present | 46104 | 13 | Verified |
| rush.sr. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://maintenance.mcp.rush.sr/mcp | Verified | 200 | |
| http (plaintext) | http://maintenance.mcp.rush.sr/mcp | HTTPS enforced | 301 | https://maintenance.mcp.rush.sr/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 →
diagnose_symptom Diagnose a Rush SR symptom ~79
Use this when you need to understand why your Rush SR has a symptom, such as why won't my Rush SR start. Do not use for a service interval or a step-by-step repair procedure. Covers the Rush SR only: do not use for other vehicles or for buying advice.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | – |
| symptom | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | – |
| rush | object | yes | – |
| stale | boolean | yes | – |
No examples provided.
lookup_procedure Look up a Rush SR procedure ~69
Use this when you need steps for a task, such as how do I bleed the brakes on my Rush SR. Do not use for a symptom diagnosis or a service interval lookup. Covers the Rush SR only: do not use for other vehicles or for buying advice.
| Name | Type | Req | Description |
|---|---|---|---|
| task | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | – |
| rush | object | yes | – |
| stale | boolean | yes | – |
No examples provided.
maintenance_schedule Rush SR maintenance schedule ~113
Use this when checking a Rush SR service interval or maintenance schedule for a component, such as how often to change brake fluid or when the chain needs service. Each result says which service interval it belongs to (every session, weekend, month, year, or 150+ hours), so pick the one that matches the car's hours or sessions. Do not use for troubleshooting a symptom or a repair procedure. Covers the Rush SR only: do not use for other vehicles or for buying advice.
| Name | Type | Req | Description |
|---|---|---|---|
| component | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | – |
| rush | object | yes | – |
| stale | boolean | yes | – |
No examples provided.
How do I install the Rush SR Maintenance MCP server?
Rush SR Maintenance is a hosted endpoint at https://maintenance.mcp.rush.sr/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 · maintenance.mcp.rush.sr
claude mcp add --transport http sr-rush-maintenance 'https://maintenance.mcp.rush.sr/mcp'
What is the Rush SR Maintenance MCP server?
Rush SR Maintenance is an MCP server listed in the public MCP registry as sr.rush/maintenance. Rush SR owner's manual: diagnose a symptom, find service intervals and repair procedures. This page covers its hosted endpoint (https://maintenance.mcp.rush.sr/mcp).
Is the Rush SR Maintenance MCP server safe to use?
Rush SR Maintenance scores 82 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 Rush SR Maintenance MCP server expose?
Rush SR Maintenance exposes 3 tools: diagnose_symptom, maintenance_schedule, lookup_procedure. Their descriptions and schemas cost roughly 261 tokens of context every time the server is loaded.
Does the Rush SR Maintenance MCP server require authentication?
No. We connected to Rush SR Maintenance without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Rush SR Maintenance MCP server still maintained?
Rush SR Maintenance 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.