tools.schemasevery tool has an object input schema
fail
tools.annotationsno tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
fail
tools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: list_policy_requests (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_evaluation (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_audit_trail (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); …
pass
tools.token_costabout 1,681 tokens to load every tool
pass
tools.api_dumptools are not a one-to-one API dump
stability100 · weight 15
pass
stability.changes4 tool changes in 30 days
pass
stability.rug_pullno tool changed its meaning under the same name
dependenciesn/a · weight 15
n/a
deps.known_vulns, deps.mcp_sdk_version, deps.resolvabledeps.dev does not know [email protected]
14 tools, about 1,681 tokens to load them all · tool set e0a243bad824 · tools last changed 2026-11-02 · checked 2026-11-07 19:10 UTC
Tool changes
get_evaluationadded
Inspect the reservation/settlement state of an evaluation
release_evaluationadded
Release a reserved ALLOW budget when the payment failed or was abandoned. Requires the evaluation_id and reservation_token returned by evaluate_payment.
settle_evaluationadded
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.
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
Dependencies
[email protected]PyPIthis version is not known to the dependency resolver
Dependency graphs from deps.dev; advisories from OSV.dev, including the GitHub Advisory Database and the PyPI Advisory Database; all CC BY 4.0. The graph is what a clean install of this version resolves today; nothing was installed or run. How it is checked.
Endpoints
remote
auth
reachable
uptime 30d
p50
protocol
last ok
https://api.boundra.io/mcpstreamable-http
none
yes
100%
338 ms
2026-07-28
2026-11-07
package
registry
version
runtime
secrets
boundra-mcp
pypi
0.1.1
–
Tools (14)
evaluate_payment
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.
get_audit_trail
View recent payment-approval audit records for an owner
get_evaluation
Inspect the reservation/settlement state of an evaluation
get_policy
View the active signed payment policy for an owner (and optionally an agent scope)
get_policy_versions
View a user's policy version history (version chain + hashes, verifiable against on-chain commitments)
get_spend_report
View today's spend summary for an owner
list_policy_requests
List pending agent policy-change requests
list_templates
List policy templates (personal assistant / travel / dev API / procurement)
release_evaluation
Release a reserved ALLOW budget when the payment failed or was abandoned. Requires the evaluation_id and reservation_token returned by evaluate_payment.
render_template
Render a natural-language rule from a template + parameters (then compile, sign & publish)
request_policy_change
[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.
revoke_policy
[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.
set_policy
[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.
settle_evaluation
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.