{"id":"co.ainumbers/tools","slug":"co-ainumbers-tools","title":"AINumbers Fintech Intelligence Suite","description":"827 MCP tools across 1275 fintech tools: ChainGraph AP2 decisions, execution_hash. Zero PII.","version":"0.4.76","publisher":{"kind":"domain","id":"ainumbers.co","label":"ainumbers.co","url":"https://ainumbers.co"},"website":"https://ainumbers.co","repository":"https://github.com/PostOakLabs/ainumbers-mcp-apps","remotes":[{"type":"streamable-http","url":"https://mcp.ainumbers.co/mcp"}],"packages":[],"published":"2026-11-19","updated":"2026-11-19","status":"online","auth":"","latency_ms":1916,"checked":"2026-11-19","uptime":100,"checks":3,"tools":[{"name":"list_ainumbers_tools","title":"List AINumbers tools","description":"Search the AINumbers catalog (1270+ client-side fintech tools). Returns deep-links; prefill-enabled tools accept #in=<base64url(JSON of {element_id: value})>[&run=1] for one-click invocation.","read_only":true},{"name":"build_workflow_links","title":"Build AINumbers workflow deep-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","read_only":true},{"name":"verify_execution_hash","title":"Verify a ChainGraph 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 integrity: policy_parameters and output_payload are byte-for-byte what was hashed. It does not by itself show the outputs were computed from the inpu","read_only":true},{"name":"build_chaingraph","title":"Build an executable ChainGraph DAG","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 li","read_only":true},{"name":"emit_chaingraph_artifact","title":"Emit a ChainGraph artifact envelope","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 ","read_only":true},{"name":"build_session_receipt","title":"Build a session audit receipt (Merkle root)","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","read_only":true},{"name":"find_tool","title":"Find ChainGraph node tool","description":"BM25 search over all 766 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-leve","read_only":true},{"name":"find_chain","title":"Find ChainGraph workflow chain","description":"BM25 search over all 417 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","read_only":true},{"name":"run_chain","title":"Run a whole ChainGraph chain in one call","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-l","read_only":true},{"name":"suite_howto","title":"AINumbers suite how-to: workflow recipes","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.","read_only":true},{"name":"describe_tool","title":"Describe one AINumbers 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_t","read_only":true},{"name":"run_chain_batch","title":"Run or estimate several ChainGraph chains in one call","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 covera","read_only":true},{"name":"call_tool","title":"Run any AINumbers tool by name","description":"Runs ONE read-only AINumbers tool that is not in your tool list. tools/list is paginated (13 pages, 722 tools) and many hosts read only the first page; this is the door to the rest. Pass { name: \"<exact mcp_name>\", arguments: { ... } } — the target's own inputSchema is validated and its result is returned verbatim, including execution_hash, so a dispatched call and a direct call are byte-identical","read_only":true},{"name":"baas_provider_comparator","title":"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 A","read_only":true},{"name":"validate_ap2_mcp_policy","title":"AP2 MCP Policy Validator & Bridge","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)","read_only":true},{"name":"build_google_ap2_mandate","title":"Google AP2 Checkout/Payment Mandate (VDC) Builder & Validator","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\").","read_only":true},{"name":"score_mcp_readiness","title":"MCP Developer Readiness Scorecard","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\").","read_only":true},{"name":"agentic_mandate_sandbox","title":"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,","read_only":true},{"name":"customer_risk_rating","title":"Customer Risk Rating Engine","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 ru","read_only":true},{"name":"ap2_aml_mandate_builder","title":"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 ","read_only":true},{"name":"lint_mcp_tool_definition","title":"MCP Tool-Definition Linter & Annotation Designer","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, z","read_only":true},{"name":"validate_mcp_server_json","title":"MCP server.json Validator & Registry-Ready Skeleton Generator","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 P","read_only":true},{"name":"compare_agentic_payment_protocols","title":"Agentic Payments Protocol Comparator & Field Crosswalk","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 fragmentin","read_only":true},{"name":"decode_x402_payment","title":"x402 Header Decoder, Payload Linter & 402 Flow Simulator","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","read_only":true},{"name":"audit_mcp_oauth","title":"MCP OAuth 2.1 Authorization Auditor","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 de","read_only":true},{"name":"scan_tool_poisoning","title":"MCP Tool-Poisoning & Prompt-Injection Manifest Scanner","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\").","read_only":true},{"name":"validate_a2a_agent_card","title":"A2A Agent Card Validator & Extension Checker","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\").","read_only":true},{"name":"inspect_visa_tap_signature","title":"Visa Trusted Agent Protocol Signature Inspector & Readiness","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\").","read_only":true},{"name":"run_kernel_vm","title":"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-s","read_only":true},{"name":"validate_input_attestations","title":"Validate ChainGraph 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 structura","read_only":true},{"name":"validate_private_inputs","title":"Validate ChainGraph private-input commitments","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 ","read_only":true},{"name":"build_disclosure_manifest","title":"Build a signed data-room 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 hashin","read_only":true},{"name":"verify_disclosure_inclusion","title":"Verify Merkle inclusion in a disclosure manifest","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. Absenc","read_only":true},{"name":"suggest_tool_idea","title":"Suggest a new tool, node, or workflow","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.","read_only":true},{"name":"export_artifact","title":"Export a ChainGraph artifact as xlsx / pdf / csv / xbrl / vc","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, pd","read_only":true},{"name":"vc_issue","title":"Issue a signed W3C Verifiable Credential 2.0","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 we","read_only":false},{"name":"sdjwt_issue","title":"Issue a Selective Disclosure JWT (RFC 9901)","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.","read_only":false},{"name":"sdjwt_present","title":"Present a redacted Selective Disclosure JWT","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 p","read_only":false},{"name":"checklist_validate_definition","title":"Validate a checklist/SOP 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.","read_only":true},{"name":"checklist_step_receipt","title":"Mint a hash-chained 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 ord","read_only":false},{"name":"checklist_verify_run","title":"Verify a checklist run's hash chain and Merkle root","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.","read_only":true},{"name":"ha_record_validate","title":"Validate a §27 human-accountability record","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.","read_only":true},{"name":"ha_gate_status","title":"Evaluate a §27.4/§27.5 human-accountability gate precondition","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 u","read_only":true},{"name":"ha_bundle_export","title":"Assemble (and optionally SD-JWT-export) a §27.6 evidence bundle","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","read_only":false},{"name":"intoto_record_chain_run","title":"Record a ChainGraph chain run as in-toto links","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 eph","read_only":true},{"name":"build_evidence_pack","title":"Assemble a complete evidence pack in one call","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. C","read_only":false},{"name":"anchor_stamp","title":"Anchor an execution_hash (or batch) at a real timestamp authority","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 o","read_only":false},{"name":"otlp_validate","title":"Validate an OTLP/JSON trace for structure + gen_ai conformance","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, s","read_only":true},{"name":"otlp_span_receipt","title":"Generate or verify a per-span OTel receipt bundle over an OTLP/JSON trace","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 ","read_only":false},{"name":"redline_diff","title":"Diff an original vs. proposed revision and mint a diff receipt","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 (accep","read_only":true},{"name":"redline_verify","title":"Verify a redline receipt bundle against the original + revised text","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 br","read_only":true},{"name":"lei_kyb_check","title":"Live LEI data-quality grading with GLEIF fetch","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 workbenc","read_only":true},{"name":"acdc_said_check","title":"Recompute ACDC / vLEI credential SAIDs (structural integrity)","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 ","read_only":true},{"name":"workbook_evaluate","title":"Evaluate workbook cells (formulas + literals) and return computed values","description":"Feeds a set of A1-style cells (formulas and/or literals) through the SAME headless evaluator the tools/554 browser workbook uses -- topo-sorted dependency graph, ~20 functions (SUM AVG MIN MAX COUNT COUNTIF IF AND OR NOT ROUND ABS CONCAT LEN LEFT RIGHT TRIM UPPER LOWER SUMIF), cycles resolve to \"#CYCLE!\" and any non-finite result to \"#NUM!\" rather than propagating. Returns the computed value of ev","read_only":true},{"name":"workbook_range_digest","title":"Digest a workbook range into a Spreadsheet Input Manifest range fragment","description":"Spreadsheet-range digest only; NOT the general artifact emitter (use emit_chaingraph_artifact to wrap arbitrary computation output — this tool's as_artifact mode covers whole-sheet workbook runs only). Evaluates the supplied cells (same evaluator as workbook_evaluate) and computes a canonical values_digest over one A1-style range (e.g. \"B2:D9\") -- the exact `executionHash(values, {})` path the res","read_only":true},{"name":"workbook_csv_parse","title":"Parse strict RFC 4180 CSV into workbook cells","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 val","read_only":true},{"name":"workbook_roundtrip_verify","title":"Verify a pasted-back Excel round-trip against a Spreadsheet Input Manifest","description":"Compares a WB-2 Spreadsheet Input Manifest (expected digests) against pasted-back CSV/TSV text per manifest range (observed, e.g. after a recompute in Excel) and returns an XLR-1 round-trip receipt -- `result: \"match\"|\"mismatch\"` plus a `mismatches[]` cell list when expected_by_ref text is also supplied. SAME comparator module as the tools/ round-trip page (XLR-2/XLR-3) -- byte-identical receipt f","read_only":true},{"name":"pain001_validate","title":"Validate a pain.001.001.09 message against the schema-subset table","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","read_only":true},{"name":"camt053_parse","title":"Parse and structurally validate a camt.053.001 bank statement","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 ","read_only":true},{"name":"recon_match","title":"Match a camt.053 statement against a counterpart expectation set","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 un","read_only":true},{"name":"diagnose_canton_readiness","title":"Canton Tokenization Readiness Diagnostic","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 brow","read_only":true},{"name":"optimize_settlement_capital","title":"Settlement-Risk Capital Efficiency Optimizer","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 br","read_only":true},{"name":"check_tokenized_collateral_eligibility","title":"Tokenized Collateral Eligibility Checker","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 browse","read_only":true},{"name":"check_cash_leg_finality","title":"On-Chain Cash-Leg Finality Checker","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. In","read_only":true},{"name":"validate_canton_dvp_atomicity","title":"Canton DvP Atomicity Validator","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 ","read_only":true},{"name":"calculate_repo_haircut","title":"On-Chain Repo Haircut Calculator","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. Input","read_only":true},{"name":"validate_canton_party_allowlist","title":"Canton Party Allowlist Validator","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. Input","read_only":true},{"name":"classify_digital_asset_regulatory","title":"Digital Asset Regulatory Classifier","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. In","read_only":true},{"name":"validate_pvp_settlement","title":"Multi-Currency PvP Validator","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 ar","read_only":true},{"name":"validate_tokenized_security_lifecycle","title":"Tokenized Security Lifecycle Validator","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.","read_only":true},{"name":"mobilize_margin_collateral","title":"Margin Call Collateral Mobilizer","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. Input","read_only":true},{"name":"validate_fund_collateral","title":"Tokenized Fund Collateral Validator","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. In","read_only":true},{"name":"validate_collateral_swap_eligibility","title":"Collateral Swap Eligibility Validator","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. ","read_only":true},{"name":"audit_borrower_escrow_stmt","title":"Borrower Escrow Auditor","description":"Borrower Escrow Auditor: OpenChainGraph compute node (consumer_finance). 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 proce","read_only":true}],"server_info":{"name":"ainumbers-apps","version":"1.2.0"},"category":"crypto","tags":["developer","finance","legal"],"kind":"remote","source":"registry","submitted":{},"first_party":true,"domain_rank":null,"score":100,"indexable":true,"first_seen":"2026-06-07","stars":0,"badges":[],"sponsor":null,"page":"https://agentsindex.org/agents/co-ainumbers-tools/"}