Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Protocol Banks

REMOTE · WWW.PROTOCOLBANKS.COM

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

+3 this week 73 Trust /100

Last scanned (13 hours ago)

Scores higher than 59% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability81
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1086 tokens (~43/item across 25 items; 23 tools + 2 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
  • Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 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. See how to fix → Fail
  • An AI judge read all 24 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
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation 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.

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 →

Changelog

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.

  • 20 Nov 26 +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.

  • 18 Nov 26 +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.

  • 16 Nov 26 +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.

  • 13 Nov 26 +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.

  • 12 Nov 26 +5
    • 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 security
    • Schema quality: 15 → 43 ▼ functional
    • 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” functional
  • 11 Nov 26 +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.

  • 9 Nov 26 +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.

  • 7 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
Diagnostics

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 21 Nov 2026 · Probed https://www.protocolbanks.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=www.protocolbanks.com CN=YR1,O=Let's Encrypt,C=US 24 Oct 2026 22 Jan 2027 RSA 2048 SHA256-RSA 5bcb55d5d552bca0285fb427a02673cb97f
SANs: www.protocolbanks.com
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.protocolbanks.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
protocolbanks.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'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://www.google.com https://www.gstatic.com https://cdn.unicorn.studio; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com https://cdn.unicorn.studio; img-src 'self' data: https: blob:; worker-src 'self' blob:; connect-src 'self' https://*.llamarpc.com https://*.infura.io https://*.alchemy.com wss://*.walletconnect.com https://*.walletconnect.com wss://*.walletconnect.org https://*.walletconnect.org https://*.reown.com wss://*.reown.com https://api.web3modal.com https://api.web3modal.org https://rpc.walletconnect.com https://api.rango.exchange https://*.trongrid.io https://*.etherscan.io https://eth.llamarpc.com https://rpc.sepolia.org https://polygon-rpc.com https://mainnet.optimism.io https://mainnet.base.org https://arb1.arbitrum.io https://bsc-dataseed.binance.org https://mainnet.hsk.xyz https://*.basescan.org https://*.arbiscan.io https://*.bscscan.com https://*.polygonscan.com htt
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=(self)

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.protocolbanks.com/api/mcp Verified 200
http (plaintext) http://www.protocolbanks.com/api/mcp HTTPS enforced 308 https://www.protocolbanks.com/api/mcp
MCP tools · 23 exposed · ~1,050 tokens

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 →

Tool Tokens
accept_commerce_quote ~33

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

NameTypeReqDescription
quoteIdstringyesQuote id.

No output schema declared.

No examples provided.

check_payment_status ~21

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

compare_chain_fees ~31

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

complete_commerce_order ~32

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

NameTypeReqDescription
orderIdstringyesOrder id.

No output schema declared.

No examples provided.

control_trading_agent ~154

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.

NameTypeReqDescription
actionstringyesThe control action: pause/resume/stop the agent, approve/reject a pending trade (manual approval mode), or set_approval to switch entry mode.
modestring–Required for set_approval: "auto" places entries automatically, "manual" holds each entry for approval.

No output schema declared.

No examples provided.

create_commerce_quote ~108

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

NameTypeReqDescription
amountUsdnumber–Optional negotiated amount.
buyerstringyesBuyer wallet address.
deliveryDuestring–Optional ISO delivery deadline.
expiresInSecondsinteger–Quote validity.
scopestringyesWhat will be delivered.
serviceIdstringyesService listing id.
termsobject–Optional refund, dispute and SLA terms.

No output schema declared.

No examples provided.

create_invoice ~28

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

create_payment ~34

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

deliver_commerce_order ~77

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

NameTypeReqDescription
deliveryHashstringyessha256 hash or 0x hash of the delivery.
deliverySignaturestring–Optional seller signature over the delivery proof.
deliveryUristring–Optional delivery location.
orderIdstringyesOrder id.

No output schema declared.

No examples provided.

estimate_gas ~25

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

execute_payment ~36

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_activity ~61

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

NameTypeReqDescription
limitinteger–Maximum number of activity items to return (default 10, max 50).

No output schema declared.

No examples provided.

get_agent_reputation ~34

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

NameTypeReqDescription
addressstringyesSeller wallet address.

No output schema declared.

No examples provided.

get_balance ~29

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_payment_quote ~34

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_positions ~42

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_track_record ~45

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_trading_overview ~64

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_agent_services ~52

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

NameTypeReqDescription
categorystring–Filter by category.
limitinteger–Maximum results.
qstring–Search the service name.

No output schema declared.

No examples provided.

list_commerce_orders ~32

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

NameTypeReqDescription
idstring–Optional order id.

No output schema declared.

No examples provided.

list_invoices ~19

List invoices for the authenticated wallet. Requires authentication.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_payments ~20

List recent payments for the authenticated wallet. Requires authentication.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_supported_tokens ~39

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

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.

remote · www.protocolbanks.com

# add to Claude Code
claude mcp add --transport http everest-an-protocol-banks 'https://www.protocolbanks.com/api/mcp'
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.