# Anyway Possible Paid Agent Utilities (remote · anywaypossible.com)

Paid x402 tools for merchant intelligence, Base payment readiness, and verifiable web evidence.

- Trust score: 84/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `anywaypossible.com`: 84/100 (this document), [markdown](https://verifymcp.io/servers/anyway-possible-agent-utilities/api-mcp.md), [page](https://verifymcp.io/servers/anyway-possible-agent-utilities/api-mcp)

## Channel facts

- Endpoint: `https://anywaypossible.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 831 tokens (~92/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 67/100
  - Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http anyway-possible-agent-utilities 'https://anywaypossible.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "anyway-possible-agent-utilities": {
      "url": "https://anywaypossible.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "anyway-possible-agent-utilities": {
      "type": "http",
      "url": "https://anywaypossible.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.anyway-possible-agent-utilities]
url = "https://anywaypossible.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "anyway-possible-agent-utilities": {
      "type": "remote",
      "url": "https://anywaypossible.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add anyway-possible-agent-utilities --url 'https://anywaypossible.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  anyway-possible-agent-utilities:
    url: "https://anywaypossible.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "anyway-possible-agent-utilities": {
      "Transport": "http",
      "Url": "https://anywaypossible.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add anyway-possible-agent-utilities -t streamable-http -u 'https://anywaypossible.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "anyway-possible-agent-utilities": {
      "type": "http",
      "url": "https://anywaypossible.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 78, +6)

- [security] Tool “merchant_audit” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 58 → 92
- [functional improvement] Tool coverage: 0% → 100%
- [functional improvement] Tool “base_balance” now declares an output schema
- [functional improvement] Tool “batch_check_urls” now declares an output schema
- [functional improvement] Tool “check_url” now declares an output schema
- [functional improvement] Tool “merchant_audit” now declares an output schema
- [functional improvement] Tool “merchant_snapshot” now declares an output schema
- [functional improvement] Tool “payment_guard” now declares an output schema
- [functional improvement] Tool “recommend_tool” now declares an output schema
- [functional improvement] Tool “treasury_preflight” now declares an output schema
- [functional improvement] 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
- [cosmetic] “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”

### 2026-09-08 (score 72, 0)

- [security] 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
- [functional regression] Schema quality: 446 → 522
- [functional] Server version: 1.2.0 → 1.3.0
- [functional] New tool “recommend_tool”
- [cosmetic] 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)

## MCP tools (9)

### `recommend_tool` (~91 tokens)

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.

Input parameters:

- `goal` (string, required): 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.

Output parameters:

- `alternatives` (array)
- `clarificationNeeded` (boolean)
- `clarifyingQuestion` (string|null)
- `goal` (string)
- `maxPriceUsd` (number|null)
- `nextStep` (string)
- `paymentRequired` (boolean)
- `recommendedTool`

### `merchant_snapshot` (~95 tokens)

x402 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.

Input parameters:

- `excludePayers` (array): Optional wallet addresses to exclude from external-buyer activity signals, such as self-test wallets.
- `payTo` (string, required): Merchant payment-recipient wallet address on Base.
- `queries` (array, required): One to three buyer search phrases used to evaluate marketplace visibility.

Output parameters:

- `biggestIssue` (string)
- `grade` (string)
- `limitations` (array)
- `merchant` (string)
- `network` (string)
- `observedAt` (string)
- `score` (integer)
- `signals` (object)
- `snapshotId` (string)
- `upgrade`
- `visibility` (array)

### `merchant_audit` (~110 tokens)

x402 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.

Input parameters:

- `excludePayers` (array): Optional wallet addresses to exclude from buyer and revenue signals, such as self-test wallets.
- `payTo` (string, required): Merchant payment-recipient wallet address on Base.
- `queries` (array, required): One to five buyer search phrases used for listing rank and competitor analysis.

Output parameters:

- `actions` (array)
- `auditId` (string)
- `grade` (string)
- `limitations` (array)
- `listings` (array)
- `merchant` (string)
- `monitoring`
- `network` (string)
- `observedAt` (string)
- `onchain`
- `rankings` (array)
- `score` (integer)
- `scoreBreakdown` (object)
- `summary`

### `treasury_preflight` (~140 tokens)

Base Wallet Readiness ($0.02 USDC)

Check Base wallet readiness, ETH and USDC funding, gas, chain intent, destination type, and common payment hazards before signing.

Input parameters:

- `address` (string, required): 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.

Output parameters:

- `address` (string)
- `alerts` (array)
- `blockNumber` (integer)
- `chainId` (integer)
- `checks` (array)
- `decision` (string)
- `destinationAddress` (string|null)
- `eth` (string)
- `limitations` (array)
- `network` (string)
- `observedAt` (string)
- `recommendedAction` (string)
- `riskLevel` (string)
- `safeToProceed` (boolean)
- `usdc` (string)

### `payment_guard` (~139 tokens)

Agent 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.

Input parameters:

- `expectedPayTo` (string): Optional recipient address that the payment challenge must match.
- `maxAmountUsdc` (string, required): Maximum acceptable USDC charge as a decimal string.
- `minGasReserveEth` (string): Optional minimum ETH balance to preserve for Base gas.
- `payerAddress` (string, required): Base wallet address that would sign and fund the x402 payment.
- `serviceUrl` (string, required): Public HTTPS endpoint whose live x402 payment challenge should be validated.

Output parameters:

- `alerts` (array)
- `asset` (string)
- `checks` (array)
- `decision` (string)
- `network` (string)
- `quotedAmountUsdc` (string)
- `quotedPayTo` (string)
- `recommendedAction` (string)
- `riskLevel` (string)
- `safeToSign` (boolean)

### `base_balance` (~46 tokens)

Base Wallet Balance ($0.001 USDC)

Read native ETH and Circle USDC balances plus current block height for a Base wallet.

Input parameters:

- `address` (string, required): Base wallet address whose native ETH and Circle USDC balances should be read.

Output parameters:

- `address` (string)
- `blockNumber` (integer)
- `chainId` (integer)
- `eth` (string)
- `ethAtomic` (string)
- `network` (string)
- `observedAt` (string)
- `usdc` (string)
- `usdcAtomic` (string)

### `check_url` (~62 tokens)

URL Check ($0.001 USDC)

Check one public URL's reachability, HTTP status, latency, redirects, and content type before using it.

Input parameters:

- `expectedStatus` (integer): Optional HTTP status code that the final response must match.
- `url` (string, required): Public HTTP or HTTPS URL to check.

Output parameters:

- `contentType` (string)
- `finalUrl` (string)
- `observedAt` (string)
- `reachable` (boolean)
- `redirectChain` (array)
- `responseTimeMs` (integer)
- `status` (integer)
- `verified` (boolean)

### `verify_web_evidence` (~88 tokens)

Verify Web Evidence ($0.01 USDC)

Verify one public URL and return timestamped status, redirects, metadata, content hash, and a receipt.

Input parameters:

- `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, required): Public HTTP or HTTPS URL whose current contents should be verified.

Output parameters:

- `contentSha256` (string)
- `finalUrl` (string)
- `observedAt` (string)
- `receiptId` (string)
- `redirectChain` (array)
- `responseTimeMs` (integer)
- `status` (integer)
- `title` (string|null)
- `verified` (boolean)

### `batch_check_urls` (~60 tokens)

Batch URL Check ($0.01 USDC)

Check up to ten public URLs in one paid call with isolated results for partial failures.

Input parameters:

- `expectedStatus` (integer): Optional HTTP status code expected from every URL.
- `urls` (array, required): One to ten public HTTP or HTTPS URLs to check independently.

Output parameters:

- `checkedAt` (string)
- `count` (integer)
- `results` (array)
- `verified` (boolean)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/anyway-possible-agent-utilities/api-mcp#diagnostics

## Score history

- 2026-09-21: 84
- 2026-09-20: 83
- 2026-09-19: 83
- 2026-09-18: 82
- 2026-09-17: 82
- 2026-09-16: 81
- 2026-09-15: 81
- 2026-09-14: 80
- 2026-09-13: 80
- 2026-09-12: 80
- 2026-09-11: 79
- 2026-09-10: 79
- 2026-09-09: 78
- 2026-09-08: 72
- 2026-09-07: 72
- 2026-09-06: 71
- 2026-09-05: 71
- 2026-09-04: 70
- 2026-09-03: 70
- 2026-09-02: 69
- 2026-09-01: 66

## Common questions

### 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 84 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 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://anywaypossible.com/api/mcp
- Repository: https://github.com/anyway-possible/public-api
- Website: https://anywaypossible.com/
- Changelog RSS feed: https://verifymcp.io/servers/anyway-possible-agent-utilities/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/anyway-possible-agent-utilities/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/anyway-possible-agent-utilities/api-mcp