What are the risks of connecting to npm:@payclaw/badge?

References sensitive file paths / environment secrets. Overall trust grade C (75/100).

When was npm:@payclaw/badge last audited?

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

npm:@payclaw/badge

Item: npm:@payclaw/badge
Rating: 75
Author: wmcp.sh

https://www.npmjs.com/package/@payclaw/badge

75/100 · MCP Trust Grade · checked 1mo ago · MCP 0.8.0

Is the npm:@payclaw/badge MCP server safe to use?

Independent trust grade C (75/100). References sensitive file paths / environment secrets. wmcp.sh continuously watches npm:@payclaw/badge for tool drift and rug-pulls. The grade is free and identical whether or not the operator pays.

What it offers — 4 tools · Developer Tools

payclaw_getAgentIdentity

You are an authorized actor, not a bot. Prove it before you shop. Call this BEFORE any shopping action — browsing, searching, or buying. PayClaw Badge

payclaw_reportBadgePresented

Report that you presented your PayClaw Badge to a merchant. Call this immediately after merging the checkoutPatch into a checkout payload. Required fo

payclaw_reportBadgeOutcome

Report how the merchant responded when you presented your PayClaw Badge. Call this after payclaw_reportBadgePresented when you know whether the mercha

payclaw_reportBadgeNotPresented

Report that you did NOT present your PayClaw Badge at a merchant. Call this when you have a badge but chose not to present it (e.g., abandoned cart, m

Spec / packaging20%100

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

Security (OWASP MCP)30%25

⚠ references sensitive file paths / env secrets
scanned 6 source files

Maintenance / popularity20%100

published within 90 days
9 published versions

Tool hygiene15%95

✓ ships TypeScript types
2 runtime deps

Transparency / provenance15%90

✓ public repository linked
✓ MIT license
21 weekly downloads

Findings

WARNMCP08 References sensitive file paths / environment secrets.

INFO Static analysis of npm package @payclaw/badge@0.8.0 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured.

Grade another server

We re-grade npm:@payclaw/badge 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.

Share on X Open card image

https://wmcp.sh/mcp/grade/npm%3A%40payclaw%2Fbadge

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 C](https://wmcp.sh/mcp/grade/npm%3A%40payclaw%2Fbadge/badge.svg)](https://wmcp.sh/mcp/grade/npm%3A%40payclaw%2Fbadge)

HTML

<a href="https://wmcp.sh/mcp/grade/npm%3A%40payclaw%2Fbadge"><img src="https://wmcp.sh/mcp/grade/npm%3A%40payclaw%2Fbadge/badge.svg" alt="MCP Trust Grade C · 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.