{"apiVersion":"v1","directorySlug":"ainumbers-mcp-280a0f751f","title":"Run. Verify. Anchor.","description":"590 browser-based fintech tools and 368 MCP-callable, hash-anchored OpenChainGraph workflows for payments engineers and compliance teams. Zero PII. No install.","pageUrl":"https://www.mcpbundles.com/skills/ainumbers-mcp-280a0f751f","connectPath":"importable","connectAction":"import_server","catalogListing":false,"bundleSlug":null,"listingKind":"remote_mcp","kind":"provider","transportUrl":"https://mcp.ainumbers.co/mcp","hostedMcpUrl":null,"toolCount":75,"toolInventoryStatus":"observed","refreshedAt":"2026-11-03T13:26:00.516172+00:00","registryName":"co.ainumbers/ainumbers-mcp-280a0f751f","registryVersion":"2026.11.3","registryEligible":true,"tools":[{"name":"baas_provider_comparator","description":"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","inputSchema":{"type":"object","properties":{}},"title":"BaaS Provider Comparator","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"baas_provider_comparator","displayName":"BaaS Provider Comparator"},{"name":"validate_ap2_mcp_policy","description":"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\").","inputSchema":{"type":"object","properties":{}},"title":"AP2 MCP Policy Validator & Bridge","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"validate_ap2_mcp_policy","displayName":"AP2 MCP Policy Validator & Bridge"},{"name":"build_google_ap2_mandate","description":"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\").","inputSchema":{"type":"object","properties":{}},"title":"Google AP2 Checkout/Payment Mandate (VDC) Builder & Validator","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"build_google_ap2_mandate","displayName":"Google AP2 Checkout/Payment Mandate (VDC) Builder & Validator"},{"name":"score_mcp_readiness","description":"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\").","inputSchema":{"type":"object","properties":{}},"title":"MCP Developer Readiness Scorecard","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"score_mcp_readiness","displayName":"MCP Developer Readiness Scorecard"},{"name":"agentic_mandate_sandbox","description":"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\").","inputSchema":{"type":"object","properties":{}},"title":"Agentic Mandate Sandbox","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"agentic_mandate_sandbox","displayName":"Agentic Mandate Sandbox"},{"name":"customer_risk_rating","description":"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\").","inputSchema":{"type":"object","properties":{}},"title":"Customer Risk Rating Engine","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"customer_risk_rating","displayName":"Customer Risk Rating Engine"},{"name":"ap2_aml_mandate_builder","description":"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","inputSchema":{"type":"object","properties":{}},"title":"AP2 AML Mandate Builder","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"ap2_aml_mandate_builder","displayName":"AP2 AML Mandate Builder"},{"name":"lint_mcp_tool_definition","description":"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\").","inputSchema":{"type":"object","properties":{}},"title":"MCP Tool-Definition Linter & Annotation Designer","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"lint_mcp_tool_definition","displayName":"MCP Tool-Definition Linter & Annotation Designer"},{"name":"validate_mcp_server_json","description":"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\").","inputSchema":{"type":"object","properties":{}},"title":"MCP server.json Validator & Registry-Ready Skeleton Generator","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"validate_mcp_server_json","displayName":"MCP server.json Validator & Registry-Ready Skeleton Generator"},{"name":"compare_agentic_payment_protocols","description":"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","inputSchema":{"type":"object","properties":{}},"title":"Agentic Payments Protocol Comparator & Field Crosswalk","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"compare_agentic_payment_protocols","displayName":"Agentic Payments Protocol Comparator & Field Crosswalk"},{"name":"decode_x402_payment","description":"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\").","inputSchema":{"type":"object","properties":{}},"title":"x402 Header Decoder, Payload Linter & 402 Flow Simulator","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"decode_x402_payment","displayName":"x402 Header Decoder, Payload Linter & 402 Flow Simulator"},{"name":"audit_mcp_oauth","description":"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\").","inputSchema":{"type":"object","properties":{}},"title":"MCP OAuth 2.1 Authorization Auditor","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"audit_mcp_oauth","displayName":"MCP OAuth 2.1 Authorization Auditor"},{"name":"scan_tool_poisoning","description":"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\").","inputSchema":{"type":"object","properties":{}},"title":"MCP Tool-Poisoning & Prompt-Injection Manifest Scanner","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"scan_tool_poisoning","displayName":"MCP Tool-Poisoning & Prompt-Injection Manifest Scanner"},{"name":"validate_a2a_agent_card","description":"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\").","inputSchema":{"type":"object","properties":{}},"title":"A2A Agent Card Validator & Extension Checker","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"validate_a2a_agent_card","displayName":"A2A Agent Card Validator & Extension Checker"},{"name":"inspect_visa_tap_signature","description":"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\").","inputSchema":{"type":"object","properties":{}},"title":"Visa Trusted Agent Protocol Signature Inspector & Readiness","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"inspect_visa_tap_signature","displayName":"Visa Trusted Agent Protocol Signature Inspector & Readiness"},{"name":"run_kernel_vm","description":"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\").","inputSchema":{"type":"object","properties":{}},"title":"Kernel VM","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"run_kernel_vm","displayName":"Kernel VM"},{"name":"list_ainumbers_tools","description":"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.","inputSchema":{"type":"object","properties":{}},"title":"List AINumbers tools","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"list_ainumbers_tools","displayName":"List AINumbers tools"},{"name":"build_workflow_links","description":"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","inputSchema":{"type":"object","properties":{}},"title":"Build AINumbers workflow deep-links","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"build_workflow_links","displayName":"Build AINumbers workflow deep-links"},{"name":"verify_execution_hash","description":"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","inputSchema":{"type":"object","properties":{}},"title":"Verify a ChainGraph execution hash","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"verify_execution_hash","displayName":"Verify a ChainGraph execution hash"},{"name":"validate_input_attestations","description":"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","inputSchema":{"type":"object","properties":{}},"title":"Validate ChainGraph input attestations","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"validate_input_attestations","displayName":"Validate ChainGraph input attestations"},{"name":"validate_private_inputs","description":"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","inputSchema":{"type":"object","properties":{}},"title":"Validate ChainGraph private-input commitments","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"validate_private_inputs","displayName":"Validate ChainGraph private-input commitments"},{"name":"build_disclosure_manifest","description":"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","inputSchema":{"type":"object","properties":{}},"title":"Build a signed data-room disclosure manifest","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"build_disclosure_manifest","displayName":"Build a signed data-room disclosure manifest"},{"name":"verify_disclosure_inclusion","description":"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.","inputSchema":{"type":"object","properties":{}},"title":"Verify Merkle inclusion in a disclosure manifest","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"verify_disclosure_inclusion","displayName":"Verify Merkle inclusion in a disclosure manifest"},{"name":"build_chaingraph","description":"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","inputSchema":{"type":"object","properties":{}},"title":"Build an executable ChainGraph DAG","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"build_chaingraph","displayName":"Build an executable ChainGraph DAG"},{"name":"run_chain","description":"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","inputSchema":{"type":"object","properties":{}},"title":"Run a whole ChainGraph chain in one call","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"run_chain","displayName":"Run a whole ChainGraph chain in one call"},{"name":"run_chain_batch","description":"Batch over named chains in ONE round-trip with a PER-ROW terminal status — one row's failure never fails another, and every row's result rides the single response. mode:\"run\" (default) executes each row through the same engine as run_chain (composite artifact + execution_hash per row, deterministic); mode:\"estimate\" validates every row (chain exists, step counts, compute feasibility, inputs coverage, OCG §21.4 gate rule previews) WITHOUT executing anything. Capped at 8 rows and 11 total server-k","inputSchema":{"type":"object","properties":{}},"title":"Run or estimate several ChainGraph chains in one call","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"run_chain_batch","displayName":"Run or estimate several ChainGraph chains in one call"},{"name":"emit_chaingraph_artifact","description":"Makes ChainGraph tools agent-callable (ChainGraph Standard v0.1 §3.1). Mode 1 — supply pre_computed_artifact (exported from the browser tool): validates §4 schema fields, recomputes execution_hash via SHA-256 over canonical {policy_parameters, output_payload}, returns verified structuredContent. Mode 2 — supply tool_id + policy_parameters: returns an artifact template envelope and browser prefill URL so an agent can hand the user a pre-filled link; GPU sims always delegate to the browser per §9.","inputSchema":{"type":"object","properties":{}},"title":"Emit a ChainGraph artifact envelope","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"emit_chaingraph_artifact","displayName":"Emit a ChainGraph artifact envelope"},{"name":"build_session_receipt","description":"Aggregates execution_hashes from N ChainGraph tool calls in one agent session into a single SHA-256 Merkle root (session_receipt_root). Returns a tamper-evident session receipt and a regulator-framed PTG-01 audit prompt. One receipt covers an entire agent session: supply all execution_hashes in call order. The Merkle root is deterministic — the same hashes in the same order always produce the same root. Compliant with EU AI Act Art. 12 (transparency) and DORA ICT audit-trail requirements.","inputSchema":{"type":"object","properties":{}},"title":"Build a session audit receipt (Merkle root)","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"build_session_receipt","displayName":"Build a session audit receipt (Merkle root)"},{"name":"suggest_tool_idea","description":"Builds a prefilled GitHub Issue-Forms URL for proposing a new AINumbers fintech tool, OpenChainGraph compute node, or verifiable workflow. Returns the URL only -- it never posts to GitHub on the caller's behalf. Companion to the site's mailto suggestion form (suggest.html); this is the agent-callable path.","inputSchema":{"type":"object","properties":{}},"title":"Suggest a new tool, node, or workflow","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"suggest_tool_idea","displayName":"Suggest a new tool, node, or workflow"},{"name":"export_artifact","description":"Render a verified OpenChainGraph v0.4 artifact into a chaingraph_export profile (OCG Standard §13). Generated downstream of and EXCLUDED from the execution_hash preimage — the export is a view, not a fact; verification always routes back to the canonical JSON artifact. Pass the FULL artifact you received from a compute tool (the server is stateless — there is no hash cache). Formats: xlsx, csv, pdf, xbrl (xbrl_taxonomy=\"ocg-ext\" works now; eba-corep-* return a pending error until their concept m","inputSchema":{"type":"object","properties":{}},"title":"Export a ChainGraph artifact as xlsx / pdf / csv / xbrl / vc","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"export_artifact","displayName":"Export a ChainGraph artifact as xlsx / pdf / csv / xbrl / vc"},{"name":"find_chain","description":"BM25 search over all 368 AINumbers ChainGraph chains. Returns ranked chains with their full recipe: ordered node sequence, deep-links, composer URL, and entry tool mcp_name. Agent flow: find_chain(query) → read recipe → call the listed node MCP tools in order, passing parent_hashes between steps. Task-shaped queries work well: \"reserve composition recompute\", \"FR 2052a classification\", \"CCP margin replication\", \"SR 26-2 model validation benchmark\", \"litigation damages recompute\", \"evidence pack","inputSchema":{"type":"object","properties":{}},"title":"Find ChainGraph workflow chain","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"find_chain","displayName":"Find ChainGraph workflow chain"},{"name":"find_tool","description":"BM25 search over all 662 live AINumbers ChainGraph node tools. Returns ranked tools with mcp_name, URL, mandate type, and wave. Use to locate a specific computation node (e.g. \"FRTB expected shortfall\", \"MiCA own funds\", \"XVA calculator\", \"reserve composition\", \"2052a\", \"initial margin\", \"model validation benchmark\", \"TVM / damages calculator\") before calling it. Complements find_chain (chain-level) and list_ainumbers_tools (catalog-level).","inputSchema":{"type":"object","properties":{}},"title":"Find ChainGraph node tool","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"find_tool","displayName":"Find ChainGraph node tool"},{"name":"describe_tool","description":"Returns the full definition of exactly one AINumbers MCP tool: name, description, inputSchema, outputSchema (the JSON Schema its structuredContent validates against), annotations, and lifecycle_status. Use it after find_tool or find_chain hands you an mcp_name, or after tools/list whose entries omit outputSchema to keep the catalog reply small — the pointer sentence \"Output schema: call describe_tool(\\\"<name>\\\").\" marks exactly those tools. One call, no side effects, zero network on the server:","inputSchema":{"type":"object","properties":{}},"title":"Describe one AINumbers tool","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"describe_tool","displayName":"Describe one AINumbers tool"},{"name":"suite_howto","description":"How to chain AINumbers tools into audited workflows: call with NO recipe_id for the compact recipe index, or with one recipe_id for that workflow's full step-by-step recipe. Every recipe carries the suite conventions end to end: Policy Mandate exports, execution_hash verification, and receipts.","inputSchema":{"type":"object","properties":{}},"title":"AINumbers suite how-to: workflow recipes","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"suite_howto","displayName":"AINumbers suite how-to: workflow recipes"},{"name":"vc_issue","description":"Composes and signs a W3C Verifiable Credential 2.0 with an eddsa-jcs-2022 Data Integrity proof over a fresh ephemeral did:key (generated per call, not reused). Returns the signed credential, an OCG Standard §23 vc-2.0 input-attestation block ready to embed in a ChainGraph chain's policy_parameters at the given pointer, and an OCG receipt of the issuance activity. The signature proves the claims were not altered after signing and that the did:key holder produced it -- it is not, by itself, identi","inputSchema":{"type":"object","properties":{}},"title":"Issue a signed W3C Verifiable Credential 2.0","logicalName":"vc_issue","displayName":"Issue a signed W3C Verifiable Credential 2.0","annotations":{"untrustedContentHint":true,"readOnlyHint":true}},{"name":"sdjwt_issue","description":"Issues a Selective Disclosure JWT (RFC 9901) from a claims object, marking selected top-level claim keys as selectively disclosable via salted-hash digests in the _sd array. Signed EdDSA over a fresh ephemeral did:key (generated per call, not reused). Pair with sdjwt_present to build a redacted presentation from the returned sd_jwt.","inputSchema":{"type":"object","properties":{}},"title":"Issue a Selective Disclosure JWT (RFC 9901)","logicalName":"sdjwt_issue","displayName":"Issue a Selective Disclosure JWT (RFC 9901)","annotations":{"untrustedContentHint":true,"readOnlyHint":true}},{"name":"sdjwt_present","description":"Builds a redacted presentation from an existing SD-JWT (as returned by sdjwt_issue), keeping only the listed disclosures. Pass aud to add a KB-JWT holder-binding (a fresh ephemeral holder key is generated per call). Pass issuer_did (the sd_jwt's \"issuer\" field) to also verify the JWS and return the verifier_view -- exactly the claim set a relying party would resolve -- plus an OCG receipt of the presentation activity.","inputSchema":{"type":"object","properties":{}},"title":"Present a redacted Selective Disclosure JWT","logicalName":"sdjwt_present","displayName":"Present a redacted Selective Disclosure JWT","annotations":{"untrustedContentHint":true,"readOnlyHint":true}},{"name":"checklist_validate_definition","description":"Validates a checklist or SOP definition JSON against the CHECKRUN-1 schema (definition_id, title, semver version, non-empty steps[] each with step_id/title/instruction/evidence_requirement (none|text|file-digest|attestation)/gate (blocking|advisory)). Returns valid:true/false plus a field-by-field error list. Pair with checklist_step_receipt to run the definition headlessly.","inputSchema":{"type":"object","properties":{}},"title":"Validate a checklist/SOP definition","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"checklist_validate_definition","displayName":"Validate a checklist/SOP definition"},{"name":"checklist_step_receipt","description":"Completes ONE step of a checklist/SOP run and returns its OCG v0.4 step receipt: execution_hash chains to prev_step_receipt_digest (pass the previous step's execution_hash, or omit for step 0). A blocking-gate step with evidence_requirement != \"none\" and no evidence supplied is refused (the caller enforces step order; this tool enforces the evidence requirement per step). Call once per step in order, then pass the full ordered list of returned receipts to checklist_verify_run to check the chain","inputSchema":{"type":"object","properties":{}},"title":"Mint a hash-chained checklist step receipt","logicalName":"checklist_step_receipt","displayName":"Mint a hash-chained checklist step receipt","annotations":{"untrustedContentHint":true,"readOnlyHint":true}},{"name":"checklist_verify_run","description":"Recomputes and checks a checklist run: every step receipt's execution_hash, the hash-chain link between consecutive steps, and (if a run_receipt is supplied) the §20.1 RFC 6962 Merkle root over every step. Returns valid:true/false, per-step ok/hash_ok/link_ok, and broken_at (the zero-based index of the first broken step, or null). Same recompute a human gets from the browser Run Verifier.","inputSchema":{"type":"object","properties":{}},"title":"Verify a checklist run's hash chain and Merkle root","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"checklist_verify_run","displayName":"Verify a checklist run's hash chain and Merkle root"},{"name":"ha_record_validate","description":"Structural (non-cryptographic) §27.2 signed-named-human check: does this record carry a §16 whole-artifact proof (eddsa-jcs-2022) whose verificationMethod is bound to the record's own identity.id? Does NOT verify the signature bytes -- pair with verify_execution_hash / a proof verifier for that. Use before counting a record toward ha_gate_status.","inputSchema":{"type":"object","properties":{}},"title":"Validate a §27 human-accountability record","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"ha_record_validate","displayName":"Validate a §27 human-accountability record"},{"name":"ha_gate_status","description":"Given a step's haGatePolicy and the human_accountability_records[] collected for a subject, returns whether the gate is satisfied, held, rejected, escalated, or overridden -- same algorithm as the browser verify.html HA gate card (kernels/_hagate.mjs, SPEC.md §27.4-27.5). A rejection record is terminal-blocking regardless of policy; an active time-boxed override (§27.5) takes precedence over the underlying policy. Pure function: caller supplies nowISO for determinism.","inputSchema":{"type":"object","properties":{}},"title":"Evaluate a §27.4/§27.5 human-accountability gate precondition","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"ha_gate_status","displayName":"Evaluate a §27.4/§27.5 human-accountability gate precondition"},{"name":"ha_bundle_export","description":"Assembles a §27.6 haEvidenceBundle from a subject's collected human_accountability_records[] (reviewers, approvers, annotations, exception rationale, timestamps) -- same algorithm as the browser verify.html HA export card (kernels/_haevidence.mjs). Set sd_jwt:true to also export it as a Selective Disclosure JWT (§13.12), signed EdDSA over a fresh ephemeral did:key (generated per call, never reused) -- subject_hash/verification_result/kernel_version/policy_version/timestamps/submission_receipt ar","inputSchema":{"type":"object","properties":{}},"title":"Assemble (and optionally SD-JWT-export) a §27.6 evidence bundle","logicalName":"ha_bundle_export","displayName":"Assemble (and optionally SD-JWT-export) a §27.6 evidence bundle","annotations":{"untrustedContentHint":true,"readOnlyHint":true}},{"name":"intoto_record_chain_run","description":"Wraps the result of a run_chain call (server/auto compute mode) as standard in-toto links, one per successfully-executed step, plus a generated in-toto layout matching the chain's linear topology (each step MATCHes the previous step's product). Materials/products are keyed by the step's execution_hash; byproducts carries the raw execution_hash. All links and the layout are DSSE-signed with one ephemeral Ed25519 keypair scoped to this call (never persisted) — first shipping instance of \"in-toto f","inputSchema":{"type":"object","properties":{}},"title":"Record a ChainGraph chain run as in-toto links","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"intoto_record_chain_run","displayName":"Record a ChainGraph chain run as in-toto links"},{"name":"build_evidence_pack","description":"Composes a session receipt (build_session_receipt logic), an optional §27.6 HA evidence bundle (ha_bundle_export logic, included only when ha_records is supplied and non-empty), and a disclosure manifest (build_disclosure_manifest logic) from one array of already-produced artifacts, all keyed to the same input hashes -- replacing what today takes 4-6 separate tool calls with hand-carried hashes. Calls the same in-process functions those standalone tools use; if any one section fails to build, th","inputSchema":{"type":"object","properties":{}},"title":"Assemble a complete evidence pack in one call","logicalName":"build_evidence_pack","displayName":"Assemble a complete evidence pack in one call","annotations":{"untrustedContentHint":true,"readOnlyHint":true}},{"name":"anchor_stamp","description":"Calls the anchor-suite MCP server (server-to-server, not the browser CORS-gated relay) to timestamp one execution_hash, or batch-anchor an array via anchor-suite's own anchor_batch (one upstream call per batch, RFC 6962 Merkle root anchored, per-hash merkle_inclusion returned), and shapes the result as literal OCG v0.7 section 20 anchor_bindings entries ready to append to an artifact. Success is only reported after this tool independently confirms anchored_hash (or, for a batch entry, merkle_inc","inputSchema":{"type":"object","properties":{}},"title":"Anchor an execution_hash (or batch) at a real timestamp authority","logicalName":"anchor_stamp","displayName":"Anchor an execution_hash (or batch) at a real timestamp authority","annotations":{"untrustedContentHint":true,"readOnlyHint":true}},{"name":"otlp_validate","description":"Structurally validates an OTLP/JSON trace (resourceSpans -> scopeSpans -> spans: hex traceId/spanId shape, quoted nanosecond timestamps, parent-span references, time ordering) and checks every gen_ai span's attributes against a pinned gen_ai semantic-convention attribute snapshot (the upstream open-telemetry/semantic-conventions-genai namespace ships zero tagged releases, so this is a dated pin, stamped as semconv_snapshot in the result -- expect it to drift as the upstream spec moves). Byte-ide","inputSchema":{"type":"object","properties":{}},"title":"Validate an OTLP/JSON trace for structure + gen_ai conformance","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"otlp_validate","displayName":"Validate an OTLP/JSON trace for structure + gen_ai conformance"},{"name":"otlp_span_receipt","description":"OTLP span/trace to receipt bundle; does NOT build a ChainGraph (use build_chaingraph for that). Three modes, chosen by which input is supplied. (1) Pass `trace` alone to GENERATE a receipt bundle: a per-span receipt (span digest, parent-span receipt digest, semconv_snapshot, eddsa-jcs-2022 signature over an ephemeral did:key) for every span, plus a Merkle-rooted (RFC 6962) trace receipt. (2) Pass `bundle` ({trace, span_receipts, trace_receipt, issuer_did}) to VERIFY it: recomputes every digest,","inputSchema":{"type":"object","properties":{}},"title":"Generate or verify a per-span OTel receipt bundle over an OTLP/JSON trace","logicalName":"otlp_span_receipt","displayName":"Generate or verify a per-span OTel receipt bundle over an OTLP/JSON trace","annotations":{"untrustedContentHint":true,"readOnlyHint":true}},{"name":"redline_diff","description":"An agent proposes an edit: diffs original text/markdown against its own revised version and returns the line-level hunks plus a diff receipt (original/revised digests, diff-algorithm declaration, per-hunk digests). Byte-identical to what the tools/552 browser workbench computes for the same inputs -- a human can paste the SAME original/revised text into that workbench, disposition each hunk (accept/reject/comment), and their resulting hunk/disposition receipts will reference this diff_receipt's","inputSchema":{"type":"object","properties":{}},"title":"Diff an original vs. proposed revision and mint a diff receipt","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"redline_diff","displayName":"Diff an original vs. proposed revision and mint a diff receipt"},{"name":"redline_verify","description":"Recomputes a redline review from scratch: the diff (from the pasted original+revised text), the diff_receipt's execution_hash, every hunk_receipt's digest/execution_hash/chain-link (in the order supplied -- entries may be minted by an agent, a human, or both interleaved), the disposition_receipt's execution_hash, and the accepted-text digest. Returns valid:true/false, a per-check breakdown, and broken_hunk (the zero-based index of the first divergence, or null) -- never trusts a bundle claim wit","inputSchema":{"type":"object","properties":{}},"title":"Verify a redline receipt bundle against the original + revised text","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"redline_verify","displayName":"Verify a redline receipt bundle against the original + revised text"},{"name":"lei_kyb_check","description":"Fetches an entity's live GLEIF LEI record (api.gleif.org -- the worker's only egress target for this tool, RULINGS-2026-07-19-EGRESS-APEX.md R1) and grades it across six GLEIF data-quality dimensions -- registration status, renewal timeliness, corroboration level, entity status, Level-2 parent disclosure, address completeness -- using the SAME deterministic grader as the tools/551 browser workbench (pasting the same record there reproduces identical grades). Returns per-dimension grades, a compo","inputSchema":{"type":"object","properties":{}},"title":"Live LEI data-quality grading with GLEIF fetch","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"lei_kyb_check","displayName":"Live LEI data-quality grading with GLEIF fetch"},{"name":"acdc_said_check","description":"Agent-facing mirror of the tools/553 browser workbench (VS-1) -- recomputes the self-addressing identifiers (SAIDs) of a pasted ACDC / vLEI credential JSON (top-level \"d\" plus any nested a/e/r blocks) under the KERI/CESR Blake3-256 (\"E\") or SHA2-256 (\"I\") derivation codes, and cross-checks the declared schema SAID (\"s\") against a pinned table of 6 official GLEIF vLEI schema SAIDs. Reuses the SAME vendored SAID-check module as T553 -- the same credential produces byte-identical findings in either","inputSchema":{"type":"object","properties":{}},"title":"Recompute ACDC / vLEI credential SAIDs (structural integrity)","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"acdc_said_check","displayName":"Recompute ACDC / vLEI credential SAIDs (structural integrity)"},{"name":"workbook_csv_parse","description":"Parses CSV text with the SAME strict RFC 4180 parser as the tools/554 browser workbook -- quoted fields, embedded quotes/commas/newlines, CRLF -- and REJECTS malformed input rather than repairing it (deterministic beats forgiving for hash-stable digests). Numeric-looking and TRUE/FALSE cells are type-coerced; everything else stays a string. Returns the resulting A1-style cells (raw + evaluated value) plus the sheet's row/column extent, ready for workbook_evaluate or workbook_range_digest -- unle","inputSchema":{"type":"object","properties":{}},"title":"Parse strict RFC 4180 CSV into workbook cells","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"workbook_csv_parse","displayName":"Parse strict RFC 4180 CSV into workbook cells"},{"name":"pain001_validate","description":"Validates a pain.001.001.09 customer credit transfer initiation XML document against the same hand-derived schema-subset table as the tools/555 browser validator -- structural (mandatory fields), facet (IBAN mod-97, BIC format, ISO 4217 currency, decimal/date patterns), and batch-total cross-checks (NbOfTxs vs. actual transaction count, CtrlSum vs. sum of InstdAmt). Byte-identical error set to the browser tool for the same input. Subset validation, not full XSD conformance -- prepare/validate on","inputSchema":{"type":"object","properties":{}},"title":"Validate a pain.001.001.09 message against the schema-subset table","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"pain001_validate","displayName":"Validate a pain.001.001.09 message against the schema-subset table"},{"name":"camt053_parse","description":"Parses a camt.053.001 bank-to-customer statement XML document with the same schema-subset structural and facet checks as the tools/565 browser reconciliation workbench (IBAN mod-97, BIC, currency, date/decimal facets), returning the extracted statement (message id, statement id, account IBAN/currency, balances, entries) on success or the structural error list on failure. Byte-identical extraction to the browser tool for the same input. Read-only parse -- feed the result to recon_match for reconc","inputSchema":{"type":"object","properties":{}},"title":"Parse and structurally validate a camt.053.001 bank statement","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"camt053_parse","displayName":"Parse and structurally validate a camt.053.001 bank statement"},{"name":"recon_match","description":"Parses a camt.053.001 statement (same schema-subset checks as camt053_parse) and a counterpart expectation set (CSV, header EndToEndId,Amount,Currency,Date -- same strict RFC 4180 parser as the WORKBOOK-1 CSV tools), then runs the SAME deterministic match engine as the tools/565 browser workbench: EndToEndId exact match first (statement order), then amount+date tolerance + currency match (first unmatched expectation in CSV order). Returns matches, exceptions (unmatched entries/expectations), and","inputSchema":{"type":"object","properties":{}},"title":"Match a camt.053 statement against a counterpart expectation set","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"recon_match","displayName":"Match a camt.053 statement against a counterpart expectation set"},{"name":"diagnose_canton_readiness","description":"Canton Tokenization Readiness Diagnostic: OpenChainGraph compute node (readiness_diagnostic). Deterministic OpenChainGraph compute node. By default (compute:\"auto\") inputs are computed server-side on Cloudflare Workers for gpu:false nodes with a registered kernel; compute:\"browser\" forces client-side execution and returns a browser delegation URL instead. gpu:true nodes always delegate to the browser. Inputs are processed transiently to compute the response and are not stored, logged, or retaine","inputSchema":{"type":"object","properties":{}},"title":"Canton Tokenization Readiness Diagnostic","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"diagnose_canton_readiness","displayName":"Canton Tokenization Readiness Diagnostic"},{"name":"optimize_settlement_capital","description":"Settlement-Risk Capital Efficiency Optimizer: OpenChainGraph compute node (capital_assessment). Deterministic OpenChainGraph compute node. By default (compute:\"auto\") inputs are computed server-side on Cloudflare Workers for gpu:false nodes with a registered kernel; compute:\"browser\" forces client-side execution and returns a browser delegation URL instead. gpu:true nodes always delegate to the browser. Inputs are processed transiently to compute the response and are not stored, logged, or retai","inputSchema":{"type":"object","properties":{}},"title":"Settlement-Risk Capital Efficiency Optimizer","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"optimize_settlement_capital","displayName":"Settlement-Risk Capital Efficiency Optimizer"},{"name":"check_tokenized_collateral_eligibility","description":"Tokenized Collateral Eligibility Checker: OpenChainGraph compute node (collateral_mandate). Deterministic OpenChainGraph compute node. By default (compute:\"auto\") inputs are computed server-side on Cloudflare Workers for gpu:false nodes with a registered kernel; compute:\"browser\" forces client-side execution and returns a browser delegation URL instead. gpu:true nodes always delegate to the browser. Inputs are processed transiently to compute the response and are not stored, logged, or retained.","inputSchema":{"type":"object","properties":{}},"title":"Tokenized Collateral Eligibility Checker","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"check_tokenized_collateral_eligibility","displayName":"Tokenized Collateral Eligibility Checker"},{"name":"check_cash_leg_finality","description":"On-Chain Cash-Leg Finality Checker: OpenChainGraph compute node (attestation_mandate). Deterministic OpenChainGraph compute node. By default (compute:\"auto\") inputs are computed server-side on Cloudflare Workers for gpu:false nodes with a registered kernel; compute:\"browser\" forces client-side execution and returns a browser delegation URL instead. gpu:true nodes always delegate to the browser. Inputs are processed transiently to compute the response and are not stored, logged, or retained. Use","inputSchema":{"type":"object","properties":{}},"title":"On-Chain Cash-Leg Finality Checker","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"check_cash_leg_finality","displayName":"On-Chain Cash-Leg Finality Checker"},{"name":"validate_canton_dvp_atomicity","description":"Canton DvP Atomicity Validator: OpenChainGraph compute node (settlement_mandate). Deterministic OpenChainGraph compute node. By default (compute:\"auto\") inputs are computed server-side on Cloudflare Workers for gpu:false nodes with a registered kernel; compute:\"browser\" forces client-side execution and returns a browser delegation URL instead. gpu:true nodes always delegate to the browser. Inputs are processed transiently to compute the response and are not stored, logged, or retained. Use synth","inputSchema":{"type":"object","properties":{}},"title":"Canton DvP Atomicity Validator","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"validate_canton_dvp_atomicity","displayName":"Canton DvP Atomicity Validator"},{"name":"calculate_repo_haircut","description":"On-Chain Repo Haircut Calculator: OpenChainGraph compute node (collateral_mandate). Deterministic OpenChainGraph compute node. By default (compute:\"auto\") inputs are computed server-side on Cloudflare Workers for gpu:false nodes with a registered kernel; compute:\"browser\" forces client-side execution and returns a browser delegation URL instead. gpu:true nodes always delegate to the browser. Inputs are processed transiently to compute the response and are not stored, logged, or retained. Use syn","inputSchema":{"type":"object","properties":{}},"title":"On-Chain Repo Haircut Calculator","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"calculate_repo_haircut","displayName":"On-Chain Repo Haircut Calculator"},{"name":"validate_canton_party_allowlist","description":"Canton Party Allowlist Validator: OpenChainGraph compute node (compliance_mandate). Deterministic OpenChainGraph compute node. By default (compute:\"auto\") inputs are computed server-side on Cloudflare Workers for gpu:false nodes with a registered kernel; compute:\"browser\" forces client-side execution and returns a browser delegation URL instead. gpu:true nodes always delegate to the browser. Inputs are processed transiently to compute the response and are not stored, logged, or retained. Use syn","inputSchema":{"type":"object","properties":{}},"title":"Canton Party Allowlist Validator","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"validate_canton_party_allowlist","displayName":"Canton Party Allowlist Validator"},{"name":"classify_digital_asset_regulatory","description":"Digital Asset Regulatory Classifier: OpenChainGraph compute node (compliance_mandate). Deterministic OpenChainGraph compute node. By default (compute:\"auto\") inputs are computed server-side on Cloudflare Workers for gpu:false nodes with a registered kernel; compute:\"browser\" forces client-side execution and returns a browser delegation URL instead. gpu:true nodes always delegate to the browser. Inputs are processed transiently to compute the response and are not stored, logged, or retained. Use","inputSchema":{"type":"object","properties":{}},"title":"Digital Asset Regulatory Classifier","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"classify_digital_asset_regulatory","displayName":"Digital Asset Regulatory Classifier"},{"name":"validate_pvp_settlement","description":"Multi-Currency PvP Validator: OpenChainGraph compute node (settlement_mandate). Deterministic OpenChainGraph compute node. By default (compute:\"auto\") inputs are computed server-side on Cloudflare Workers for gpu:false nodes with a registered kernel; compute:\"browser\" forces client-side execution and returns a browser delegation URL instead. gpu:true nodes always delegate to the browser. Inputs are processed transiently to compute the response and are not stored, logged, or retained. Use synthet","inputSchema":{"type":"object","properties":{}},"title":"Multi-Currency PvP Validator","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"validate_pvp_settlement","displayName":"Multi-Currency PvP Validator"},{"name":"validate_tokenized_security_lifecycle","description":"Tokenized Security Lifecycle Validator: OpenChainGraph compute node (compliance_mandate). Deterministic OpenChainGraph compute node. By default (compute:\"auto\") inputs are computed server-side on Cloudflare Workers for gpu:false nodes with a registered kernel; compute:\"browser\" forces client-side execution and returns a browser delegation URL instead. gpu:true nodes always delegate to the browser. Inputs are processed transiently to compute the response and are not stored, logged, or retained. U","inputSchema":{"type":"object","properties":{}},"title":"Tokenized Security Lifecycle Validator","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"validate_tokenized_security_lifecycle","displayName":"Tokenized Security Lifecycle Validator"},{"name":"mobilize_margin_collateral","description":"Margin Call Collateral Mobilizer: OpenChainGraph compute node (collateral_mandate). Deterministic OpenChainGraph compute node. By default (compute:\"auto\") inputs are computed server-side on Cloudflare Workers for gpu:false nodes with a registered kernel; compute:\"browser\" forces client-side execution and returns a browser delegation URL instead. gpu:true nodes always delegate to the browser. Inputs are processed transiently to compute the response and are not stored, logged, or retained. Use syn","inputSchema":{"type":"object","properties":{}},"title":"Margin Call Collateral Mobilizer","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"mobilize_margin_collateral","displayName":"Margin Call Collateral Mobilizer"},{"name":"validate_fund_collateral","description":"Tokenized Fund Collateral Validator: OpenChainGraph compute node (collateral_mandate). Deterministic OpenChainGraph compute node. By default (compute:\"auto\") inputs are computed server-side on Cloudflare Workers for gpu:false nodes with a registered kernel; compute:\"browser\" forces client-side execution and returns a browser delegation URL instead. gpu:true nodes always delegate to the browser. Inputs are processed transiently to compute the response and are not stored, logged, or retained. Use","inputSchema":{"type":"object","properties":{}},"title":"Tokenized Fund Collateral Validator","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"validate_fund_collateral","displayName":"Tokenized Fund Collateral Validator"},{"name":"validate_collateral_swap_eligibility","description":"Collateral Swap Eligibility Validator: OpenChainGraph compute node (collateral_mandate). Deterministic OpenChainGraph compute node. By default (compute:\"auto\") inputs are computed server-side on Cloudflare Workers for gpu:false nodes with a registered kernel; compute:\"browser\" forces client-side execution and returns a browser delegation URL instead. gpu:true nodes always delegate to the browser. Inputs are processed transiently to compute the response and are not stored, logged, or retained. Us","inputSchema":{"type":"object","properties":{}},"title":"Collateral Swap Eligibility Validator","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"validate_collateral_swap_eligibility","displayName":"Collateral Swap Eligibility Validator"},{"name":"validate_ap2_mandate_chain","description":"AP2 Mandate-Chain Validator: OpenChainGraph compute node (payment_mandate). Deterministic OpenChainGraph compute node. By default (compute:\"auto\") inputs are computed server-side on Cloudflare Workers for gpu:false nodes with a registered kernel; compute:\"browser\" forces client-side execution and returns a browser delegation URL instead. gpu:true nodes always delegate to the browser. Inputs are processed transiently to compute the response and are not stored, logged, or retained. Use synthetic o","inputSchema":{"type":"object","properties":{}},"title":"AP2 Mandate-Chain Validator","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"validate_ap2_mandate_chain","displayName":"AP2 Mandate-Chain Validator"},{"name":"simulate_spend_policy","description":"Agent Spend-Policy Simulator: OpenChainGraph compute node (payment_policy). Deterministic OpenChainGraph compute node. By default (compute:\"auto\") inputs are computed server-side on Cloudflare Workers for gpu:false nodes with a registered kernel; compute:\"browser\" forces client-side execution and returns a browser delegation URL instead. gpu:true nodes always delegate to the browser. Inputs are processed transiently to compute the response and are not stored, logged, or retained. Use synthetic o","inputSchema":{"type":"object","properties":{}},"title":"Agent Spend-Policy Simulator","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"simulate_spend_policy","displayName":"Agent Spend-Policy Simulator"},{"name":"model_x402_settlement","description":"x402 Settlement Cost & Finality Modeler: OpenChainGraph compute node (settlement_mandate). Deterministic OpenChainGraph compute node. By default (compute:\"auto\") inputs are computed server-side on Cloudflare Workers for gpu:false nodes with a registered kernel; compute:\"browser\" forces client-side execution and returns a browser delegation URL instead. gpu:true nodes always delegate to the browser. Inputs are processed transiently to compute the response and are not stored, logged, or retained.","inputSchema":{"type":"object","properties":{}},"title":"x402 Settlement Cost & Finality Modeler","annotations":{"readOnlyHint":true,"untrustedContentHint":true},"logicalName":"model_x402_settlement","displayName":"x402 Settlement Cost & Finality Modeler"}],"toolSource":"directory_preview","agentAction":"both","installLinks":[{"id":"cursor","label":"Cursor","href":"cursor://anysphere.cursor-deeplink/mcp/install?name=Run-Verify-Anchor-&config=eyJ1cmwiOiAiaHR0cHM6Ly9tY3AuYWludW1iZXJzLmNvL21jcCJ9"},{"id":"vscode","label":"VS Code","href":"vscode:mcp/install?%7B%22name%22%3A%22Run-Verify-Anchor-%22%2C%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.ainumbers.co%2Fmcp%22%7D"},{"id":"vscode-insiders","label":"VS Code Insiders","href":"vscode-insiders:mcp/install?%7B%22name%22%3A%22Run-Verify-Anchor-%22%2C%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.ainumbers.co%2Fmcp%22%7D"},{"id":"claude-web","label":"Claude.ai","href":"https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Run.+Verify.+Anchor.&connectorUrl=https%3A%2F%2Fmcp.ainumbers.co%2Fmcp"},{"id":"codex","label":"Codex","copyText":"codex mcp add \"Run-Verify-Anchor-\" --url \"https://mcp.ainumbers.co/mcp\""},{"id":"chatgpt","label":"ChatGPT","href":"https://www.mcpbundles.com/docs/integrations/chatgpt"}],"catalogUrl":"https://www.mcpbundles.com/api/directory/v1/servers/ainumbers-mcp-280a0f751f","callUrl":"https://www.mcpbundles.com/api/directory/v1/servers/ainumbers-mcp-280a0f751f/tools/{tool}","mcpServerUrl":"https://mcp.ainumbers.co/mcp","liveCatalogUrl":"https://www.mcpbundles.com/api/directory/v1/servers/ainumbers-mcp-280a0f751f?live=1"}