Rush SR Maintenance is a remote MCP server that gives an AI agent 3 tools, among them diagnose_symptom, lookup_procedure, maintenance_schedule. It answers at https://maintenance.mcp.rush.sr/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 1 October 2026; the last check, on 16 November 2026, succeeded.
Rush SR owner's manual: diagnose a symptom, find service intervals and repair procedures.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
diagnose_symptom | 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 buy Inputs: symptom, context |
lookup_procedure | 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. Inputs: task |
maintenance_schedule | 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, weeken Inputs: component |
Every block below points at https://maintenance.mcp.rush.sr/mcp. Pick your client and copy.
claude mcp add --transport http rush-sr-maintenance https://maintenance.mcp.rush.sr/mcp
{
"mcpServers": {
"rush-sr-maintenance": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://maintenance.mcp.rush.sr/mcp"]
}
}
}{
"mcpServers": {
"rush-sr-maintenance": {
"url": "https://maintenance.mcp.rush.sr/mcp"
}
}
}{
"servers": {
"rush-sr-maintenance": {
"type": "http",
"url": "https://maintenance.mcp.rush.sr/mcp"
}
}
}{
"context_servers": {
"rush-sr-maintenance": {
"url": "https://maintenance.mcp.rush.sr/mcp"
}
}
}{
"mcpServers": {
"rush-sr-maintenance": {
"serverUrl": "https://maintenance.mcp.rush.sr/mcp"
}
}
}{
"mcpServers": {
"rush-sr-maintenance": {
"url": "https://maintenance.mcp.rush.sr/mcp"
}
}
}name: Rush SR Maintenance
version: 0.0.1
schema: v1
mcpServers:
- name: Rush SR Maintenance
type: streamable-http
url: https://maintenance.mcp.rush.sr/mcp{
"mcpServers": {
"rush-sr-maintenance": {
"httpUrl": "https://maintenance.mcp.rush.sr/mcp"
}
}
}{
"mcpServers": {
"rush-sr-maintenance": {
"type": "http",
"url": "https://maintenance.mcp.rush.sr/mcp"
}
}
}{
"mcpServers": {
"rush-sr-maintenance": {
"url": "https://maintenance.mcp.rush.sr/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmaintenance.mcp.rush.sr%2Fmcp&type=streamable_http&id=rush-sr-maintenance&name=Rush%20SR%20Maintenance
It answered our last check on 16 November 2026 in 697 ms. Over 4 checks since 1 October 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by rush.sr and served from maintenance.mcp.rush.sr, the vendor's own domain: https://maintenance.mcp.rush.sr/mcp.
3, as returned by the server's own tools/list on 19 November 2026: diagnose_symptom, lookup_procedure, maintenance_schedule.
It answered our last check on 16 November 2026 in 697 ms. Over 4 checks since 1 October 2026 it answered 4.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://maintenance.mcp.rush.sr/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: sr.rush. Endpoint host: maintenance.mcp.rush.sr. ARD identifier: urn:air:sr.rush:mcp:maintenance.
First indexed 1 October 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.