Boundra — Payment Approval Gateway for AI Agents
REMOTE · API.BOUNDRA.IO · 2 COMPONENTS
Allow, ask, or veto — a policy decision point your agent consults before signing any payment
Available components
Last scanned (6 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 5 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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 14 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability59
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 919 tokens (~65/item across 14 items; 14 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.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; "revoke_policy" implies "revoke" 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 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
- Schema quality: 737 → 919 ▼ functional
- New tool “get_evaluation” functional
- New tool “release_evaluation” functional
- New tool “settle_evaluation” functional
- “evaluate_payment” added an optional parameter “method” cosmetic
- “evaluate_payment” added an optional parameter “network” cosmetic
- “evaluate_payment” added an optional parameter “resource” cosmetic
- “evaluate_payment” added an optional parameter “asset” cosmetic
- “evaluate_payment” added an optional parameter “expected_recipient” cosmetic
- 1 Nov 26 +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.
- 30 Oct 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.
- 28 Oct 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.
- 26 Oct 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.
- 24 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 23 Oct 26 57
First indexed and scored.
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 5 Nov 2026 · Probed https://api.boundra.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.boundra.io | CN=YE2,O=Let's Encrypt,C=US | 17 Oct 2026 | 15 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6b4c33b3369365647ea9aaf97648f21c391 |
| SANs: api.boundra.io | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.boundra.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| boundra.io. | absent | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.boundra.io/mcp | Verified | 200 | |
| http (plaintext) | http://api.boundra.io/mcp | HTTPS enforced | 301 | https://api.boundra.io/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 →
evaluate_payment ~155
Evaluate a payment intent. MUST be called before executing any payment. ALLOW = you may pay; DENY = you must abandon; ASK = a challenge is returned — relay the reason to the user, then retry with approval_token once the user signs. An optional mandate parameter carries a user-issued single-task authorization.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | – | – | – |
| amount | number | yes | – |
| approval_token | – | – | – |
| asset | – | – | – |
| expected_amount | – | – | – |
| expected_recipient | – | – | – |
| mandate | – | – | – |
| method | – | – | – |
| network | – | – | – |
| owner | – | – | – |
| purpose | string | yes | – |
| recipient | string | yes | – |
| resource | – | – | – |
| source_content | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_audit_trail ~36
View recent payment-approval audit records for an owner
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| owner | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_evaluation ~28
Inspect the reservation/settlement state of an evaluation
| Name | Type | Req | Description |
|---|---|---|---|
| evaluation_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_policy ~37
View the active signed payment policy for an owner (and optionally an agent scope)
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | – | – | – |
| owner | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_policy_versions ~35
View a user's policy version history (version chain + hashes, verifiable against on-chain commitments)
| Name | Type | Req | Description |
|---|---|---|---|
| owner | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_spend_report ~25
View today's spend summary for an owner
| Name | Type | Req | Description |
|---|---|---|---|
| owner | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_policy_requests ~16
List pending agent policy-change requests
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_templates ~22
List policy templates (personal assistant / travel / dev API / procurement)
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
release_evaluation ~51
Release a reserved ALLOW budget when the payment failed or was abandoned. Requires the evaluation_id and reservation_token returned by evaluate_payment.
| Name | Type | Req | Description |
|---|---|---|---|
| evaluation_id | string | yes | – |
| reservation_token | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
render_template ~59
Render a natural-language rule from a template + parameters (then compile, sign & publish)
| Name | Type | Req | Description |
|---|---|---|---|
| ask_above | – | – | – |
| daily | – | – | – |
| per_tx | – | – | – |
| template_id | string | yes | – |
| whitelist | array | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
request_policy_change ~84
[For agents] Ask the user for a policy/budget change (e.g. 'raise daily budget from 50 to 80'). The request is queued for user approval; the user signs and publishes a new policy version. Agents can NEVER change policy directly.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| reason | string | yes | – |
| request | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
revoke_policy ~85
[USER ONLY] Revoke a policy chain (takes effect immediately; subsequent payments default to DENY). Must carry the user's wallet signature over the revocation statement.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | – | – | – |
| created_at | number | yes | – |
| owner | string | yes | – |
| revoked_through | integer | yes | – |
| scope | string | yes | – |
| signature | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
set_policy ~108
[USER ONLY] Submit a new policy version. Must carry the user's wallet EIP-191 signature over the policy document; accepted only after signature + version-chain checks pass. Agents MUST NOT call this tool.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | – | – | – |
| created_at | number | yes | – |
| nl_rule | string | yes | – |
| owner | string | yes | – |
| prev_hash | string | yes | – |
| scope | string | yes | – |
| signature | string | yes | – |
| version | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
settle_evaluation ~76
Confirm that an ALLOWed payment settled. Requires the evaluation_id and the reservation_token returned by evaluate_payment, plus the real transaction/hash reference. Idempotent for the same evaluation; never call this before settlement.
| Name | Type | Req | Description |
|---|---|---|---|
| evaluation_id | string | yes | – |
| reservation_token | string | yes | – |
| settlement_ref | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the Boundra — Payment Approval Gateway for AI Agents MCP server?
Boundra — Payment Approval Gateway for AI Agents is a hosted endpoint at https://api.boundra.io/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 · api.boundra.io
claude mcp add --transport http io-boundra-boundra 'https://api.boundra.io/mcp'
What is the Boundra — Payment Approval Gateway for AI Agents MCP server?
Boundra — Payment Approval Gateway for AI Agents is an MCP server listed in the public MCP registry as io.boundra/boundra. Allow, ask, or veto, a policy decision point your agent consults before signing any payment. This page covers its hosted endpoint (https://api.boundra.io/mcp).
Is the Boundra — Payment Approval Gateway for AI Agents MCP server safe to use?
Boundra — Payment Approval Gateway for AI Agents scores 64 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 Boundra — Payment Approval Gateway for AI Agents MCP server expose?
Boundra — Payment Approval Gateway for AI Agents exposes 14 tools: evaluate_payment, settle_evaluation, release_evaluation, get_evaluation, request_policy_change, and 9 more. Their descriptions and schemas cost roughly 817 tokens of context every time the server is loaded.
Does the Boundra — Payment Approval Gateway for AI Agents MCP server require authentication?
No. We connected to Boundra — Payment Approval Gateway for AI Agents without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Boundra — Payment Approval Gateway for AI Agents MCP server still maintained?
Boundra — Payment Approval Gateway for AI Agents is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.