io.github.anyway-possiblePublished by GitHub account anyway-possiblev1.0.0Updated Oct 24, 2026
Paid x402 tools for merchant intelligence, Base payment readiness, and verifiable web evidence.
The publisher's own server: Anyway Possible Agent Utilities
Remote paid x402 tools that let an assistant check Base wallet readiness, validate x402 payments before signing, audit merchants, and verify public URLs.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.anyway-possible%2Fagent-utilities/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"anyway-possible-paid-agent-utilities": {
"type": "http",
"url": "https://anywaypossible.com/api/mcp"
}
}
}Anyway Possible provides paid, decision-ready checks for autonomous agents before they pay, cite, or act. Agents can connect without an account through remote MCP or call the HTTP APIs directly, paying per successful answer in USDC on Base through x402.
An agent can reason over information it already has, but it cannot independently create fresh external evidence, enforce a payment policy at signing time, or turn several live systems into a stable answer by reasoning alone. Anyway Possible performs those bounded observations and validations, then returns structured decisions with timestamps, receipts, hashes, and explicit limitations where relevant.
Remote MCP endpoint:
Client-specific setup for Codex, Claude Code, Cursor, and any Streamable HTTP MCP client is published in the agent integration guide. Connecting and calling the free recommend_tool router does not require an account or payment. Paid tools require an x402-capable client with a funded Base USDC wallet; connecting the server alone does not grant spending authority. A payment-capable TypeScript example shows the complete discover, approve, pay, retry, and receive-result path.
Machine-readable contracts:
All prices are USDC on Base mainnet. An unpaid request returns an x402 v2 payment requirement containing the exact amount, asset, network, recipient, and timeout. The client decides whether to sign and then retries with payment authorization.
The service is discoverable through Coinbase x402 Bazaar metadata, the official MCP Registry, Smithery-compatible server-card metadata, downstream registries that ingest the official Registry, direct HTTP/OpenAPI, llms.txt, and the public catalog. Human-facing guides explain x402, payment safety, and merchant conversion in plain language.
Requirements: Node.js 22.13 or newer.
The canonical product definitions live in lib/product-catalog.mjs. The homepage, docs, examples, catalog, OpenAPI document, and llms.txt are generated from that shared manifest so names, prices, schemas, and examples cannot drift independently.
The APIs reject private and local network targets, bound response sizes and redirects, avoid exposing payer identities in public analytics, and publish a security contact at /.well-known/security.txt. The public status page states exactly what its current check proves and does not claim unrecorded historical uptime.
Source: README.md at commit 9bb4ac4
Start Here: Choose a Tool (Free)
Use this free tool before paying. Describe the decision you need and receive the best Anyway Possible tool, exact price, required inputs, alternatives, and next step. This tool never triggers payment or calls an external service.
goalrequiredmaxPriceUsdx402 Merchant Snapshot ($0.05 USDC)
Score an x402 merchant's discovery, reliability, buyer signals, and observed Base USDC activity, then identify the largest revenue issue.
payTorequiredqueriesrequiredexcludePayersx402 Merchant Audit ($0.25 USDC)
Audit listings, semantic rank, competitor prices, payment reliability, buyer reach, and observed Base USDC activity. Repeated runs with the same wallet and queries return privacy-safe score history and change alerts.
payTorequiredqueriesrequiredexcludePayersBase Wallet Readiness ($0.02 USDC)
Check Base wallet readiness, ETH and USDC funding, gas, chain intent, destination type, and common payment hazards before signing.
addressrequiredexpectedChainIdminGasReserveEthplannedSpendUsdcdestinationAddressAgent Payment Safety ($0.01 USDC)
Use for agent payment safety: validate a live x402 challenge, price, Base network, USDC asset, recipient, funding, gas reserve, and destination immediately before signing.
serviceUrlrequiredpayerAddressrequiredexpectedPayTomaxAmountUsdcrequiredminGasReserveEthBase Wallet Balance ($0.001 USDC)
Read native ETH and Circle USDC balances plus current block height for a Base wallet.
addressrequiredURL Check ($0.001 USDC)
Check one public URL's reachability, HTTP status, latency, redirects, and content type before using it.
urlrequiredexpectedStatusVerify Web Evidence ($0.01 USDC)
Verify one public URL and return timestamped status, redirects, metadata, content hash, and a receipt.
urlrequiredexpectedTextexpectedStatusBatch URL Check ($0.01 USDC)
Check up to ten public URLs in one paid call with isolated results for partial failures.
urlsrequiredexpectedStatus90% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Declare a license in the repository or the registry entry.
https://anywaypossible.com/api/mcpnpm installnpm run devnpm testnpm run lint