io.github.dgtalquantumleap-ai/ebenova-fieldops
NPM · @EBENOVA/FIELDOPS-MCP · SCANNED SEP 20
WhatsApp booking, staff coordination, and invoice recovery for services.
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
- 35 of 111 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- 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 159 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 403 tokens (~80/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_payment_link" implies "send" 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 5 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 io.github.dgtalquantumleap-ai/ebenova-fieldops MCP server?
io.github.dgtalquantumleap-ai/ebenova-fieldops runs locally as an npm package, launched with npx -y @ebenova/fieldops-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 · @ebenova/fieldops-mcp
claude mcp add dgtalquantumleap-ai-ebenova-fieldops -- npx -y @ebenova/fieldops-mcp
{
"mcpServers": {
"dgtalquantumleap-ai-ebenova-fieldops": {
"command": "npx",
"args": [
"-y",
"@ebenova/fieldops-mcp"
]
}
}
} {
"servers": {
"dgtalquantumleap-ai-ebenova-fieldops": {
"command": "npx",
"args": [
"-y",
"@ebenova/fieldops-mcp"
]
}
}
} codex mcp add dgtalquantumleap-ai-ebenova-fieldops -- npx -y @ebenova/fieldops-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dgtalquantumleap-ai-ebenova-fieldops": {
"type": "local",
"command": [
"npx",
"-y",
"@ebenova/fieldops-mcp"
],
"enabled": true
}
}
} openclaw mcp add dgtalquantumleap-ai-ebenova-fieldops --command npx --arg -y --arg @ebenova/fieldops-mcp
mcp_servers:
dgtalquantumleap-ai-ebenova-fieldops:
command: "npx"
args: ["-y", "@ebenova/fieldops-mcp"] {
"McpServers": {
"dgtalquantumleap-ai-ebenova-fieldops": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@ebenova/fieldops-mcp"
]
}
}
} assistant mcp add dgtalquantumleap-ai-ebenova-fieldops -t stdio -c npx -a -y @ebenova/fieldops-mcp
{
"mcpServers": {
"dgtalquantumleap-ai-ebenova-fieldops": {
"command": "npx",
"args": [
"-y",
"@ebenova/fieldops-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.
- 19 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.
- 17 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.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 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.
- 12 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.
- 10 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.
- 9 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/@ebenova/fieldops-mcp@1.0.2
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 111 packages
| Packages resolved | 111 |
|---|---|
| Stale | 35 |
| 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 →
book_service ~136
Book a cleaning or service appointment. Creates the job, assigns staff, sends WhatsApp confirmation with payment link.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Full service address |
| business_id | number | – | Business ID |
| customer_name | string | yes | Full name of the customer |
| customer_phone | string | yes | Customer WhatsApp number in E.164 format e.g. +14031234567 |
| date | string | yes | Date in YYYY-MM-DD format |
| service | string | yes | Service name e.g. "Deep Clean", "Standard Clean" |
| time | string | yes | Time in HH:MM 24h format |
No output schema declared.
No examples provided.
check_availability ~56
Check available booking slots for a given date. Returns booked and available time slots.
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | number | – | Business ID (optional — uses default if not provided) |
| date | string | yes | Date in YYYY-MM-DD format |
No output schema declared.
No examples provided.
recover_invoice ~79
Send an escalating WhatsApp payment recovery message for an unpaid invoice. Step 1=polite reminder, 2=firm follow-up, 3=final notice.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice_id | number | yes | Invoice ID |
| step | number | – | Escalation step: 1=polite, 2=firm, 3=final |
No output schema declared.
No examples provided.
send_payment_link ~86
Generate and send a payment link to a customer via WhatsApp. Supports CAD (Polar/Stripe) and NGN (OxaPay).
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Amount to charge |
| currency | string | – | Currency |
| customer_phone | string | yes | Customer WhatsApp number in E.164 format |
| job_id | number | yes | Job ID to generate payment for |
No output schema declared.
No examples provided.
send_staff_briefing ~46
Send a WhatsApp job briefing to the assigned staff member with service details, customer info, and location.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | number | yes | Job ID to send briefing for |
No output schema declared.
No examples provided.
What is the io.github.dgtalquantumleap-ai/ebenova-fieldops MCP server?
io.github.dgtalquantumleap-ai/ebenova-fieldops is an MCP server listed in the public MCP registry as io.github.dgtalquantumleap-ai/ebenova-fieldops. WhatsApp booking, staff coordination, and invoice recovery for services. This page covers its npm package (@ebenova/fieldops-mcp).
Is the io.github.dgtalquantumleap-ai/ebenova-fieldops MCP server safe to use?
io.github.dgtalquantumleap-ai/ebenova-fieldops scores 77 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 io.github.dgtalquantumleap-ai/ebenova-fieldops MCP server expose?
io.github.dgtalquantumleap-ai/ebenova-fieldops exposes 5 tools: check_availability, book_service, send_payment_link, recover_invoice, send_staff_briefing. Their descriptions and schemas cost roughly 403 tokens of context every time the server is loaded.
Is the io.github.dgtalquantumleap-ai/ebenova-fieldops MCP server still maintained?
io.github.dgtalquantumleap-ai/ebenova-fieldops 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.dgtalquantumleap-ai/ebenova-fieldops MCP server under?
io.github.dgtalquantumleap-ai/ebenova-fieldops declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.