# Protocol Banks (remote · www.protocolbanks.com)

Control plane for agent commerce: orders, payments, cards and trading under one mandate.

- Trust score: 73/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `www.protocolbanks.com`: 73/100 (this document), [markdown](https://verifymcp.io/servers/everest-an-protocol-banks/api-mcp-2.md), [page](https://verifymcp.io/servers/everest-an-protocol-banks/api-mcp-2)

## Channel facts

- Endpoint: `https://www.protocolbanks.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.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-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 23 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - 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**: 81/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1086 tokens (~43/item across 25 items; 23 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 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.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "execute_payment" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 24 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 Protocol Banks MCP server?

Protocol Banks is a hosted endpoint at https://www.protocolbanks.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 everest-an-protocol-banks 'https://www.protocolbanks.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "everest-an-protocol-banks": {
      "url": "https://www.protocolbanks.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "everest-an-protocol-banks": {
      "type": "http",
      "url": "https://www.protocolbanks.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.everest-an-protocol-banks]
url = "https://www.protocolbanks.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "everest-an-protocol-banks": {
      "type": "remote",
      "url": "https://www.protocolbanks.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add everest-an-protocol-banks --url 'https://www.protocolbanks.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  everest-an-protocol-banks:
    url: "https://www.protocolbanks.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "everest-an-protocol-banks": {
      "Transport": "http",
      "Url": "https://www.protocolbanks.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add everest-an-protocol-banks -t streamable-http -u 'https://www.protocolbanks.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "everest-an-protocol-banks": {
      "type": "http",
      "url": "https://www.protocolbanks.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-11-20 (score 73, +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-11-18 (score 72, +1)

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

### 2026-11-16 (score 71, +1)

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

### 2026-11-13 (score 70, +1)

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

### 2026-11-12 (score 69, +5)

- [security] Tool “check_payment_status” rewrote its description, which is the text the model reads
- [security] Tool “compare_chain_fees” rewrote its description, which is the text the model reads
- [security] Tool “create_invoice” rewrote its description, which is the text the model reads
- [security] Tool “create_payment” rewrote its description, which is the text the model reads
- [security] Tool “estimate_gas” rewrote its description, which is the text the model reads
- [security] Tool “execute_payment” rewrote its description, which is the text the model reads
- [security] Tool “get_balance” rewrote its description, which is the text the model reads
- [security] Tool “get_payment_quote” rewrote its description, which is the text the model reads
- [security] Tool “list_invoices” rewrote its description, which is the text the model reads
- [security] Tool “list_payments” rewrote its description, which is the text the model reads
- [security] Tool “list_supported_tokens” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 15 → 43
- [functional improvement] MCP protocol: fail → pass
- [functional] First check of Tool coverage: 100
- [functional] Schema quality: fair → good
- [functional] MCP protocol version: 2024-11-05 → 2025-11-25
- [functional] New tool “accept_commerce_quote”
- [functional] New tool “complete_commerce_order”
- [functional] New tool “control_trading_agent”
- [functional] New tool “create_commerce_quote”
- [functional] New tool “deliver_commerce_order”
- [functional] New tool “get_activity”
- [functional] New tool “get_agent_reputation”
- [functional] New tool “get_positions”
- [functional] New tool “get_track_record”
- [functional] New tool “get_trading_overview”
- [functional] New tool “list_agent_services”
- [functional] New tool “list_commerce_orders”

### 2026-11-11 (score 64, +1)

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

### 2026-11-09 (score 63, +1)

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

### 2026-11-07 (score 62, +1)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (23)

### `list_supported_tokens` (~39 tokens)

List all supported tokens and networks for payments. Returns token symbols, contract addresses, decimals, and which networks they are available on. No authentication required.

### `get_payment_quote` (~34 tokens)

Get a fee estimate for a payment on a specific network. Returns the protocol fee percentage and estimated total. No authentication required.

### `estimate_gas` (~25 tokens)

Estimate gas cost for an ERC-20 stablecoin transfer. No authentication required.

### `compare_chain_fees` (~31 tokens)

Compare transfer fees across all supported chains for a token. Identifies the cheapest chain. No authentication required.

### `create_payment` (~34 tokens)

Create a new payment. Requires authentication. Creates a payment record in pending status. The actual on-chain transaction must be submitted separately.

### `check_payment_status` (~21 tokens)

Check the status of a payment by ID. Requires authentication.

### `list_payments` (~20 tokens)

List recent payments for the authenticated wallet. Requires authentication.

### `create_invoice` (~28 tokens)

Create a new invoice for receiving payments. Generates a payment link that can be shared. Requires authentication.

### `list_invoices` (~19 tokens)

List invoices for the authenticated wallet. Requires authentication.

### `get_balance` (~29 tokens)

Get token balances for the authenticated wallet across one or all networks. Returns cached balance data. Requires authentication.

### `execute_payment` (~36 tokens)

Create AND execute a stablecoin payment on-chain in one step. Requires authentication. Uses server-side executor key to sign and broadcast the transaction.

### `get_trading_overview` (~64 tokens)

Get AI trading overview

Get the AI trading cockpit state: agent status (running/paused/stopped), total equity, trading wallet, max loss, today/all-time PnL, open positions and the latest activity. Without a configured wallet this reads the guest demo account (paper mode).

### `get_positions` (~42 tokens)

Get open positions

List the AI agent's open positions with side, leverage, entry/mark price, size, unrealized PnL and the plain-language reason the position was opened.

### `get_activity` (~61 tokens)

Get AI activity feed

Read the AI agent's recent activity feed in plain language: market scans, position opens/closes (with PnL), and risk-guard events.

Input parameters:

- `limit` (integer): Maximum number of activity items to return (default 10, max 50).

### `get_track_record` (~45 tokens)

Get public live track record

Get the public, anonymized live track record: every live Protocol Bank account with its budget, realized PnL and trade count. No auth required — this is public data.

### `control_trading_agent` (~154 tokens)

Control the AI trading agent

Control the AI trading agent. Actions: "pause" (stop opening new trades, keep managing positions), "resume" (start scanning again), "stop" (emergency stop — halt everything), "approve"/"reject" (resolve a pending trade in manual approval mode), "set_approval" (+ mode: auto|manual — choose whether entries need your approval). Requires authentication.

Input parameters:

- `action` (string, required): The control action: pause/resume/stop the agent, approve/reject a pending trade (manual approval mode), or set_approval to switch entry mode.
- `mode` (string): Required for set_approval: "auto" places entries automatically, "manual" holds each entry for approval.

### `list_agent_services` (~52 tokens)

List public agent services with price, token, chain and category.

Input parameters:

- `category` (string): Filter by category.
- `limit` (integer): Maximum results.
- `q` (string): Search the service name.

### `get_agent_reputation` (~34 tokens)

Read a seller's completed, disputed and refunded order counts and volume.

Input parameters:

- `address` (string, required): Seller wallet address.

### `create_commerce_quote` (~108 tokens)

Seller: create a structured quote for a service. Returns a terms hash. Requires authentication.

Input parameters:

- `amountUsd` (number): Optional negotiated amount.
- `buyer` (string, required): Buyer wallet address.
- `deliveryDue` (string): Optional ISO delivery deadline.
- `expiresInSeconds` (integer): Quote validity.
- `scope` (string, required): What will be delivered.
- `serviceId` (string, required): Service listing id.
- `terms` (object): Optional refund, dispute and SLA terms.

### `accept_commerce_quote` (~33 tokens)

Buyer: accept a quote and create an order. Requires authentication.

Input parameters:

- `quoteId` (string, required): Quote id.

### `deliver_commerce_order` (~77 tokens)

Seller: record delivery proof for an order. Requires authentication.

Input parameters:

- `deliveryHash` (string, required): sha256 hash or 0x hash of the delivery.
- `deliverySignature` (string): Optional seller signature over the delivery proof.
- `deliveryUri` (string): Optional delivery location.
- `orderId` (string, required): Order id.

### `complete_commerce_order` (~32 tokens)

Buyer: confirm a paid, delivered order. Requires authentication.

Input parameters:

- `orderId` (string, required): Order id.

### `list_commerce_orders` (~32 tokens)

List commerce orders where the authenticated wallet is buyer or seller.

Input parameters:

- `id` (string): Optional order id.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/everest-an-protocol-banks/api-mcp-2#diagnostics

## Score history

- 2026-11-21: 73
- 2026-11-20: 73
- 2026-11-19: 72
- 2026-11-18: 72
- 2026-11-17: 71
- 2026-11-16: 71
- 2026-11-15: 70
- 2026-11-14: 70
- 2026-11-13: 70
- 2026-11-12: 69
- 2026-11-11: 64
- 2026-11-10: 63
- 2026-11-09: 63
- 2026-11-08: 62
- 2026-11-07: 62
- 2026-11-06: 61

## Common questions

### What is the Protocol Banks MCP server?

Protocol Banks is an MCP server listed in the public MCP registry as io.github.everest-an/protocol-banks. Control plane for agent commerce: orders, payments, cards and trading under one mandate. This page covers its hosted endpoint (https://www.protocolbanks.com/api/mcp).

### Is the Protocol Banks MCP server safe to use?

Protocol Banks scores 73 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 Protocol Banks MCP server expose?

Protocol Banks exposes 23 tools: list_supported_tokens, get_payment_quote, estimate_gas, compare_chain_fees, create_payment, and 18 more. Their descriptions and schemas cost roughly 1,050 tokens of context every time the server is loaded.

### Does the Protocol Banks MCP server require authentication?

No. We connected to Protocol Banks without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Protocol Banks MCP server still maintained?

Protocol Banks is still listed as active in the MCP registry. We last reached this channel on 21 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 Protocol Banks MCP server?

VerifyMCP ran 12 checks on Protocol Banks, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Protocol Banks: Authorization. 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.

## Links

- Remote endpoint: https://www.protocolbanks.com/api/mcp
- Changelog RSS feed: https://verifymcp.io/servers/everest-an-protocol-banks/api-mcp-2.xml
- Changelog JSON feed: https://verifymcp.io/servers/everest-an-protocol-banks/api-mcp-2/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/everest-an-protocol-banks/api-mcp-2.json
- HTML version of this page: https://verifymcp.io/servers/everest-an-protocol-banks/api-mcp-2
