# three.ws Agent Payments (io.github.nirholas/agentcore-payments-mcp@0.1.4) > Source: > Published: 2026-08-19 22:05:25+00:00 [← Index](/leaderboard) # three.ws Agent Payments Governed x402 payment sessions: pay any endpoint with budget, allowlist & per-tx caps, no key. The current version, v0.1.4, was published to the official MCP registry on 2026-08-19. It is distributed as @three-ws/agentcore-payments-mcp on npm, filed under Finance & Payments by this index, and declares 4 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; [the index's current counts](/stats) put this record in context. ## Using three.ws Agent Payments in Claude, Cursor, Gemini CLI, Cline, or Zed? MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and **HOLDs the call** when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use **Install this server** for that). Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less ``` uv tool install mcpindex-gate && mcpindex-config-wire ``` [method](/methodology) Semantic screen found no manipulation pattern in the description. Conformance probe not yet run. `mcpindex.integrity.description` passINFOevidence“No suspicious instructions found”via static_description - - Semantic screen only - the deterministic conformance probe has not run on this server - - Confidence is reported but not yet calibrated (v1) - - Screen reads the tool description, not the live behavior - - advisory - - registry description only no input schema - - screen model 8b - - Still current: the description we screened is unchanged, re-checked against the registry - - The registry listing (version, packages, links) changed after this screen ran - the description we assessed did not Semantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page. Own this server? [Screen its description →](/screen) ## That verdict was true at screening time (snapshot 2026-08-19). Contracts can change after screening, with no version bump. The gate pins three.ws Agent Payments’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday. [See your first HOLD in 2 minutes →](/guides/install-the-gate-first-hold) Related: [how to trust an MCP server](/guides/how-to-trust-an-mcp-server) · [screen before install](/guides/screen-mcp-server-before-install) · [silent contract drift](/guides/mcp-silent-contract-drift) People vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land. ``` [Independent trust record for three.ws Agent Payments](https://mcpindex.ai/server/io-github-nirholas-agentcore-payments-mcp) - screening verdict, registry provenance, and contract drift monitoring. Independent trust record for three.ws Agent Payments - screening verdict, registry provenance, and contract drift monitoring. ``` A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does. ``` [![mcpindex](https://mcpindex.ai/api/v1/badge/io-github-nirholas-agentcore-payments-mcp)](https://mcpindex.ai/server/io-github-nirholas-agentcore-payments-mcp) mcpindex verdict ``` `THREE_WS_SESSION` Your three.ws session token (value of the `__Host-sid` cookie from a signed-in browser). Required for account management operations: create_payment_session, list_payment_sessions, check_payment_session, cancel_payment_session. `PAYMENT_SESSION_TOKEN` A payment session bearer token (starts with 'pss_') from create_payment_session. Used by the agent for pay_with_session calls when no inline token is passed. Treat like a spending card — it authorizes payments up to the session's budget. `THREE_WS_BASE` Base URL of the three.ws API. Override only when self-hosting or targeting a preview deployment. `THREE_WS_TIMEOUT_MS` Per-request HTTP timeout in milliseconds. x402 payments involve on-chain settlement so this should be generous (default: 30000). [methodology](/methodology) [Diavgis — Greek Public Procurementgr.diavgis/procurement](/server/gr-diavgis-procurement) Search Greek public procurement: tenders, awards, contracts, payments, buyers and suppliers. [three.ws 3D Studio (free)io.github.nirholas/threews-3d-studio-free](/server/io-github-nirholas-threews-3d-studio-free) Free text/image → 3D: generate, rig, avatar-ify, and refine GLB models. No auth, no payment.