# ServiceSchedule (remote · service-schedule.magicteams.ai)

Car maintenance due dates, cost estimates and seasonal checklists. Free.

- Trust score: 79/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `service-schedule.magicteams.ai`: 79/100 (this document), [markdown](https://verifymcp.io/servers/everyai-com-service-schedule/service-schedule.md), [page](https://verifymcp.io/servers/everyai-com-service-schedule/service-schedule)

## Channel facts

- Endpoint: `https://service-schedule.magicteams.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-23.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 63/100
  - Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http everyai-com-service-schedule 'https://service-schedule.magicteams.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "everyai-com-service-schedule": {
      "url": "https://service-schedule.magicteams.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "everyai-com-service-schedule": {
      "type": "http",
      "url": "https://service-schedule.magicteams.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.everyai-com-service-schedule]
url = "https://service-schedule.magicteams.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "everyai-com-service-schedule": {
      "type": "remote",
      "url": "https://service-schedule.magicteams.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add everyai-com-service-schedule --url 'https://service-schedule.magicteams.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  everyai-com-service-schedule:
    url: "https://service-schedule.magicteams.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "everyai-com-service-schedule": {
      "Transport": "http",
      "Url": "https://service-schedule.magicteams.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add everyai-com-service-schedule -t streamable-http -u 'https://service-schedule.magicteams.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "everyai-com-service-schedule": {
      "type": "http",
      "url": "https://service-schedule.magicteams.ai/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-21 (score 79, +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.

### 2026-10-19 (score 78, +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.

### 2026-10-17 (score 77, +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.

### 2026-10-15 (score 76, +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.

### 2026-10-13 (score 75, +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.

### 2026-10-12 (score 74, +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.

### 2026-10-10 (score 73, +3)

- [security] 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
- [functional regression] Schema quality: pass → fail
- [functional improvement] Stability: unverified → 0.20
- [functional] First check of Tool coverage: 100
- [functional] Schema quality: good → excellent
- [cosmetic] “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”

### 2026-10-04 (score 70)

First indexed and scored.

## MCP tools (4)

### `due_services` (~245 tokens)

Due services

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).

Input parameters:

- `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, required): 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'

Output parameters:

- `next_service` (object): The most urgent service
- `note` (string): Summary counts, baseline assumptions and caveats
- `odometer_input` (object): Odometer value and unit as supplied
- `odometer_km` (number): Current odometer converted to km (1 decimal)
- `services` (array): Status of every tracked maintenance service

### `service_cost_estimate` (~134 tokens)

Service cost estimate

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).

Input parameters:

- `services` (array, required): 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)

Output parameters:

- `items` (array): Price range per service in USD
- `note` (string): Summary of what was priced
- `source_note` (string): Source and estimate-not-quote caveat
- `tier` (string): Shop tier used for pricing
- `total_high` (number): Sum of high prices, USD
- `total_low` (number): Sum of low prices, USD

### `service_timeline` (~179 tokens)

Service timeline

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).

Input parameters:

- `km_per_month` (number, required): 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, required): 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'

Output parameters:

- `months` (array): Twelve monthly entries, month 1 = next month
- `note` (string): Assumptions behind the projection

### `seasonal_checklist` (~107 tokens)

Seasonal checklist

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).

Input parameters:

- `climate` (string): Local climate: 'hot', 'cold' or 'mixed' (default)
- `season` (string, required): Season to prepare for

Output parameters:

- `checklist` (array): Checks grouped by area
- `climate` (string): Climate the checklist is tuned for
- `note` (string): Item count and preventive-only caveat
- `season` (string): Season the checklist covers

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/everyai-com-service-schedule/service-schedule#diagnostics

## Score history

- 2026-10-23: 79
- 2026-10-22: 79
- 2026-10-21: 79
- 2026-10-20: 78
- 2026-10-19: 78
- 2026-10-18: 77
- 2026-10-17: 77
- 2026-10-16: 76
- 2026-10-15: 76
- 2026-10-14: 75
- 2026-10-13: 75
- 2026-10-12: 74
- 2026-10-10: 73
- 2026-10-04: 70

## Common questions

### 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.

## Links

- Remote endpoint: https://service-schedule.magicteams.ai/mcp
- Repository: https://github.com/everyai-com/sahadeva
- Changelog RSS feed: https://verifymcp.io/servers/everyai-com-service-schedule/service-schedule.xml
- Changelog JSON feed: https://verifymcp.io/servers/everyai-com-service-schedule/service-schedule.json
- HTML version of this page: https://verifymcp.io/servers/everyai-com-service-schedule/service-schedule