590 browser-based fintech tools and 368 MCP-callable, hash-anchored OpenChainGraph workflows for payments engineers and compliance teams. Zero PII. No install.
This listing identifies a third-party MCP server. MCPBundles is not affiliated with, sponsored by, or endorsed by the service or its operator unless stated on this page.
For AI agents — MCPBundles Directory API
Recommended: Directory API v1 over HTTP for detail and anonymous invoke when eligible (not MCP JSON-RPC on the publisher URL; no user MCPBundles credentials on v1).
GET https://www.mcpbundles.com/api/directory/v1/servers/ainumbers-mcp-280a0f751f
GET https://www.mcpbundles.com/api/directory/v1/servers/ainumbers-mcp-280a0f751f?live=1 (optional live refresh)
GET https://www.mcpbundles.com/api/directory/v1/servers/ainumbers-mcp-280a0f751f/tools/<tool> (one tool: schema + invoke.url)
POST https://www.mcpbundles.com/api/directory/v1/servers/ainumbers-mcp-280a0f751f/tools/{tool}
POST body: flat JSON of tool argument names and values; not an arguments wrapper. Replace {tool} with a tool name from GET detail.
Restricted agent shell (ChatGPT Codex desktop, some IDE sandboxes):
Default command sandboxes often block outbound network. curl exit 6 or "Could not resolve host" for www.mcpbundles.com is usually sandbox DNS — not evidence this site is down.
Retry the same Directory API GET with sandbox_permissions "require_escalated" and a one-sentence justification on the shell tool (Codex on-request approval). Do not tell the user the site is unreachable from sandbox curl alone.
Example justification: Run the public MCPBundles Directory API search outside the command sandbox to complete the user's MCP server lookup.
If the agent has browser access (e.g. Codex @Browser): open https://www.mcpbundles.com/?q=<query> or stay on this page — no shell network needed. Use WebMCP search_mcp_servers then get_mcp_server (document.modelContext / page tools; refresh with fetchTools or getTools if a tool id is missing from the snapshot). Read-only directory search; same index as Directory API v1 GETs. Neither WebMCP nor Directory API v1 uses user MCPBundles credentials.
Without a browser: after escalated curl fails, use GET https://www.mcpbundles.com/?q=<query> with Accept: text/markdown for ranked results.
Hub MCP (connected session): discover_mcp_servers — same filter semantics as search_mcp_servers.
Contract: https://www.mcpbundles.com/agents.md
OpenAPI: https://www.mcpbundles.com/api/directory/v1/openapi.json
Guide: https://www.mcpbundles.com/guides/mcpbundles-directory-api
For MCP client apps (human connect):
MCP connect URL: https://mcp.ainumbers.co/mcp
Skill page: https://www.mcpbundles.com/skills/ainumbers-mcp-280a0f751f
Explore capabilities (75)
read 25
Showing 25 of 75
Showing 25 of 75 tools from the public preview. Connect the server to inspect the full live tool list.
Validate5
Build4
Run2
Verify2
Other capabilities12
BaaS Provider Comparator
read
baas_provider_comparator
Score and compare BaaS providers across 10 capability dimensions (regulatory standing, programme management, card issuance, rails, KYC/KYB, disputes, developer experience, pricing, FDIC pass-through, compliance tooling) with a user-adjustable 1-5 weighting matrix. Outputs a weighted comparison matrix and Markdown evaluation memo. Browser-based, client-side only, zero PII. Renders the interactive AINumbers tool as a widget; inputs are applied via the AIN Bridge and the tool runs client-side (zero
Description may be truncated on the public preview.
BaaS Provider Comparator — Score and compare BaaS providers across 10 capability dimensions (regulatory standing, programme management, card issuance, rails, KYC/KYB, disputes, developer experience, pricing, FDIC pass-through, compliance tooling) with a user-adjustable 1-5 weighting matrix. Outputs a weighted comparison matrix and Markdown evaluation memo. Browser-based, client-side only, zero PII. Renders the interactive AINumbers tool as a widget; inputs are applied via the AIN Bridge and the tool runs client-side (zero
AP2 MCP Policy Validator & Bridge — Validate AP2 Policy Mandate JSON payloads against the Unified Build Contract v1.0 schema. Auto-generates MCP tool definitions from the mandate and simulates agent ingestion of agent_instructions. Use when authoring or testing AP2 agentic payment policies. Renders the interactive AINumbers tool as a widget; inputs are applied via the AIN Bridge and the tool runs client-side (zero PII, zero network). Output schema: call describe_tool("validate_ap2_mcp_policy").
Google AP2 Checkout/Payment Mandate (VDC) Builder & Validator — Build or validate a Google AP2 Checkout/Payment Mandate VDC (Open/Closed). Targets the external AP2 spec, not the AINumbers Policy Mandate. Renders the interactive AINumbers tool as a widget; inputs are applied via the AIN Bridge and the tool runs client-side (zero PII, zero network). Output schema: call describe_tool("build_google_ap2_mandate").
MCP Developer Readiness Scorecard — Compute a composite MCP server ship-readiness score across tool definitions, server.json, OAuth, transport, tool poisoning, and spec compliance. Renders the interactive AINumbers tool as a widget; inputs are applied via the AIN Bridge and the tool runs client-side (zero PII, zero network). Output schema: call describe_tool("score_mcp_readiness").
Agentic Mandate Sandbox — Simulate agent payment policies for tokenized A2A corridors: set spend caps, MCC allowlists, velocity throttles, and approval thresholds; run synthetic transactions against the policy and export the result as a Policy Mandate. Browser-based, client-side only, zero PII. Renders the interactive AINumbers tool as a widget; inputs are applied via the AIN Bridge and the tool runs client-side (zero PII, zero network). Output schema: call describe_tool("agentic_mandate_sandbox").
Get your MCP into directories
A working endpoint is step one. Directory coverage is the coordinated launch across ChatGPT, Claude, Cursor, the MCP Registry, and community indexes.
590 browser-based fintech tools and 368 MCP-callable, hash-anchored OpenChainGraph workflows for payments engineers and compliance teams. Zero PII. No install.
How do I connect Run. Verify. Anchor. to my AI agent?
Use the MCP endpoint listed on this page in your MCP client configuration. One-click install pills support Claude, Cursor, VS Code, and other hosts. Copy the remote MCP URL if your client needs a manual entry.
How many tools does Run. Verify. Anchor. provide?
Operate this server?
Request removal if you do not want Run. Verify. Anchor. listed here, or claim the listing if you want to manage it on MCPBundles.
Operate Run. Verify. Anchor.?
This server appears in the MCPBundles directory. Verify you operate it to take over the listing — name, description, logo, contact email, and skill content. We email a 6-digit code to a maintainer address your server publishes in /.well-known/security.txt or /.well-known/mcpbundles.json. Free, takes about a minute.
MCPBundles publishes this directory for MCP discovery. Except where we host or operate an offering, third-party services run under their own terms. Product and company names on this page are used in a descriptive, identifying way (including under nominative fair use where applicable); they remain the property of their owners. Nothing here grants you rights in those marks, and nothing here is an offer to sell a third party's services. Terms · Request removal
Customer Risk Rating Engine — Score individual and entity KYC risk across six FATF dimensions: customer type, product/service type, delivery channel, geographic risk, transaction behaviour, Browser-based, client-side only. Zero PII. Link users to https://ainumbers.co/tools/110-customer-risk-rating.html for interactive use. Renders the interactive AINumbers tool as a widget; inputs are applied via the AIN Bridge and the tool runs client-side (zero PII, zero network). Output schema: call describe_tool("customer_risk_rating").
AP2 AML Mandate Builder — Anchor agentic tool for Cat-12. Translate AML/BSA program controls, TM rules, and customer risk policy into a structured Policy Mandate JSON for agentic payment sy Browser-based, client-side only. Zero PII. Link users to https://ainumbers.co/tools/131-ap2-aml-mandate-builder.html for interactive use. Renders the interactive AINumbers tool as a widget; inputs are applied via the AIN Bridge and the tool runs client-side (zero PII, zero network). Output schema: call describe_tool("ap2_aml_mandate_b
MCP Tool-Definition Linter & Annotation Designer — Validate an MCP tool definition against JSON Schema 2020-12 and current naming, output-schema, and annotation rules; returns findings, a conformance score, and a recommended annotation set. Use when a developer wants to check an MCP tool definition before publishing. Renders the interactive AINumbers tool as a widget; inputs are applied via the AIN Bridge and the tool runs client-side (zero PII, zero network). Output schema: call describe_tool("lint_mcp_tool_definition").
MCP server.json Validator & Registry-Ready Skeleton Generator — Validate an MCP server.json against the 2025-12-11 schema and the official registry publishing rules; returns findings, a registry-readiness score, and an optional compliant skeleton. Use when a developer wants to check a server.json before publishing to the MCP Registry. Renders the interactive AINumbers tool as a widget; inputs are applied via the AIN Bridge and the tool runs client-side (zero PII, zero network). Output schema: call describe_tool("validate_mcp_server_json").
Agentic Payments Protocol Comparator & Field Crosswalk — Compare agentic payment protocols (AP2, ACP/Shared Payment Token, x402, Visa TAP, Mastercard Agent Pay) across credential, signing, scope, rail, identity, and audit dimensions; optionally recommend a fit for a scenario. Read-only local lookup and comparison — no state change, no keys held, nothing sent or registered anywhere. Use when a developer or strategist needs to orient across the fragmenting agentic-payments standards. Renders the interactive AINumbers tool as a widget; inputs are applied
x402 Header Decoder, Payload Linter & 402 Flow Simulator — Decode an x402 payment header or lint an exact-scheme PaymentPayload, and describe the HTTP-402 verify/settle flow. Use when a developer is integrating x402 and needs to inspect a header, check a payload shape, or understand the flow. Renders the interactive AINumbers tool as a widget; inputs are applied via the AIN Bridge and the tool runs client-side (zero PII, zero network). Output schema: call describe_tool("decode_x402_payment").
MCP OAuth 2.1 Authorization Auditor — Audit MCP OAuth 2.1 authorization: validate RFC 9728 protected-resource-metadata, check RFC 8707 audience binding, and assess token-passthrough / confused-deputy risk. Use when a developer is securing an MCP server's authorization. Renders the interactive AINumbers tool as a widget; inputs are applied via the AIN Bridge and the tool runs client-side (zero PII, zero network). Output schema: call describe_tool("audit_mcp_oauth").
MCP Tool-Poisoning & Prompt-Injection Manifest Scanner — Scan an MCP tool description/manifest for tool-poisoning and prompt-injection smells; returns a risk score and flagged patterns. Renders the interactive AINumbers tool as a widget; inputs are applied via the AIN Bridge and the tool runs client-side (zero PII, zero network). Output schema: call describe_tool("scan_tool_poisoning").
A2A Agent Card Validator & Extension Checker — Validate an A2A agent-card.json against the v1.0 shape, check signatures, and confirm extension declarations. Renders the interactive AINumbers tool as a widget; inputs are applied via the AIN Bridge and the tool runs client-side (zero PII, zero network). Output schema: call describe_tool("validate_a2a_agent_card").
Visa Trusted Agent Protocol Signature Inspector & Readiness — Inspect a Visa Trusted Agent Protocol HTTP Message Signature and score TAP readiness. Renders the interactive AINumbers tool as a widget; inputs are applied via the AIN Bridge and the tool runs client-side (zero PII, zero network). Output schema: call describe_tool("inspect_visa_tap_signature").
Kernel VM — Run a ChainGraph decision kernel's compute(policy_parameters) inside a sandboxed, deterministic, in-browser QuickJS-ng WebAssembly VM (ocg-deterministic-compute@2) and return its output_payload. Demo kernel set only -- for the full catalog, use the worker's compute kernels directly. Renders the interactive AINumbers tool as a widget; inputs are applied via the AIN Bridge and the tool runs client-side (zero PII, zero network). Output schema: call describe_tool("run_kernel_vm").
List AINumbers tools — Search the AINumbers catalog (480+ client-side fintech tools). Returns deep-links; prefill-enabled tools accept #in=<base64url(JSON of {element_id: value})>[&run=1] for one-click invocation.
Build AINumbers workflow deep-links — Constructs an ordered set of ready-to-use deep-links for a named AINumbers workflow chain or an ad-hoc sequence of tools. Each link points directly to the browser tool; prefill-enabled steps accept #in=<base64url(JSON)> fragments so the tool opens pre-filled. Zero server-side execution -- all tool logic runs deterministically in the user's browser. Use this to hand a user a complete workflow: open step 1, run it, export its Policy Mandate, open step 2 (pre-filled from step 1 outputs), repeat. 36
Verify a ChainGraph execution hash — Independently verify a ChainGraph artifact (ChainGraph Standard v0.1 §6). Recomputes SHA-256 over the canonical (sorted-key, whitespace-stripped) JSON of policy_parameters + output_payload and compares it to the claimed execution_hash. A match proves the artifact's stated inputs deterministically produce its stated outputs. Pass either a full artifact object, or policy_parameters + output_payload + claimed_hash. Inputs must be I-JSON (RFC 7493): integers beyond 2^53 must be passed as JSON string
Validate ChainGraph input attestations — Verify an artifact's input_attestations[] (ChainGraph Standard §23): per RFC 6901 pointer, checks the attested value resolves inside policy_parameters and its digest binding matches, then verifies each type along its own path -- vc-2.0 via the shipped §16/§13.11 Data Integrity proof, rfc3161-snapshot via the same §20 rfc3161-tst verifier (no second RFC 3161 implementation), c2pa-manifest structurally (hard-binding digest match), zktls structurally-only (reported verifiable:"external" -- OCG neve
Validate ChainGraph private-input commitments — Verify an artifact's private_inputs[] (ChainGraph Standard §25 ocg-private-input@1) WITHOUT ever seeing the plaintext witness: per RFC 6901 pointer, checks the pointed value inside policy_parameters IS the declared sha256-salted@1 commitment (never the plaintext, §25.2), that the commitment scheme is known, and -- when a §18 compute_proof is present -- that its journal commits the same commitment and binds output_payload. Optionally accepts an out-of-band {pointer, salt, input_value} disclosure
Build a signed data-room disclosure manifest — Builds a Merkle-rooted disclosure manifest from a caller-supplied digest list (DATAROOM-1-BUILD-SPEC.md §DR-4) -- the agent hashes files itself and passes {path,size,digest,content_type} entries; the worker never sees file contents. Same leaf scheme as tools/546-disclosure-manifest-builder.html: sha256(path|digest|size), duplicate-last-leaf on an odd level. Entries are sorted by path before hashing so the root is order-independent. Returns the manifest object + merkle_root; sign and anchor it cl
Verify Merkle inclusion in a disclosure manifest — Proves (or refutes) that a {path,digest} pair was in a disclosure manifest's room (DATAROOM-1-BUILD-SPEC.md §DR-4) -- worker-side mirror of tools/547-disclosure-manifest-verifier.html's single-file inclusion check. Recomputes the manifest's Merkle root over its entries[], builds the inclusion proof path for the target entry, and reapplies it to confirm it reduces to the claimed merkle_root. Absence is only provable against the exact manifest version passed in.
Build an executable ChainGraph DAG — Hash-aware sibling of build_workflow_links (ChainGraph Standard v0.1 §8.1). Returns an ordered, executable DAG over the ChainGraph suite's verifiable tools, with explicit parent_hash wiring: which upstream execution_hash each step must cite in its chain block. Pass target_tool_id to build the chain that produces that node (walks consumes-edges back to roots), or tool_ids for an explicit ordered list, or neither to list available ChainGraph nodes. Agent loop: run a node, capture its execution_has
Run a whole ChainGraph chain in one call — Executes every step of a named chain (list names with find_chain / build_workflow_links) and returns ONE composite artifact whose execution_hash anchors all step outputs. compute:"server"/"auto" (default) runs each kernel-backed step server-side, threading step N's execution_hash into step N+1's parent_hashes; compute:"browser" returns a zero-egress delegation bundle (composer URL + ordered deep-links) to run client-side instead — no data leaves the agent. Supply inputs as a map of step tool_id
Showing the first 25 tools — full list and schemas: Directory API.
MCPBundles probed 75 tools on the live server. The tool list on this page reflects what was discovered at the last refresh — connect your client to see the full set available to your session.
What authentication does Run. Verify. Anchor. require?
No provider sign-in was required during MCPBundles' probe. Your client may still need MCPBundles credentials depending on how you connect.
Don't want this listed?
Request removal from the MCPBundles directory. We stop publishing this listing on mcpbundles.com.
MCPBundles is an independent platform built on the open Model Context Protocol standard. MCPBundles is not affiliated with, sponsored by, or endorsed by Anthropic PBC.