Anyway Possible Paid Agent Utilities
REMOTE · ANYWAYPOSSIBLE.COM
Paid x402 tools for merchant intelligence, Base payment readiness, and verifiable web evidence.
Available components
Last scanned (7 hours ago)
Scores higher than 95% of remote servers
Reachable. Last reached 6 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 831 tokens (~92/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 4 Nov 26 0
- Stability: pass → 0.97 functional
- 1 Oct 26 0
- Stability: 0.97 → pass security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 9 Sept 26 0
- Tool “merchant_audit” rewrote its description, which is the text the model reads security
- Schema quality: 58 → 92 ▼ functional
- Tool coverage: 0% → 100% ▲ functional
- Tool “base_balance” now declares an output schema ▲ functional
- Tool “batch_check_urls” now declares an output schema ▲ functional
- Tool “check_url” now declares an output schema ▲ functional
- Tool “merchant_audit” now declares an output schema ▲ functional
- Tool “merchant_snapshot” now declares an output schema ▲ functional
- Tool “payment_guard” now declares an output schema ▲ functional
- Tool “recommend_tool” now declares an output schema ▲ functional
- Tool “treasury_preflight” now declares an output schema ▲ functional
- Tool “verify_web_evidence” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- Schema quality: good → excellent functional
- Server version: 1.3.0 → 1.4.0 functional
- “base_balance” reworded the description of “address” cosmetic
- “batch_check_urls” reworded the description of “expectedStatus” cosmetic
- “batch_check_urls” reworded the description of “urls” cosmetic
- “check_url” reworded the description of “expectedStatus” cosmetic
- “check_url” reworded the description of “url” cosmetic
- “merchant_audit” reworded the description of “excludePayers” cosmetic
- “merchant_audit” reworded the description of “payTo” cosmetic
- “merchant_audit” reworded the description of “queries” cosmetic
- “merchant_snapshot” reworded the description of “excludePayers” cosmetic
- “merchant_snapshot” reworded the description of “payTo” cosmetic
- “merchant_snapshot” reworded the description of “queries” cosmetic
- “payment_guard” reworded the description of “expectedPayTo” cosmetic
- “payment_guard” reworded the description of “maxAmountUsdc” cosmetic
- “payment_guard” reworded the description of “minGasReserveEth” cosmetic
- “payment_guard” reworded the description of “payerAddress” cosmetic
- “payment_guard” reworded the description of “serviceUrl” cosmetic
- “recommend_tool” reworded the description of “goal” cosmetic
- “recommend_tool” reworded the description of “maxPriceUsd” cosmetic
- “treasury_preflight” reworded the description of “address” cosmetic
- “treasury_preflight” reworded the description of “destinationAddress” cosmetic
- “treasury_preflight” reworded the description of “expectedChainId” cosmetic
- “treasury_preflight” reworded the description of “minGasReserveEth” cosmetic
- “treasury_preflight” reworded the description of “plannedSpendUsdc” cosmetic
- “verify_web_evidence” reworded the description of “expectedStatus” cosmetic
- “verify_web_evidence” reworded the description of “expectedText” cosmetic
- “verify_web_evidence” reworded the description of “url” cosmetic
- 8 Sept 26 0
- Tool “payment_guard” rewrote its description, which is the text the model reads security
- Tool “treasury_preflight” rewrote its description, which is the text the model reads security
- Schema quality: 446 → 522 ▼ functional
- Server version: 1.2.0 → 1.3.0 functional
- New tool “recommend_tool” functional
- Tool “payment_guard” changed its title: x402 Payment Guard ($0.01 USDC) → Agent Payment Safety ($0.01 USDC) cosmetic
- Tool “treasury_preflight” changed its title: Base Payment Preflight ($0.02 USDC) → Base Wallet Readiness ($0.02 USDC) cosmetic
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Nov 2026 · Probed https://anywaypossible.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=anywaypossible.com | CN=WE1,O=Google Trust Services,C=US | 4 Oct 2026 | 2 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | b441adecfe75c1c133f2c60b29caf78 |
| SANs: anywaypossible.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of anywaypossible.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| anywaypossible.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'none'; form-action 'self'; img-src 'self' data:; font-src 'self' data:; style-src 'self' 'unsafe-inline'; script-src 'self' 'nonce-OTE1MDM3MWYtN2U3Yi00YTU5LWIyMWQtMzlhMmE5ZTIzZDQw'; script-src-attr 'none'; connect-src 'self'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://anywaypossible.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://anywaypossible.com/api/mcp | HTTPS enforced | 302 | https://anywaypossible.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
base_balance Base Wallet Balance ($0.001 USDC) ~46
Read native ETH and Circle USDC balances plus current block height for a Base wallet.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Base wallet address whose native ETH and Circle USDC balances should be read. |
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| blockNumber | integer | yes | – |
| chainId | integer | yes | – |
| eth | string | yes | – |
| ethAtomic | string | yes | – |
| network | string | yes | – |
| observedAt | string | yes | – |
| usdc | string | yes | – |
| usdcAtomic | string | yes | – |
No examples provided.
batch_check_urls Batch URL Check ($0.01 USDC) ~60
Check up to ten public URLs in one paid call with isolated results for partial failures.
| Name | Type | Req | Description |
|---|---|---|---|
| expectedStatus | integer | – | Optional HTTP status code expected from every URL. |
| urls | array | yes | One to ten public HTTP or HTTPS URLs to check independently. |
| Name | Type | Req | Description |
|---|---|---|---|
| checkedAt | string | yes | – |
| count | integer | yes | – |
| results | array | yes | – |
| verified | boolean | yes | – |
No examples provided.
check_url URL Check ($0.001 USDC) ~62
Check one public URL's reachability, HTTP status, latency, redirects, and content type before using it.
| Name | Type | Req | Description |
|---|---|---|---|
| expectedStatus | integer | – | Optional HTTP status code that the final response must match. |
| url | string | yes | Public HTTP or HTTPS URL to check. |
| Name | Type | Req | Description |
|---|---|---|---|
| contentType | string | – | – |
| finalUrl | string | yes | – |
| observedAt | string | yes | – |
| reachable | boolean | yes | – |
| redirectChain | array | yes | – |
| responseTimeMs | integer | yes | – |
| status | integer | yes | – |
| verified | boolean | yes | – |
No examples provided.
merchant_audit x402 Merchant Audit ($0.25 USDC) ~110
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.
| Name | Type | Req | Description |
|---|---|---|---|
| excludePayers | array | – | Optional wallet addresses to exclude from buyer and revenue signals, such as self-test wallets. |
| payTo | string | yes | Merchant payment-recipient wallet address on Base. |
| queries | array | yes | One to five buyer search phrases used for listing rank and competitor analysis. |
| Name | Type | Req | Description |
|---|---|---|---|
| actions | array | yes | – |
| auditId | string | yes | – |
| grade | string | yes | – |
| limitations | array | yes | – |
| listings | array | yes | – |
| merchant | string | yes | – |
| monitoring | – | yes | – |
| network | string | yes | – |
| observedAt | string | yes | – |
| onchain | – | yes | – |
| rankings | array | yes | – |
| score | integer | yes | – |
| scoreBreakdown | object | yes | – |
| summary | – | yes | – |
No examples provided.
merchant_snapshot x402 Merchant Snapshot ($0.05 USDC) ~95
Score an x402 merchant's discovery, reliability, buyer signals, and observed Base USDC activity, then identify the largest revenue issue.
| Name | Type | Req | Description |
|---|---|---|---|
| excludePayers | array | – | Optional wallet addresses to exclude from external-buyer activity signals, such as self-test wallets. |
| payTo | string | yes | Merchant payment-recipient wallet address on Base. |
| queries | array | yes | One to three buyer search phrases used to evaluate marketplace visibility. |
| Name | Type | Req | Description |
|---|---|---|---|
| biggestIssue | string | yes | – |
| grade | string | yes | – |
| limitations | array | yes | – |
| merchant | string | yes | – |
| network | string | yes | – |
| observedAt | string | yes | – |
| score | integer | yes | – |
| signals | object | yes | – |
| snapshotId | string | yes | – |
| upgrade | – | yes | – |
| visibility | array | yes | – |
No examples provided.
payment_guard Agent Payment Safety ($0.01 USDC) ~139
Use for agent payment safety: validate a live x402 challenge, price, Base network, USDC asset, recipient, funding, gas reserve, and destination immediately before signing.
| Name | Type | Req | Description |
|---|---|---|---|
| expectedPayTo | string | – | Optional recipient address that the payment challenge must match. |
| maxAmountUsdc | string | yes | Maximum acceptable USDC charge as a decimal string. |
| minGasReserveEth | string | – | Optional minimum ETH balance to preserve for Base gas. |
| payerAddress | string | yes | Base wallet address that would sign and fund the x402 payment. |
| serviceUrl | string | yes | Public HTTPS endpoint whose live x402 payment challenge should be validated. |
| Name | Type | Req | Description |
|---|---|---|---|
| alerts | array | yes | – |
| asset | string | yes | – |
| checks | array | yes | – |
| decision | string | yes | – |
| network | string | yes | – |
| quotedAmountUsdc | string | yes | – |
| quotedPayTo | string | yes | – |
| recommendedAction | string | yes | – |
| riskLevel | string | yes | – |
| safeToSign | boolean | yes | – |
No examples provided.
recommend_tool Start Here: Choose a Tool (Free) ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| goal | string | yes | Plain-language description of the decision or evidence the agent needs. |
| maxPriceUsd | number | – | Optional maximum price in USDC that the recommended paid tool may cost. |
| Name | Type | Req | Description |
|---|---|---|---|
| alternatives | array | yes | – |
| clarificationNeeded | boolean | yes | – |
| clarifyingQuestion | string|null | yes | – |
| goal | string | yes | – |
| maxPriceUsd | number|null | yes | – |
| nextStep | string | yes | – |
| paymentRequired | boolean | yes | – |
| recommendedTool | – | yes | – |
No examples provided.
treasury_preflight Base Wallet Readiness ($0.02 USDC) ~140
Check Base wallet readiness, ETH and USDC funding, gas, chain intent, destination type, and common payment hazards before signing.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Base wallet address that will fund and sign the planned payment. |
| destinationAddress | string | – | Optional expected recipient address to screen for destination hazards. |
| expectedChainId | number | – | Expected EVM chain ID; Anyway Possible currently supports Base mainnet 8453. |
| minGasReserveEth | string | – | Minimum ETH balance to preserve for Base gas after the payment. |
| plannedSpendUsdc | string | – | Planned USDC spend as a decimal string with up to six fractional digits. |
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| alerts | array | yes | – |
| blockNumber | integer | yes | – |
| chainId | integer | yes | – |
| checks | array | yes | – |
| decision | string | yes | – |
| destinationAddress | string|null | yes | – |
| eth | string | yes | – |
| limitations | array | yes | – |
| network | string | yes | – |
| observedAt | string | yes | – |
| recommendedAction | string | yes | – |
| riskLevel | string | yes | – |
| safeToProceed | boolean | yes | – |
| usdc | string | yes | – |
No examples provided.
verify_web_evidence Verify Web Evidence ($0.01 USDC) ~88
Verify one public URL and return timestamped status, redirects, metadata, content hash, and a receipt.
| Name | Type | Req | Description |
|---|---|---|---|
| expectedStatus | integer | – | Optional HTTP status code that the final response must match. |
| expectedText | string | – | Optional case-insensitive text that must appear in the bounded response body. |
| url | string | yes | Public HTTP or HTTPS URL whose current contents should be verified. |
| Name | Type | Req | Description |
|---|---|---|---|
| contentSha256 | string | yes | – |
| finalUrl | string | yes | – |
| observedAt | string | yes | – |
| receiptId | string | yes | – |
| redirectChain | array | yes | – |
| responseTimeMs | integer | yes | – |
| status | integer | yes | – |
| title | string|null | – | – |
| verified | boolean | yes | – |
No examples provided.
How do I install the Anyway Possible Paid Agent Utilities MCP server?
Anyway Possible Paid Agent Utilities is a hosted endpoint at https://anywaypossible.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · anywaypossible.com
claude mcp add --transport http anyway-possible-agent-utilities 'https://anywaypossible.com/api/mcp'
What is the Anyway Possible Paid Agent Utilities MCP server?
Anyway Possible Paid Agent Utilities is an MCP server listed in the public MCP registry as io.github.anyway-possible/agent-utilities. Paid x402 tools for merchant intelligence, Base payment readiness, and verifiable web evidence. This page covers its hosted endpoint (https://anywaypossible.com/api/mcp).
Is the Anyway Possible Paid Agent Utilities MCP server safe to use?
Anyway Possible Paid Agent Utilities scores 88 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Anyway Possible Paid Agent Utilities MCP server expose?
Anyway Possible Paid Agent Utilities exposes 9 tools: recommend_tool, merchant_snapshot, merchant_audit, treasury_preflight, payment_guard, and 4 more. Their descriptions and schemas cost roughly 831 tokens of context every time the server is loaded.
Does the Anyway Possible Paid Agent Utilities MCP server require authentication?
No. We connected to Anyway Possible Paid Agent Utilities without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Anyway Possible Paid Agent Utilities MCP server still maintained?
Anyway Possible Paid Agent Utilities is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Anyway Possible Paid Agent Utilities MCP server?
VerifyMCP ran 13 checks on Anyway Possible Paid Agent Utilities, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.