Footnote
Related Servers
Alternatives to Footnote
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityCmaintenanceA deterministic MCP server that governs read-only queries across multiple data sources, returning answers with full provenance (every row cited) or a typed refusal, ensuring LLM answers are traceable and contract-enforced.1Apache 2.0- FlicenseNot gradedqualityCmaintenanceModel Context Protocol (MCP) server that gives AI assistants a safe, correct data-analyst capability over business metrics - without raw SQL improvisation.-
- FlicenseNot gradedqualityDmaintenanceA governed MCP server that enforces a trust layer between AI agents and databases, requiring sign-off on joins and metrics and producing auditable receipts for every query.-
- AlicenseAqualityDmaintenanceMCP server for deterministic numeric verification and spreadsheet auditing. Enables AI agents to verify math/finance claims, audit rows, and evaluate covenant rules with signed, independently checkable receipts.4MIT
- AlicenseNot gradedqualityDmaintenanceConfig-driven MCP server that gives AI scoped, auditable database access without exposing the entire database.3 npm6MIT
- AlicenseNot gradedqualityDmaintenanceCryptographic proof of every AI decision. An immutable, verifiable audit trail MCP server.1MIT
TDQS
Scored across 6 tools
The tools mostly target clearly distinct operations: customer summary, overdue invoices, payment history, open tickets, aging, and provenance verification. There is some conceptual overlap between getOverdueInvoices and getCustomerSummary because both can answer balance-related questions, but the descriptions distinguish detailed invoice-level debt from a general customer overview.
Five of the six tools follow a consistent getNoun phrase pattern in camelCase, such as getOverdueInvoices and getCustomerSummary. verifyProvenanceChain is a minor verb-style deviation, but it remains clear and readable.
Six tools is a well-scoped set for a focused accounts-receivable and customer-support query server. Each tool appears to earn its place without unnecessary surface area.
The surface covers the core read-only workflows for customer financial health, support context, portfolio aging, and provenance. Minor gaps could include customer search/list operations or more detailed invoice/ticket lookups, but the essential questions in this domain are addressable.