Is the npm:@ebenova/fieldops-mcp MCP server safe to use?
Independent trust grade C- (70/100). References sensitive file paths / environment secrets. wmcp.sh continuously watches npm:@ebenova/fieldops-mcp for tool drift and rug-pulls. The grade is free and identical whether or not the operator pays.
What it offers — 5 tools · Finance & Crypto
check_availability
Check available booking slots for a given date. Returns booked and available time slots.
book_service
Book a cleaning or service appointment. Creates the job, assigns staff, sends WhatsApp confirmation with payment link.
send_payment_link
Generate and send a payment link to a customer via WhatsApp. Supports CAD (Polar/Stripe) and NGN (OxaPay).
recover_invoice
Send an escalating WhatsApp payment recovery message for an unpaid invoice. Step 1=polite reminder, 2=firm follow-up, 3=final notice.
send_staff_briefing
Send a WhatsApp job briefing to the assigned staff member with service details, customer info, and location.
INFO Static analysis of npm package @ebenova/fieldops-mcp@1.0.2 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured.
We re-grade npm:@ebenova/fieldops-mcp on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.
Share this report card
A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.
A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.
Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:
https://wmcp.sh/mcp/trust
How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.