io.github.chrischall/simplisafe-mcp
NPM · SIMPLISAFE-MCP · SCANNED SEP 20
Check SimpliSafe system state and sensors, review events, arm/disarm, and control smart locks
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
- No install/post-install scripts declared.Pass
- 0 of 5 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to chrischall/simplisafe-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1174 tokens (~117/item across 10 items; 10 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 Management90
- Stability observed for 27 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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
How do I install the io.github.chrischall/simplisafe-mcp server?
io.github.chrischall/simplisafe-mcp runs locally as an npm package, launched with npx -y simplisafe-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · simplisafe-mcp
claude mcp add chrischall-simplisafe-mcp -- npx -y simplisafe-mcp
{
"mcpServers": {
"chrischall-simplisafe-mcp": {
"command": "npx",
"args": [
"-y",
"simplisafe-mcp"
]
}
}
} {
"servers": {
"chrischall-simplisafe-mcp": {
"command": "npx",
"args": [
"-y",
"simplisafe-mcp"
]
}
}
} codex mcp add chrischall-simplisafe-mcp -- npx -y simplisafe-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"chrischall-simplisafe-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"simplisafe-mcp"
],
"enabled": true
}
}
} openclaw mcp add chrischall-simplisafe-mcp --command npx --arg -y --arg simplisafe-mcp
mcp_servers:
chrischall-simplisafe-mcp:
command: "npx"
args: ["-y", "simplisafe-mcp"] {
"McpServers": {
"chrischall-simplisafe-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"simplisafe-mcp"
]
}
}
} assistant mcp add chrischall-simplisafe-mcp -t stdio -c npx -a -y simplisafe-mcp
{
"mcpServers": {
"chrischall-simplisafe-mcp": {
"command": "npx",
"args": [
"-y",
"simplisafe-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.
- 20 Sept 26 0
- Stability: 0.87 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Package version: 1.0.0 → 1.1.0 functional
- 19 Sept 26 +2
- Stability: 0.83 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Dependency health: 0.86 → 1.00 ▲ functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Package version: 0.2.2 → 1.0.0 functional
- 17 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 16 Sept 26 −3
- Stability: pass → 0.77 functional
- 15 Sept 26 +1
- Malware scan: unverified → pass ▲ security
- Stability: 0.97 → pass security
- Package version: 0.2.1 → 0.2.2 functional
- 13 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.
- 11 Sept 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.
- 10 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.2.0 → 0.2.1 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 20 Sept 2026 · Analysed npm/simplisafe-mcp@1.1.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | chrischall/simplisafe-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/chrischall/simplisafe-mcp/.github/workflows/release-please.yml@refs/heads/main |
| Rekor log index | 2893922593 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:10429a64878cea7795871ba745fa0cc02c3db1dfa14a4e17b095f67b02f9db1b562eb7157a86022b75ffc1e17e3b698c6f66d00687f2cd43b500f4340 |
Background: How many MCP packages publish verified provenance →
Dependencies 5 packages
| Packages resolved | 5 |
|---|---|
| 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 →
simplisafe_get_events ~149
Get recent events recorded by the base station — arm/disarm, sensor opens, lock and unlock, alarms, errors — newest first. Each event carries an ISO timestamp alongside the raw epoch seconds.
| Name | Type | Req | Description |
|---|---|---|---|
| event_type | string | – | Only return events with this eventType, e.g. "activity" or "alarm". |
| from_timestamp | integer | – | Only events at or after this Unix timestamp (seconds). |
| num_events | integer | – | How many events to return, 1-50 (SimpliSafe rejects more than 50). Defaults to 50. |
| sid | integer | – | System id. Optional when the account has exactly one system; required when it has several. |
No output schema declared.
No examples provided.
simplisafe_get_pins ~113
Read the system's user PINs (master, duress and named users). CONFIRM-GATED: these are the live alarm codes and are returned in cleartext, so calling this puts them into the conversation. Without confirm: true it returns a warning and fetches nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | Must be true to proceed. Without this, the tool returns a preview. |
| sid | integer | – | System id. Optional when the account has exactly one system; required when it has several. |
No output schema declared.
No examples provided.
simplisafe_get_settings ~98
Get base-station settings for a system: entry/exit delays, alarm volume and duration, door chime, voice prompts, plus base-station health (wifi/cellular signal, wall power, backup battery, RF jamming). Does not include PINs — use simplisafe_get_pins for those.
| Name | Type | Req | Description |
|---|---|---|---|
| sid | integer | – | System id. Optional when the account has exactly one system; required when it has several. |
No output schema declared.
No examples provided.
simplisafe_get_system ~71
Get the current state of one SimpliSafe system: alarm state, whether it is alarming, base-station connectivity, power/battery status and any pending base-station messages.
| Name | Type | Req | Description |
|---|---|---|---|
| sid | integer | – | System id. Optional when the account has exactly one system; required when it has several. |
No output schema declared.
No examples provided.
simplisafe_healthcheck ~57
Check that the server can authenticate to SimpliSafe and reach the API. Reports whether the refresh token is configured and working, the resolved user id, and how many active systems the account has. Start here when other tools fail.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
simplisafe_list_locks ~143
List the smart locks on a system with their current state (locked / unlocked / jammed), lock and keypad battery status, and keypad connectivity. Returns the `serial` that simplisafe_set_lock_state takes. Polls the base station fresh by default, because a stale answer to "is my door locked?" is worse than a slow one.
| Name | Type | Req | Description |
|---|---|---|---|
| force_update | boolean | – | Re-poll the base station before answering. Defaults to TRUE for locks — set false to accept a possibly-stale cached reading in exchange for speed. |
| sid | integer | – | System id. Optional when the account has exactly one system; required when it has several. |
No output schema declared.
No examples provided.
simplisafe_list_sensors ~171
List the sensors and devices paired to a system — entry sensors, motion, glass break, smoke/CO, keypads, sirens and locks — with battery, offline and triggered status. Filter by type with `type_name` (e.g. "entry", "motion_v2", "lock").
| Name | Type | Req | Description |
|---|---|---|---|
| force_update | boolean | – | Ask the base station to re-poll its devices first (slower). Defaults to false. |
| problems_only | boolean | – | Only return devices that are offline, low battery, or triggered. |
| sid | integer | – | System id. Optional when the account has exactly one system; required when it has several. |
| type_name | string | – | Only return devices of this type name, e.g. "entry", "lock", "smoke". |
No output schema declared.
No examples provided.
simplisafe_list_systems ~52
List the SimpliSafe systems on this account with their current alarm state (off/home/away), alarming status, connectivity and power status. Start here to get the `sid` other tools take.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
simplisafe_set_alarm_state ~171
Arm or disarm the alarm system: "off" (disarm), "home" (perimeter only) or "away" (all sensors). CONFIRM-GATED — without confirm: true nothing is sent and you get a dry-run preview. This physically changes a security system: disarming leaves the house unmonitored, and arming can trigger a siren and a monitoring-center dispatch. After executing, the new state is verified by re-reading the system.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | Must be true to proceed. Without this, the tool returns a preview. |
| sid | integer | – | System id. Optional when the account has exactly one system; required when it has several. |
| state | string | yes | Target state: off (disarm), home, or away. |
No output schema declared.
No examples provided.
simplisafe_set_lock_state ~149
Lock or unlock a SimpliSafe smart lock. CONFIRM-GATED — without confirm: true nothing is sent and you get a dry-run preview. Unlocking physically opens a door lock, so it is gated even though it is technically reversible. After executing, the result is verified by re-reading the lock state.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | Must be true to proceed. Without this, the tool returns a preview. |
| serial | string | yes | Lock serial, from simplisafe_list_locks. |
| sid | integer | – | System id. Optional when the account has exactly one system; required when it has several. |
| state | string | yes | Target: lock or unlock. |
No output schema declared.
No examples provided.
What is the io.github.chrischall/simplisafe-mcp server?
io.github.chrischall/simplisafe-mcp is listed in the public MCP registry as io.github.chrischall/simplisafe-mcp. Check SimpliSafe system state and sensors, review events, arm/disarm, and control smart locks. This page covers its npm package (simplisafe-mcp).
Is the io.github.chrischall/simplisafe-mcp server safe to use?
io.github.chrischall/simplisafe-mcp scores 95 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 io.github.chrischall/simplisafe-mcp server expose?
io.github.chrischall/simplisafe-mcp exposes 10 tools: simplisafe_list_systems, simplisafe_get_system, simplisafe_get_settings, simplisafe_get_pins, simplisafe_list_sensors, and 5 more. Their descriptions and schemas cost roughly 1,174 tokens of context every time the server is loaded.
Is the io.github.chrischall/simplisafe-mcp server still maintained?
io.github.chrischall/simplisafe-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.chrischall/simplisafe-mcp server under?
io.github.chrischall/simplisafe-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.