What are the risks of connecting to npm:@expensebot/mcp-server-auth?

References sensitive file paths / environment secrets. Overall trust grade D (66/100).

When was npm:@expensebot/mcp-server-auth last audited?

Last checked 2026-06-03; wmcp.sh re-checks it on a schedule for tool drift and rug-pulls.

npm:@expensebot/mcp-server-auth

Item: npm:@expensebot/mcp-server-auth
Rating: 66
Author: wmcp.sh

https://www.npmjs.com/package/@expensebot/mcp-server-auth

66/100 · MCP Trust Grade · checked 1mo ago · MCP 0.6.1

Is the npm:@expensebot/mcp-server-auth MCP server safe to use?

Independent trust grade D (66/100). References sensitive file paths / environment secrets. wmcp.sh continuously watches npm:@expensebot/mcp-server-auth for tool drift and rug-pulls. The grade is free and identical whether or not the operator pays.

What it offers — 30 tools · Developer Tools

search_expenses

get_spending_summary

get_deep_analytics

create_report

list_reports

get_report_details

share_report

check_compliance

fix_compliance

check_tax_deductibility

search_knowledge

submit_receipt

add_cash_expense

parse_expense

process_gmail_receipts

scan_gmail

get_signup_link

add_mileage_entry

+12 more tools

Spec / packaging20%100

✓ depends on an MCP SDK
✓ declares a bin entry (runnable server)
✓ 30 tool(s) detected in source

Security (OWASP MCP)30%25

⚠ references sensitive file paths / env secrets
uses eval/exec/child_process (review for unsanitized input)
scanned 4 source files

Maintenance / popularity20%100

published within 90 days
10 published versions

Tool hygiene15%70

no TypeScript types
1 runtime deps

Transparency / provenance15%55

no repository link
✓ MIT license
58 weekly downloads

Findings

WARNMCP08 References sensitive file paths / environment secrets.

INFO Static analysis of npm package @expensebot/mcp-server-auth@0.6.1 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured.

Grade another server

We re-grade npm:@expensebot/mcp-server-auth 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.

MCP Trust report card — npm:@expensebot/mcp-server-auth grade D

Share on X Open card image

https://wmcp.sh/mcp/grade/npm%3A%40expensebot%2Fmcp-server-auth

Embed this grade

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.

Markdown (for your README)

[![MCP Trust Grade D](https://wmcp.sh/mcp/grade/npm%3A%40expensebot%2Fmcp-server-auth/badge.svg)](https://wmcp.sh/mcp/grade/npm%3A%40expensebot%2Fmcp-server-auth)

HTML

<a href="https://wmcp.sh/mcp/grade/npm%3A%40expensebot%2Fmcp-server-auth"><img src="https://wmcp.sh/mcp/grade/npm%3A%40expensebot%2Fmcp-server-auth/badge.svg" alt="MCP Trust Grade D · wmcp.sh"></a>

Agents: check this before connecting

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.