Agentic Finance Graph MCP Server
Related Servers
Alternatives to Agentic Finance Graph MCP Server
- AlicenseAqualityBmaintenanceEnables agents to query a read-only ledger of machine payments, exposing tools for spending totals, purchases with event chains, verdicts, payer passports, and fiscal reporting data.7MIT
Related Servers
- FlicenseNot gradedqualityBmaintenanceProvides protocol-neutral market intelligence for the AI agent economy, with read-only tools to search agents, retrieve details and histories, compare agents, list categories, view category rankings, and access methodology.-
- AlicenseAqualityAmaintenanceProvides AI agents read-only, keyless access to Aster DEX data, including futures and spot markets, TradFi perpetuals, funding rates, order books, klines, vault deposit flows, and account views through MCP tools.1359 PyPI1MIT
- AlicenseNot gradedqualityCmaintenanceProvides live, read-only access to Robinhood Chain and Lox Corp data, enabling AI agents to query chain stats, token launches, agent details, and more.7 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to query a read-only data surface through typed tools, enforcing caller-specific row access, field masking, and withheld-row disclosure so they can retrieve entitled information without writes or silent data leakage.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to preview Base token market data, evaluate SpendGuard spending policies, and read x402 payment challenge terms without signing or paying.Apache 2.0
- AlicenseAqualityCmaintenanceEnables MCP-capable AI agents to make pay-per-call Solana data requests (snapshots, risk checks, token reports, health, balances, transactions, trending pairs) with automatic USDC settlement over x402.5MIT
TDQS
Scored across 25 tools
Several clusters of tools target near-identical decisions: pay_check, gate_check, payee_facts, agent_pattern, agent_pass and blast_radius all answer variants of 'is it safe to pay this agent/address', and find_agent, agent_record, ranked_agents, payer_set and counterparty_preview all retrieve agent/counterparty data. Descriptions do add distinguishing language (free vs paid pack, per-payment vs per-agent) but an agent could easily pick the wrong one. Boundaries exist but are subtle rather than clean.
All names are consistent snake_case with no camelCase or mixed styles. There is mild drift between noun-only names (definition, detections, market_state, agent_record, payee_facts) and verb_noun names (find_agent, pay_check, gate_check, list_metrics, canary_register), but the conventions remain readable and predictable.
25 tools is at the heavy end for the rubric, and the domain is rich enough to justify many of them, but the overlaps above suggest some tools could be consolidated (e.g. payee_facts as a subset of gate_check). Borderline over-scoped rather than clearly well-scoped.
The surface is unusually broad: metric discovery/definitions/history, agent lookup and records, ranking, detections, statements with proofs, sum-log verification, payment gating, and canary registration/status. Coverage looks close to complete for the stated domain; only minor gaps or unclear lifecycle edges keep it from a 5.