suite_howto — AINumbers Fintech Intelligence Suite MCP Tool
suite_howto
(suite howto) is one of 75 tools on the
AINumbers Fintech Intelligence Suite
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call suite_howto from your client
- Claude Code AINumbers Fintech Intelligence Suite suite_howto run in your project directory
- Claude Desktop AINumbers Fintech Intelligence Suite suite_howto ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor AINumbers Fintech Intelligence Suite suite_howto ~/.cursor/mcp.json
- VS Code AINumbers Fintech Intelligence Suite suite_howto .vscode/mcp.json
- Zed AINumbers Fintech Intelligence Suite suite_howto ~/.config/zed/settings.json
- Windsurf AINumbers Fintech Intelligence Suite suite_howto ~/.codeium/windsurf/mcp_config.json
- Cline AINumbers Fintech Intelligence Suite suite_howto ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI AINumbers Fintech Intelligence Suite suite_howto ~/.gemini/settings.json
- Grok AINumbers Fintech Intelligence Suite suite_howto .mcp.json (in your project root)
- ChatGPT AINumbers Fintech Intelligence Suite suite_howto Settings → Connectors → Advanced → Developer mode
- Claude.ai AINumbers Fintech Intelligence Suite suite_howto Settings → Connectors → Add custom connector
- LangChain AINumbers Fintech Intelligence Suite suite_howto pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http tools https://mcp.ainumbers.co/mcpOther tools on this server
- baas_provider_comparator
- validate_ap2_mcp_policy
- build_google_ap2_mandate
- score_mcp_readiness
- agentic_mandate_sandbox
- customer_risk_rating
- ap2_aml_mandate_builder
- lint_mcp_tool_definition
- validate_mcp_server_json
- compare_agentic_payment_protocols
- decode_x402_payment
- audit_mcp_oauth
- scan_tool_poisoning
- validate_a2a_agent_card
- inspect_visa_tap_signature
- run_kernel_vm
- list_ainumbers_tools
- build_workflow_links
- verify_execution_hash
- validate_input_attestations
- validate_private_inputs
- build_disclosure_manifest
- verify_disclosure_inclusion
- build_chaingraph
- run_chain
- run_chain_batch
- emit_chaingraph_artifact
- build_session_receipt
- suggest_tool_idea
- export_artifact
- find_chain
- find_tool
- describe_tool
- vc_issue
- sdjwt_issue
- sdjwt_present
- checklist_validate_definition
- checklist_step_receipt
- checklist_verify_run
- ha_record_validate
- ha_gate_status
- ha_bundle_export
- intoto_record_chain_run
- build_evidence_pack
- anchor_stamp
- otlp_validate
- otlp_span_receipt
- redline_diff
- redline_verify
- lei_kyb_check
- acdc_said_check
- workbook_evaluate
- workbook_range_digest
- workbook_csv_parse
- workbook_roundtrip_verify
- pain001_validate
- camt053_parse
- recon_match
- diagnose_canton_readiness
- optimize_settlement_capital
- check_tokenized_collateral_eligibility
- check_cash_leg_finality
- validate_canton_dvp_atomicity
- calculate_repo_haircut
- validate_canton_party_allowlist
- classify_digital_asset_regulatory
- validate_pvp_settlement
- validate_tokenized_security_lifecycle
- mobilize_margin_collateral
- validate_fund_collateral
- validate_collateral_swap_eligibility
- validate_ap2_mandate_chain
- simulate_spend_policy
- model_x402_settlement
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.