Inspect-only MCP server for HTTP 402 and agent-commerce surfaces without executing payment.
Your agent will hit a 402 paywall in the wild. Will it inspect, decide, pay, recover, verify, and continue — or freeze? is a buyer-side HTTP 402 runtime and agent-commerce surface inspector for autonomous agents. In the broader agentic commerce stack, acts as the buyer-side component of an observability and trust-evidence layer for HTTP 402-compatible paid actions. It helps agents inspect…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
Your agent will hit a 402 paywall in the wild. Will it inspect, decide, pay, recover, verify, and continue — or freeze? is a buyer-side HTTP 402 runtime and agent-commerce surface inspector for autonomous agents. In the broader agentic commerce stack, acts as the buyer-side component of an observability and trust-evidence layer for HTTP 402-compatible paid actions. It helps agents inspect paid-action surfaces, distinguish executable payment rails from higher-order commerce protocols, and prove…
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.