MCP Tools DirectoryAbout this integration
Provides an MCP stdio client for a hosted advisory service that scans x402 payment metadata, checks counterparty reputation, reports delivery outcomes, manages service keys and plans, and verifies signed verdicts.
- Transport
- stdio
- Authentication
- api-key
- Initial setup
- credentials
- Runtime
- unattended
- Evidence
- documented
- Package
- tollwarden
- Last compatibility test
- Not independently tested
Connect your agent
tollwardenPinned publisher README and executable npm manifest reviewed. The package and hosted service were not executed or independently security-audited. Core scans are advisory, but some tools create or rotate credentials, write reports or outcomes, or initiate paid plan actions; operators must apply their own mutation and spending policy. The separately configured human approval flow can intentionally pause flagged payments and is not claimed as unattended. The package is source-available under BUSL-1.1.
Capabilities: Scan outgoing and incoming x402 payment metadata, Check and report counterparty reputation, Report payment delivery outcomes bound to prior scans, Mint or rotate service API keys and inspect or subscribe to plans, Verify signed payment-scan verdict attestations
Connected profiles
Additional details
tollwarden
Source ↗ · Checked 2026-09-201.6.0
Source ↗ · Checked 2026-09-20The publisher documents eleven callable stdio tools, including scans, reputation queries, key lifecycle, plan subscription and local attestation verification. Core advisory calls do not document a required human decision; the separately configured flag-override approval path is optional and excluded from this unattended qualification.
Source ↗ · Checked 2026-09-20The hosted service uses an API key issued by its key endpoint; the first documented free-call allowance bypasses payment, after which calls may require x402 payment. Credential creation, rotation, quota and cost policy remain operator responsibilities.
Source ↗ · Checked 2026-09-20The independent npm artifact is launched locally over stdio with npx -y tollwarden and defaults to the publisher's hosted service. Registry naming is treated only as an alias and not as another integration.
Source ↗ · Checked 2026-09-20Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-20