ProofSlip — 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

Ephemeral creation and verification of AI agent action receipts

What we know

Ephemeral creation and verification of AI agent action receipts. Published by the owner of npm package @proofslip/mcp-server. Receipt-based verification for AI agent workflows — create, verify, and poll ephemeral proof objects.

Maintenance / activity evidence

233 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.
Signed workflow receipts are sent to a third-party verification service; ensure receipts do not expose credentials or customer information. Reported action classes: Create workflow receipt. Complete write authority is not verified.
ProofSlip API key
Sensitive access: Service account information and data accessible by supplied credentials

Signed workflow receipts are sent to a third-party verification service; ensure receipts do not expose credentials or customer information.
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

· 233 package downloads / 30 days

Downloads observed Oct 10, 2026.

Exact npm package @proofslip/mcp-server; provider interval 2026-09-09–2026-10-08 (inclusive); observed 2026-10-10T04:43:53Z.

All limitations / Review context

Has @proofslip/mcp-server changed publishing identity, permissions, install requirements, or risk exposure?

Published package documentation reviewed; public listing with prominently disclosed risks: Signed workflow receipts are sent to a third-party verification service; ensure receipts do not expose credentials or customer information.

Signed workflow receipts are sent to a third-party verification service; ensure receipts do not expose credentials or customer information.
Public listing suitability does not imply safe installation or entitlement to access third-party accounts.
ProofSlip API key
Reviewed write actions: Create workflow receipt
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

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

Technical identity

npm/@proofslip/mcp-server

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

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 ↗
@proofslip/mcp-server
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

Publisher documentation reviewed; compatibility with user environment and live service not tested.
Documented by publisher; environment and client prerequisites still required. Placeholder values must not be executed verbatim.
MCP100 normalized this JSON from publisher-documented package, env and/or client examples; not verified byte-for-byte against a live client. This is not Codex config.toml or VS Code servers JSON.
Creation of receipts is not a safe smoke test.
Never test by purchase, publication, deletion, financial transfer, sending or account mutation.
Checked against publisher README or official docs; not executed. A library install is not MCP host registration.
MCP client unregister, stopping hosted processes, package uninstall, OAuth disconnect and token revocation are distinct actions.

Install / connect
Publisher instructions
PROOFSLIP_API_KEY required to create receipts; separate read-only receipt verification.
publisher install or stdio launch · Publisher instructions
npx -y @proofslip/mcp-server
publisher documented install or connection · Claude Code only · Publisher instructions
claude mcp add proofslip -- npx -y @proofslip/mcp-server
Configure / authenticate
MCP100 setup guide
MCP client npx -y @proofslip/mcp-server; PROOFSLIP_API_KEY only needed for receipt creation, not public verify_receipt/check_receipt_status.
claude desktop or cursor mcpServers json · MCP100 composed guide
{ "mcpServers": { "proofslip": { "args": [ "-y", "@proofslip/mcp-server" ], "command": "npx", "env": { "PROOFSLIP_API_KEY": "ak_REPLACE" } } } }
Check connection
Suggested check
Publisher verify_receipt or check_receipt_status with existing benign receipt id requires no key; create_receipt uses PROOFSLIP_API_KEY and should not be used as a smoke test.
Remove / uninstall / revoke
MCP100 setup guide
If you added this integration to Claude Code under the registration name `proofslip`, run `claude mcp remove proofslip` to unregister that client entry. In Claude Desktop, Cursor, VS Code or another host, delete/disable the corresponding named MCP registration in that host's settings and restart/reconnect. If you installed an npm package globally or operate a separate HTTP server, uninstall/stop it with its original deployment method. This does not delete user data or revoke service credentials.
MCP client unregister, stopping hosted processes, package uninstall, OAuth disconnect and token revocation are distinct actions.
A claude mcp remove command is only valid for Claude Code when the local registration actually has that name. Other MCP hosts require their own UI/config cleanup.
Separate credential guidance / limitations: ProofSlip API key is only required to create receipts, not verify or poll them. Official README includes public signup and token issuance but no exact revoke action.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove proofslip

Official Documentation & Sources

What it does

Ephemeral creation and verification of AI agent action receipts. Published by the owner of npm package @proofslip/mcp-server. Receipt-based verification for AI agent workflows — create, verify, and poll ephemeral proof objects.

Capability: Security & Testing
Resource type: MCP Server
Best fit: Ephemeral creation and verification of AI agent action receipts

Representative uses

Ephemeral creation and verification of AI agent action receipts

Limitations

Signed workflow receipts are sent to a third-party verification service; ensure receipts do not expose credentials or customer information.
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: ProofSlip API key
Permissions: Signed workflow receipts are sent to a third-party verification service; ensure receipts do not expose credentials or customer information.
Data handling: Signed workflow receipts are sent to a third-party verification service; ensure receipts do not expose credentials or customer information.
Cost: Credit/subscription costs may apply; inspect provider docs
Risk and cautions: Signed workflow receipts are sent to a third-party verification service; ensure receipts do not expose credentials or customer information.

Access scope and cautions

Write actions: Not verified Create workflow receipt
Sensitive access: Service account information and data accessible by supplied credentials
Risk level: medium
Security notes: Signed workflow receipts are sent to a third-party verification service; ensure receipts do not expose credentials or customer information. 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: ProofSlip API key

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. The partial inventory lists: Create workflow receipt. Recorded permission context: Signed workflow receipts are sent to a third-party verification service; ensure receipts do not expose credentials or customer information.

What data-handling boundary should I consider?

Signed workflow receipts are sent to a third-party verification service; ensure receipts do not expose credentials or customer information. Recorded sensitive-access context: Service account information and data accessible by supplied credentials.

What limitations and risks should I check before use?

Signed workflow receipts are sent to a third-party verification service; ensure receipts do not expose credentials or customer information. 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.

What cost model is recorded?

The reviewed cost model is Credit/subscription costs may apply; inspect provider docs. This classification does not establish current prices, quotas or the cost of every downstream operation. Check the applicable service terms before authorizing paid actions.