RoastPilot
PYPI · COFFEE-ROASTER-MCP · SCANNED SEP 22
RoastPilot controls coffee roasting sessions through local stdio MCP tools and exports logs.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 2 of 50 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (Apache Software License) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability62
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 549 tokens (~36/item across 15 items; 15 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "drop_beans" implies "drop" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 16 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
How do I install the RoastPilot MCP server?
RoastPilot runs locally as a PyPI package, launched with uvx coffee-roaster-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · coffee-roaster-mcp
claude mcp add syamaner-coffee-roaster-mcp -- uvx coffee-roaster-mcp
{
"mcpServers": {
"syamaner-coffee-roaster-mcp": {
"command": "uvx",
"args": [
"coffee-roaster-mcp"
]
}
}
} {
"servers": {
"syamaner-coffee-roaster-mcp": {
"command": "uvx",
"args": [
"coffee-roaster-mcp"
]
}
}
} codex mcp add syamaner-coffee-roaster-mcp -- uvx coffee-roaster-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"syamaner-coffee-roaster-mcp": {
"type": "local",
"command": [
"uvx",
"coffee-roaster-mcp"
],
"enabled": true
}
}
} openclaw mcp add syamaner-coffee-roaster-mcp --command uvx --arg coffee-roaster-mcp
mcp_servers:
syamaner-coffee-roaster-mcp:
command: "uvx"
args: ["coffee-roaster-mcp"] {
"McpServers": {
"syamaner-coffee-roaster-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"coffee-roaster-mcp"
]
}
}
} assistant mcp add syamaner-coffee-roaster-mcp -t stdio -c uvx -a coffee-roaster-mcp
{
"mcpServers": {
"syamaner-coffee-roaster-mcp": {
"command": "uvx",
"args": [
"coffee-roaster-mcp"
]
}
}
} 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.
- 22 Sept 26 +1
- Stability: 0.97 → pass security
- 20 Sept 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.
- 19 Sept 26 −2
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Security disclosure: fail → unverified ▼ functional
- Schema quality: good → fair functional
- Stability: pass → 0.90 functional
- Package version: 0.2.0 → 0.2.1 functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 −3
- Stability: pass → 0.80 functional
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 22 Sept 2026 · Analysed pypi/coffee-roaster-mcp@0.2.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 50 packages
| Packages resolved | 50 |
|---|---|
| Stale | 2 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
drop_beans ~20
Drop beans through the driver and record the cooling transition.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| event | – | yes | – |
| event_count | integer | yes | – |
| phase | string | yes | – |
| session_id | string | yes | – |
No examples provided.
emergency_stop ~27
Call the configured driver safety method and record a fault event.
| Name | Type | Req | Description |
|---|---|---|---|
| reason | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| event | – | yes | – |
| event_count | integer | yes | – |
| phase | string | yes | – |
| session_id | string | yes | – |
No examples provided.
export_roast_log ~25
Write a snapshot export for one roast session.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| csv_path | string | yes | – |
| jsonl_path | string | yes | – |
| log_dir | string | yes | – |
| note | string | yes | – |
| ready | boolean | yes | – |
| session_id | string | yes | – |
| summary_path | string | yes | – |
No examples provided.
finalise_cold_characterisation_session ~33
Finalise one eligible cold-characterisation session without actuation.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| abort_reason | – | yes | – |
| admission_driver_evidence | – | yes | – |
| attempt_number | integer | yes | – |
| clean | boolean | yes | – |
| disconnect | – | yes | – |
| emergency_stop_ordering | string | yes | – |
| failures | array | yes | – |
| final_driver_evidence | – | yes | – |
| first_crack_runtime | – | yes | – |
| first_started_at_utc | – | yes | – |
| first_started_session_elapsed_seconds | – | yes | – |
| last_ended_at_utc | – | yes | – |
| last_ended_session_elapsed_seconds | – | yes | – |
| pre_disconnect_driver_evidence | – | yes | – |
| pre_finalisation_first_crack_status | – | yes | – |
| recording | – | yes | – |
| recovered_after_failure | boolean | yes | – |
| rejection_reason | – | yes | – |
| reservation_generation | – | yes | – |
| retained | boolean | yes | – |
| sampler | – | yes | – |
| session_active_after | boolean | yes | – |
| session_id | string | yes | – |
| session_phase_after | – | yes | – |
| session_purpose | – | yes | – |
| stages | array | yes | – |
| status | string | yes | – |
No examples provided.
get_roast_state ~24
Return the current authoritative roast session state.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | yes | – |
| ambient_status | – | yes | – |
| bean_ror_c_per_min | – | yes | – |
| bean_temp_delta_60s_c | – | yes | – |
| beans_added_at_utc | – | yes | – |
| beans_added_monotonic_seconds | – | yes | – |
| beans_dropped_at_utc | – | yes | – |
| beans_dropped_monotonic_seconds | – | yes | – |
| cooling_on | boolean | yes | – |
| cooling_started_at_utc | – | yes | – |
| cooling_started_monotonic_seconds | – | yes | – |
| cooling_stopped_at_utc | – | yes | – |
| cooling_stopped_monotonic_seconds | – | yes | – |
| created_at_utc | string | yes | – |
| development_percent | – | yes | – |
| development_time_seconds | – | yes | – |
| device_state | – | yes | – |
| elapsed_monotonic_seconds | number | yes | – |
| env_ror_c_per_min | – | yes | – |
| env_temp_delta_60s_c | – | yes | – |
| events | array | yes | – |
| fan_level_percent | integer | yes | – |
| faulted_at_utc | – | yes | – |
| faulted_monotonic_seconds | – | yes | – |
| first_crack_at_utc | – | yes | – |
| first_crack_monotonic_seconds | – | yes | – |
| first_crack_status | – | yes | – |
| heat_level_percent | integer | yes | – |
| log_dir | – | yes | – |
| phase | string | yes | – |
| roast_elapsed_seconds | – | yes | – |
| session_id | string | yes | – |
| session_purpose | string | – | – |
| stopped_at_utc | – | yes | – |
| t0_status | – | yes | – |
No examples provided.
get_runtime_config ~21
Return a bootstrap-safe summary of the active RoastPilot config.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_manual_override | boolean | yes | – |
| auto_t0_detection_enabled | boolean | yes | – |
| auto_t0_drop_threshold_c | number | yes | – |
| command_interval_seconds | number | yes | – |
| config_source | – | yes | – |
| first_crack_mode | string | yes | – |
| log_dir | string | yes | – |
| model_precision | string | yes | – |
| model_repo_id | string | yes | – |
| roaster_baudrate | integer | yes | – |
| roaster_driver | string | yes | – |
| roaster_port | – | yes | – |
| sample_interval_seconds | number | yes | – |
| temperature_unit | string | yes | – |
No examples provided.
get_server_info ~18
Return structured metadata about the running MCP server.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| available_bootstrap_tools | array | yes | – |
| bootstrap_safe | boolean | yes | – |
| current_phase | string | yes | – |
| first_crack_mode | string | yes | – |
| package_name | string | yes | – |
| product_name | string | yes | – |
| roaster_driver | string | yes | – |
| started_at_utc | string | yes | – |
| transport | string | yes | – |
| version | string | yes | – |
No examples provided.
mark_beans_added ~17
Record the authoritative beans-added event.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| event | – | yes | – |
| event_count | integer | yes | – |
| phase | string | yes | – |
| session_id | string | yes | – |
No examples provided.
mark_first_crack ~18
Record the authoritative first-crack event.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| event | – | yes | – |
| event_count | integer | yes | – |
| phase | string | yes | – |
| session_id | string | yes | – |
No examples provided.
set_fan ~26
Set fan through the configured driver boundary.
| Name | Type | Req | Description |
|---|---|---|---|
| fan_level_percent | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| cooling_on | boolean | yes | – |
| fan_level_percent | integer | yes | – |
| heat_level_percent | integer | yes | – |
| phase | string | yes | – |
| session_id | string | yes | – |
No examples provided.
set_heat ~25
Set heat through the configured driver boundary.
| Name | Type | Req | Description |
|---|---|---|---|
| heat_level_percent | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| cooling_on | boolean | yes | – |
| fan_level_percent | integer | yes | – |
| heat_level_percent | integer | yes | – |
| phase | string | yes | – |
| session_id | string | yes | – |
No examples provided.
set_recording_metadata ~197
Store bean origin + roast number for the next roast's audio recording. Call this BEFORE starting the roast. The recorder reads it when it creates the WAVs, naming them ``mic{N}-{origin}-roast{N}.wav`` and writing a ``{origin}-roast{N}-session.json`` so the captured audio plugs straight into the coffee-first-crack-detection annotation pipeline. This is purely additive metadata: it sends no hardware command. If never called, recording falls back to the session id as origin and roast number 0. Args: origin: Bean origin slug (e.g. ``"brazil"``). roast_num: 1-based roast number. Returns: The stored origin and roast number. Raises: ValueError: If origin is blank or roast_num is negative.
| Name | Type | Req | Description |
|---|---|---|---|
| origin | string | yes | – |
| roast_num | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| origin | string | yes | – |
| roast_num | integer | yes | – |
No examples provided.
start_cooling ~20
Start cooling through the driver as an explicit recovery command.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| event | – | yes | – |
| event_count | integer | yes | – |
| phase | string | yes | – |
| session_id | string | yes | – |
No examples provided.
start_roast_session ~28
Start one new authoritative roast session and prepare the driver.
| Name | Type | Req | Description |
|---|---|---|---|
| purpose | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| session | – | yes | – |
No examples provided.
stop_cooling ~17
Stop cooling through the configured driver boundary.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| event | – | yes | – |
| event_count | integer | yes | – |
| phase | string | yes | – |
| session_id | string | yes | – |
No examples provided.
What is the RoastPilot MCP server?
RoastPilot is an MCP server listed in the public MCP registry as io.github.syamaner/coffee-roaster-mcp. RoastPilot controls coffee roasting sessions through local stdio MCP tools and exports logs. This page covers its PyPI package (coffee-roaster-mcp).
Is the RoastPilot MCP server safe to use?
RoastPilot scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 2026. 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 RoastPilot MCP server expose?
RoastPilot exposes 15 tools: get_server_info, get_runtime_config, start_roast_session, finalise_cold_characterisation_session, get_roast_state, and 10 more. Their descriptions and schemas cost roughly 516 tokens of context every time the server is loaded.
Is the RoastPilot MCP server still maintained?
RoastPilot is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.