ServiceSchedule
REMOTE · SERVICE-SCHEDULE.MAGICTEAMS.AI
Car maintenance due dates, cost estimates and seasonal checklists. Free.
Available components
Last scanned (16 hours ago)
Scores higher than 82% of remote servers
Reachable. Last reached 23 Oct 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 Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 704 tokens (~176/item across 4 items; 4 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 Management63
- Stability observed for 19 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
- 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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.
- 21 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.
- 19 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.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 15 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.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 27. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +3
- Tool “due_services” rewrote its description, which is the text the model reads security
- Tool “seasonal_checklist” rewrote its description, which is the text the model reads security
- Tool “service_cost_estimate” rewrote its description, which is the text the model reads security
- Tool “service_timeline” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Stability: unverified → 0.20 ▲ functional
- First check of Tool coverage: 100 functional
- Schema quality: good → excellent functional
- “due_services” reworded the description of “km_per_month” cosmetic
- “due_services” reworded the description of “last_service” cosmetic
- “due_services” reworded the description of “months_since_last_oil” cosmetic
- “due_services” reworded the description of “odometer” cosmetic
- “due_services” reworded the description of “unit” cosmetic
- “seasonal_checklist” reworded the description of “climate” cosmetic
- “seasonal_checklist” reworded the description of “season” cosmetic
- “service_cost_estimate” reworded the description of “services” cosmetic
- “service_cost_estimate” reworded the description of “tier” cosmetic
- “service_timeline” reworded the description of “km_per_month” cosmetic
- “service_timeline” reworded the description of “months_since_last_oil” cosmetic
- “service_timeline” reworded the description of “odometer” cosmetic
- “service_timeline” reworded the description of “unit” cosmetic
- 4 Oct 26 70
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 23 Oct 2026 · Probed https://service-schedule.magicteams.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=magicteams.ai | CN=WE1,O=Google Trust Services,C=US | 4 Oct 2026 | 2 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | f8e62871f04072900ed9cff7d8888ccb |
| SANs: magicteams.ai, service-schedule.magicteams.ai, *.service-schedule.magicteams.ai | ||||||
| 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 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of service-schedule.magicteams.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| magicteams.ai. | 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://service-schedule.magicteams.ai/mcp | Verified | 200 | |
| http (plaintext) | http://service-schedule.magicteams.ai/mcp | HTTPS enforced | 301 | https://service-schedule.magicteams.ai/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 →
due_services Due services ~245
Work out which car maintenance services (oil, tires, brakes, filters, coolant, plugs, transmission, battery) are due, due soon or ok from the current odometer and optional service history, and name the next one. Use to check what a car needs now. Do NOT use for prices (use service_cost_estimate) or a 12-month plan (use service_timeline).
| Name | Type | Req | Description |
|---|---|---|---|
| km_per_month | number | – | Average distance driven per month in km (always km, 100-10000); adds a 'next due in about N months' hint |
| last_service | array | – | Optional per-service history, one entry per service id; items without an entry assume last service at odometer 0 |
| months_since_last_oil | number | – | Months since the last oil change; used as the time baseline for every item without its own history, default 0 |
| odometer | number | yes | Current odometer reading, non-negative, in the unit given by unit, e.g. 48000 |
| unit | string | – | Unit of odometer and last_service odometer values: 'km' (default) or 'mi' |
| Name | Type | Req | Description |
|---|---|---|---|
| next_service | object | yes | The most urgent service |
| note | string | yes | Summary counts, baseline assumptions and caveats |
| odometer_input | object | yes | Odometer value and unit as supplied |
| odometer_km | number | yes | Current odometer converted to km (1 decimal) |
| services | array | yes | Status of every tracked maintenance service |
No examples provided.
seasonal_checklist Seasonal checklist ~107
Generate a preventive car checklist for spring, summer, fall or winter, grouped by area (tires, battery, fluids, wipers and more) and tuned for a hot, cold or mixed climate. Use when getting a car ready for the season ahead. Do NOT use for mileage-based maintenance status (use due_services).
| Name | Type | Req | Description |
|---|---|---|---|
| climate | string | – | Local climate: 'hot', 'cold' or 'mixed' (default) |
| season | string | yes | Season to prepare for |
| Name | Type | Req | Description |
|---|---|---|---|
| checklist | array | yes | Checks grouped by area |
| climate | string | yes | Climate the checklist is tuned for |
| note | string | yes | Item count and preventive-only caveat |
| season | string | yes | Season the checklist covers |
No examples provided.
service_cost_estimate Service cost estimate ~134
Estimate typical US parts-and-labor price ranges (USD) for a list of car maintenance services at an economy, mid or luxury shop, with low and high totals. Use when budgeting for known services. An estimate, not a quote. Do NOT use to find which services are due (use due_services).
| Name | Type | Req | Description |
|---|---|---|---|
| services | array | yes | Service ids to price (duplicates ignored), e.g. ["oil_change","brake_inspection"] |
| tier | string | – | Shop tier: 'economy' (x0.85), 'mid' (default) or 'luxury' (x1.6) |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | Price range per service in USD |
| note | string | yes | Summary of what was priced |
| source_note | string | yes | Source and estimate-not-quote caveat |
| tier | string | yes | Shop tier used for pricing |
| total_high | number | yes | Sum of high prices, USD |
| total_low | number | yes | Sum of low prices, USD |
No examples provided.
service_timeline Service timeline ~179
Project the next 12 months of driving and list which maintenance services fall due in each month, from the odometer and monthly distance. Use when planning maintenance over the coming year. Do NOT use for what is due right now (use due_services) or prices (use service_cost_estimate).
| Name | Type | Req | Description |
|---|---|---|---|
| km_per_month | number | yes | Average distance driven per month in km (always km, 100-10000), e.g. 1200 |
| months_since_last_oil | number | – | Months since the last oil change; time baseline for every service, default 0 |
| odometer | number | yes | Current odometer reading, non-negative, in the unit given by unit, e.g. 48000 |
| unit | string | – | Unit of the odometer value: 'km' (default) or 'mi' |
| Name | Type | Req | Description |
|---|---|---|---|
| months | array | yes | Twelve monthly entries, month 1 = next month |
| note | string | yes | Assumptions behind the projection |
No examples provided.
How do I install the ServiceSchedule MCP server?
ServiceSchedule is a hosted endpoint at https://service-schedule.magicteams.ai/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 · service-schedule.magicteams.ai
claude mcp add --transport http everyai-com-service-schedule 'https://service-schedule.magicteams.ai/mcp'
What is the ServiceSchedule MCP server?
ServiceSchedule is an MCP server listed in the public MCP registry as io.github.everyai-com/service-schedule. Car maintenance due dates, cost estimates and seasonal checklists. Free. This page covers its hosted endpoint (https://service-schedule.magicteams.ai/mcp).
Is the ServiceSchedule MCP server safe to use?
ServiceSchedule scores 79 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 ServiceSchedule MCP server expose?
ServiceSchedule exposes 4 tools: due_services, service_cost_estimate, service_timeline, seasonal_checklist. Their descriptions and schemas cost roughly 665 tokens of context every time the server is loaded.
Does the ServiceSchedule MCP server require authentication?
No. We connected to ServiceSchedule without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ServiceSchedule MCP server still maintained?
ServiceSchedule is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.