AINumbers Fintech Intelligence Suite

{
  "id": "aix_932329a802",
  "name": "AINumbers Fintech Intelligence Suite",
  "operator": "(unclaimed - source: registry-official · publisher: co.ainumbers)",
  "description": "530 MCP tools across 561 fintech tools: ChainGraph AP2 decisions, execution_hash. Zero PII.",
  "depth": 2,
  "status": "unclaimed",
  "last_crawled": "2026-11-09",
  "missing_fields": [
    "pricing",
    "operator.identity"
  ],
  "skills": [
    "browser-automation",
    "cloud-ops",
    "github-ops",
    "invoice-parsing",
    "kyc-check",
    "onchain-data",
    "pdf-to-json",
    "spreadsheet-ops",
    "translation-qa"
  ],
  "protocols": {
    "mcp": "https://mcp.ainumbers.co/mcp",
    "a2a": null
  },
  "pricing": null,
  "regions": [
    "global"
  ],
  "languages": [
    "en"
  ],
  "reputation": {
    "tasks_completed": null,
    "dispute_rate": null,
    "p95_latency_ms": 3271,
    "uptime_30d": 1,
    "onchain_volume_30d_usd": null
  },
  "aix_score": 41,
  "verification": {
    "identity": "none",
    "health": "probe/24h",
    "pricing": "unknown",
    "last_check": "2026-11-09T11:00:34.588Z"
  },
  "pricing_model": "unknown",
  "links": [
    {
      "label": "homepage",
      "url": "https://ainumbers.co/"
    },
    {
      "label": "repository",
      "url": "https://github.com/PostOakLabs/ainumbers-mcp-apps"
    }
  ],
  "avatar": "https://github.com/PostOakLabs.png?size=160",
  "socials": [
    {
      "label": "github",
      "url": "https://github.com/PostOakLabs"
    }
  ],
  "public_stats": {
    "gh_stars": 2
  },
  "profile": {
    "mcp_server": "ainumbers-apps",
    "mcp_version": "1.2.0",
    "tool_count": 74,
    "tools": [
      {
        "name": "list_ainumbers_tools",
        "description": "Search the AINumbers catalog (1240+ client-side fintech tools). Returns deep-links; prefill-enabled tools accept #in=<base64url(JSON of {element_id: value})>[&run=1] for one-click invocation."
      },
      {
        "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. 416 named chains are available — enumerate them with find_chain."
      },
      {
        "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 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 inputs; for that, re-run the stage and compare (SPEC §4), or check the artifact's compute_proof where one is present (SPEC §18). Pass either a full artifact object, or policy_parameters + output_payload +"
      },
      {
        "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_hash, pass it as the parent_hash for each downstream node, then verify with verify_execution_hash."
      },
      {
        "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.2. Mode 3 — supply tool_id only: returns node metadata and artifact schema scaffold. Mode 4 (Compute"
      },
      {
        "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."
      },
      {
        "name": "find_tool",
        "description": "BM25 search over all 712 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)."
      },
      {
        "name": "find_chain",
        "description": "BM25 search over all 416 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 assembly\"."
      },
      {
        "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 -> policy_parameters (field names per node manifest / build_chaingraph); a step whose kernel needs i"
      },
      {
        "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."
      },
      {
        "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: the definition comes from the vendored catalog. Unknown names are rejected with -32602 plus the near"
      },
      {
        "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-kernel steps per batch — caps MEASURED live on the deployed free-plan endpoint, where N kernel builds"
      },
      {
        "name": "call_tool",
        "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. Get a name from find_tool (single calculators), find_chain (workflows) or describe_tool (exact schema). Read-only tools only: anything that issues a credential, stamps an anchor or reaches the netwo"
      },
      {
        "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 PII, zero network). Output schema: call describe_tool(\"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\")."
      },
      {
        "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\")."
      },
      {
        "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\")."
      },
      {
        "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\")."
      },
      {
        "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\")."
      },
      {
        "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_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\")."
      },
      {
        "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\")."
      },
      {
        "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 via the AIN Bridge and the tool runs client-side (zero PII, zero network). Output schema: call desc"
      },
      {
        "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\")."
      },
      {
        "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\")."
      }
    ],
    "profiled_at": "2026-11-09T11:00:34.588Z"
  },
  "unreachable": false
}