com.crisphive/mcp
NPM · @CRISPHIVE/MCP · 2 COMPONENTS · SCANNED SEP 20
Field operations on a deterministic solver — run jobs, crews & fleet from Claude or ChatGPT.
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 Security98
- 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
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 16 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 12228 tokens (~230/item across 53 items; 53 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
- All 7 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 53 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 com.crisphive/mcp server?
com.crisphive/mcp runs locally as an npm package, launched with npx -y @crisphive/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 · @crisphive/mcp
claude mcp add com-crisphive-mcp -- npx -y @crisphive/mcp
{
"mcpServers": {
"com-crisphive-mcp": {
"command": "npx",
"args": [
"-y",
"@crisphive/mcp"
]
}
}
} {
"servers": {
"com-crisphive-mcp": {
"command": "npx",
"args": [
"-y",
"@crisphive/mcp"
]
}
}
} codex mcp add com-crisphive-mcp -- npx -y @crisphive/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-crisphive-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@crisphive/mcp"
],
"enabled": true
}
}
} openclaw mcp add com-crisphive-mcp --command npx --arg -y --arg @crisphive/mcp
mcp_servers:
com-crisphive-mcp:
command: "npx"
args: ["-y", "@crisphive/mcp"] {
"McpServers": {
"com-crisphive-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@crisphive/mcp"
]
}
}
} assistant mcp add com-crisphive-mcp -t stdio -c npx -a -y @crisphive/mcp
{
"mcpServers": {
"com-crisphive-mcp": {
"command": "npx",
"args": [
"-y",
"@crisphive/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 +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.
- 18 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.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 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.
- 13 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.
- 11 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.
- 10 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 20 Sept 2026 · Analysed npm/@crisphive/mcp@2.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| 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 →
updateCustomer Update a customer ~572
Update a customer PARTIAL update — send only the fields you are changing; anything you OMIT is left exactly as stored (two-way CRM sync friendly: push one field from your system of record without re-sending the record). To CLEAR a field, send it as an empty string: uid, phone, email, notes, preferred_technician_id, service_area_id. `tier` and `status` are enums with no empty member, so an empty value there is ignored rather than stored. `full_name` cannot be set to empty. The nested `address` object is all-or-nothing: omit it to leave the stored address (and its coordinates) untouched; when present it REPLACES the whole block, and missing latitude/longitude are geocoded from the address. A customer must keep at least one contact channel — an update that would clear both phone and email is refused with PHONE_OR_EMAIL_REQUIRED.
| Name | Type | Req | Description |
|---|---|---|---|
| address | – | – | Postal address and coordinates. Omit the whole object to leave the stored address untouched; when present it REPLACES the address block. |
| string | – | Email address. Omit to leave unchanged, "" to clear. | |
| full_name | string | – | Customer's full name. Omit to leave unchanged; an empty or blank value is ignored (a customer cannot be left nameless). Max 255 chars. |
| id | string | yes | Customer ID (UUID) |
| notes | string | – | Free-form internal notes about the customer. Omit to leave unchanged, "" to clear; max 4000 chars. |
| phone | string | – | Phone number in E.164 international format (`+16135550188`); a bare national number is rejected with PHONE_INVALID — see createCustomerReq.Phone. Omit to leave unchanged, "" to clear. 10–20 chars. |
| preferred_technician_id | string | – | UUID of the technician this customer prefers. Omit to leave unchanged, "" to clear. Must belong to this business. |
| service_area_id | string | – | UUID of the service area for this customer. Omit to leave unchanged, "" to clear. Must belong to this business. |
| sms_opt_in | boolean | – | SMS consent, tri-state: omit/null = leave unchanged; true = grant (only when the customer explicitly consented — the original consent timestamp is preserved); false = revoke (opt-out, stops SMS immed… |
| status | string | – | Lifecycle status. Omit to leave unchanged; "" is ignored. |
| tier | string | – | Loyalty tier. Omit to leave unchanged; "" is ignored (an enum has no empty member). |
| uid | string | – | Your external reference for this customer. Omit to leave unchanged, "" to clear. Max 32 chars. |
No output schema declared.
No examples provided.
updateJobPriority Set job priority (scheduling staff) ~301
Set job priority (scheduling staff) Sets the P0–P3 priority on a non-archived, non-completed job (Owner / Administrator / Booking Coordinator). Allowed values: "p0" (emergency, interrupt-driven) | "p1" (top — displaced only by p0; may carry an sla_deadline arming auto-escalation) | "p2" (standard) | "p3" (deferrable, first displacement victim). sla_deadline is only valid with p1 and must be in the future (business-local naive datetime); moving away from p1 disarms the SLA clock. Accepts UUID or short_code in :id.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Job request ID or short_code |
| note | string | – | Optional justification (max 500 chars) — recorded on the activity trail and the priority_changed webhook. Recommended when de-escalating an SLA-escalated job (audit provenance). |
| priority | string | yes | New P0–P3 priority level. p0=emergency, p1=top, p2=standard, p3=deferrable. |
| sla_deadline | string | – | SLA deadline (business-local naive datetime) — only with priority=p1; (re)arms the auto-escalation clock. Omitted on a p1 change keeps any stored deadline; changing away from p1 disarms SLA entirely. |
No output schema declared.
No examples provided.
updateTechnician Update a technician ~378
Update a technician Updates mutable technician profile fields. `start_location_type=office` re-snapshots the current business address + coordinates (body `address`/`start_location_lat`/`start_location_long` ignored; requires business coordinates, else 400 BUSINESS_LOCATION_MISSING). `start_location_type=home` (or empty) uses the address + coordinates from the body.
| Name | Type | Req | Description |
|---|---|---|---|
| address | – | – | Home address (the day-start point when start_location_type=home). |
| assignment_tier | string | – | Crew tier: lead / buddy / float (float = excluded from auto crew-assign). |
| business_group_id | string | yes | Role group. Discover IDs via GET /permission/groups. |
| string | – | Email address. At least one of phone/email is required. | |
| full_name | string | yes | The person's full display name. Required; max 255 chars. |
| id | string | yes | Technician ID |
| job_title | string | – | Display title. |
| join_date | string | – | First working day (YYYY-MM-DD). |
| phone | string | – | Phone number in E.164 international format (`+16135550188`); a bare national number is rejected with PHONE_INVALID — see AddTechnicianReq.Phone. At least one of phone/email is required — enforced in… |
| start_location_lat | number | – | Explicit day-start latitude in decimal degrees (-90..90); when set it wins over the address geocode. |
| start_location_long | number | – | Explicit day-start longitude in decimal degrees (-180..180); when set it wins over the address geocode. |
| start_location_type | string | – | Day-start point: home or office; explicit coordinates win when set. |
No output schema declared.
No examples provided.
What is the com.crisphive/mcp server?
com.crisphive/mcp is listed in the public MCP registry as com.crisphive/mcp. Field operations on a deterministic solver, run jobs, crews & fleet from Claude or ChatGPT. This page covers its npm package (@crisphive/mcp).
Is the com.crisphive/mcp server safe to use?
com.crisphive/mcp scores 81 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. 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 com.crisphive/mcp server expose?
com.crisphive/mcp exposes 53 tools: commitEmergencyReschedule, commitJobRequestMove, confirmJobRequest, createCustomer, createJobRequest, and 48 more. Their descriptions and schemas cost roughly 12,228 tokens of context every time the server is loaded.
Is the com.crisphive/mcp server still maintained?
com.crisphive/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 com.crisphive/mcp server under?
com.crisphive/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.