Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.dgtalquantumleap-ai/ebenova-fieldops

NPM · @EBENOVA/FIELDOPS-MCP

WhatsApp booking, staff coordination, and invoice recovery for services.

0 this week 72 Trust /100

Last scanned (22 hours ago)

Scores higher than 43% of npm servers

Category CRM and Sales

Trust breakdown (7 categories)

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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 34 of 108 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency13
  • 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
  • Maintenance check failed: the publisher has marked this version as deprecated on the registry, telling users to stop installing it. See how to fix → Fail
  • 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
Changelog

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.

  • 28 Oct 26 0
    • Stability: 0.97 → pass security
  • 27 Oct 26 0
    • Stability: pass → 0.97 functional
  • 24 Oct 26 −5
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
  • 21 Oct 26 0
    • Stability: 0.97 → pass security
  • 20 Oct 26 0
    • Stability: pass → 0.97 functional
  • 17 Oct 26 +2
    • Stability: 0.83 → pass security
  • 16 Oct 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.

  • 15 Oct 26 −3
    • Stability: pass → 0.80 functional
Diagnostics

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 4 Nov 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 →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 108 packages
Packages resolved 108
Stale 34
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~403 tokens

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 →

Tool Tokens
book_service ~136

Book a cleaning or service appointment. Creates the job, assigns staff, sends WhatsApp confirmation with payment link.

NameTypeReqDescription
addressstringyesFull service address
business_idnumber–Business ID
customer_namestringyesFull name of the customer
customer_phonestringyesCustomer WhatsApp number in E.164 format e.g. +14031234567
datestringyesDate in YYYY-MM-DD format
servicestringyesService name e.g. "Deep Clean", "Standard Clean"
timestringyesTime 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.

NameTypeReqDescription
business_idnumber–Business ID (optional — uses default if not provided)
datestringyesDate 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.

NameTypeReqDescription
invoice_idnumberyesInvoice ID
stepnumber–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).

NameTypeReqDescription
amountnumberyesAmount to charge
currencystring–Currency
customer_phonestringyesCustomer WhatsApp number in E.164 format
job_idnumberyesJob 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.

NameTypeReqDescription
job_idnumberyesJob ID to send briefing for

No output schema declared.

No examples provided.

Install

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

# add to Claude Code
claude mcp add dgtalquantumleap-ai-ebenova-fieldops -- npx -y @ebenova/fieldops-mcp
Common questions

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 72 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 November 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 4 November 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.