coffee.402/mcp — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Monitor identity continuity, MCP tool inventory, permissions and adoption.

Reviewed Oct 10, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Agent identity, x402 payments and escrow verification through MCP

What we know

Agent identity, x402 payments and escrow verification through MCP. Published by the owner of npm package 402coffee-mcp. Trust layer for agent payments (x402, Base): verify agents, risk scores, signed escrow verdicts.

Maintenance / activity evidence

232 npm downloads, 2026-09-09 to 2026-10-08

Tracking evidence observed Oct 10, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high_for_identity_and_metrics_medium_for_verified_package_description.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
x402 payment and escrow verification can interact with blockchain transactions; verify paid calls, account identity, and wallet controls. Reported action classes: Payment/escrow actions when authorized. Complete write authority is not verified.
Wallet/payment credentials for paid calls; verify actual signer requirements
Sensitive access: Service account information and data accessible by supplied credentials

x402 payment and escrow verification can interact with blockchain transactions; verify paid calls, account identity, and wallet controls.
Public listing suitability does not imply safe installation or entitlement to access third-party accounts.

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

· 232 package downloads / 30 days

Downloads observed Oct 10, 2026.

Exact npm package 402coffee-mcp; provider interval 2026-09-09–2026-10-08 (inclusive); observed 2026-10-10T04:43:53Z.

All limitations / Review context

Has 402coffee-mcp changed publishing identity, permissions, install requirements, or risk exposure?

Published package documentation reviewed; public listing with prominently disclosed risks: x402 payment and escrow verification can interact with blockchain transactions; verify paid calls, account identity, and wallet controls.

x402 payment and escrow verification can interact with blockchain transactions; verify paid calls, account identity, and wallet controls.
Public listing suitability does not imply safe installation or entitlement to access third-party accounts.
Wallet/payment credentials for paid calls; verify actual signer requirements
Reviewed write actions: Payment/escrow actions when authorized
Sensitive access: Service account information and data accessible by supplied credentials
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Respect upstream entitlements, version constraints and least-privilege setup.
Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
Publicly documented capabilities are not a guarantee of a safe deployment; review third-party data processing and access scopes.
Public exact-package npm downloads observed for recent 30-day window.

Original activity observations

232 npm downloads, 2026-09-09 to 2026-10-08

Technical identity

npm/402coffee-mcp

Exact implementation source: https://www.npmjs.com/package/402coffee-mcp ↗
Reviewed resource type: MCP Server
Package identity: npm:402coffee-mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 10, 2026 · Latest source observation Oct 10, 2026

Registry source ↗
registry.modelcontextprotocol.io/v0/servers
Source material retained for this review.
Package registry ↗
402coffee-mcp
Recorded package identity, distribution or download evidence.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Warning

Financial risk: package may sign and pay for calls or buy tokens. Never use production wallet/private key to test. Obtain explicit spending approval.
A private key is not an API key; do not expose it in project files, screenshots, logs, or chat transcripts.
Paid x402 calls sign transactions on Base; paid usage must be opt-in and explicitly authorized.
Literal command/entry path confirmed against official README; does not validate runtime or host compatibility.
Prior reviewed safety note: Never use a personal treasury wallet for a connection check.
Prior reviewed safety note: Do not use any paid x402 tool, make a transfer, or set PAYER_PRIVATE_KEY as a connectivity test.
Prior reviewed safety note: Do not delete user data or assume this cancels upstream authorizations.
Client removal, software uninstall, persistent-data deletion and credential revocation are separate actions.

Install / connect
Publisher instructions
Publisher-documented install or connect path; prerequisites and any extra host configuration remain required.
publisher install or stdio launch · Publisher instructions
npx -y 402coffee-mcp
Configure / authenticate
MCP100 setup guide
MCP client config runs npx 402coffee-mcp; optional PAYER_PRIVATE_KEY enables paid x402 tools, while free tools work without a wallet.
Check connection
Suggested check
Inspect registered free tools only; do not invoke any billable tools.
Remove / uninstall / revoke
MCP100 setup guide
If registered in Claude Code under the name `402coffee`, remove the client entry with `claude mcp remove 402coffee`. For other MCP hosts remove the matching server/connector in that host’s MCP settings. Remove a globally installed software package separately if applicable; this does not delete data or revoke a service credential.
Client removal, software uninstall, persistent-data deletion and credential revocation are separate actions.
Separate credential guidance (provider revocation is not verified): Deleting the server or removing PAYER_PRIVATE_KEY from client configuration does NOT invalidate that wallet key. If exposed, move assets to a newly controlled wallet using a trusted wallet procedure; this is security guidance, not a publisher CLI revoke command.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove 402coffee

Official Documentation & Sources

https://www.npmjs.com/package/402coffee-mcp ↗

What it does

Agent identity, x402 payments and escrow verification through MCP. Published by the owner of npm package 402coffee-mcp. Trust layer for agent payments (x402, Base): verify agents, risk scores, signed escrow verdicts.

Capability: Finance & Payments
Resource type: MCP Server
Industry: Financial Services & Investing
Best fit: Agent identity, x402 payments and escrow verification through MCP

Representative uses

Agent identity, x402 payments and escrow verification through MCP

Limitations

x402 payment and escrow verification can interact with blockchain transactions; verify paid calls, account identity, and wallet controls.
Publicly documented capabilities are not a guarantee of a safe deployment; review third-party data processing and access scopes.
Public exact-package npm downloads observed for recent 30-day window.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Wallet/payment credentials for paid calls; verify actual signer requirements
Permissions: x402 payment and escrow verification can interact with blockchain transactions; verify paid calls, account identity, and wallet controls.
Data handling: x402 payment and escrow verification can interact with blockchain transactions; verify paid calls, account identity, and wallet controls.
Cost: USDC x402 pay-per-call
Risk and cautions: x402 payment and escrow verification can interact with blockchain transactions; verify paid calls, account identity, and wallet controls.

Access scope and cautions

Write actions: Not verified Payment/escrow actions when authorized
Sensitive access: Service account information and data accessible by supplied credentials
Risk level: high
Security notes: x402 payment and escrow verification can interact with blockchain transactions; verify paid calls, account identity, and wallet controls. Public listing suitability does not imply safe installation or entitlement to access third-party accounts.

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-10T04:43:53Z. Watchlist tracking is not a recommendation or a security certification.

What setup and authentication are documented?

A complete connection procedure is not verified. Client notes: Do not infer shell entrypoint or automated credential setup if a command is not explicitly verified. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: Wallet/payment credentials for paid calls; verify actual signer requirements

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. The partial inventory lists: Payment/escrow actions when authorized. Recorded permission context: x402 payment and escrow verification can interact with blockchain transactions; verify paid calls, account identity, and wallet controls.

What data-handling boundary should I consider?

x402 payment and escrow verification can interact with blockchain transactions; verify paid calls, account identity, and wallet controls. Recorded sensitive-access context: Service account information and data accessible by supplied credentials.

What limitations and risks should I check before use?

x402 payment and escrow verification can interact with blockchain transactions; verify paid calls, account identity, and wallet controls. Publicly documented capabilities are not a guarantee of a safe deployment; review third-party data processing and access scopes. Public exact-package npm downloads observed for recent 30-day window. Public listing suitability does not imply safe installation or entitlement to access third-party accounts. Respect upstream entitlements, version constraints and least-privilege setup.