Skip to main content
Glama
ReportProof MCP Server

ReportProof MCP Server

by vikyathhj-ui

Related Servers

Alternatives to ReportProof MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to verify claims deterministically by computing arithmetic, ratios, and dates and matching statements against provided sources, returning a confidence ladder of certain, source-backed, or unverifiable.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude to run nine marketing calculations on real public data — A/B test evaluation and planning, email campaign analysis, budget simulation and optimization, store sales breakdowns, RFM customer segmentation, lead funnel analysis, and multi-model attribution comparison. It connects without an account and returns a short summary plus structured numbers so decisions rest on computed results rather than guesses.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides exact, deterministic tools for math, dates, units, validation, and more to AI agents, returning precise answers with explicit assumptions and warnings instead of model guesses.
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables plain-language growth marketing maths (CAC, LTV, ROAS, PPC forecasts, budgets, CLV and ecommerce metrics) alongside SEO and AI-visibility checks such as robots.txt AI-crawler audits, JSON-LD schema and meta tag generation. It is free, read-only and needs no authentication or API key.
      2
      29
      3
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides accurate SaaS metrics calculations (LTV, CAC, runway, health score, etc.) with formulas and interpretations for AI agents and founders, ensuring no hallucinated numbers.
      MIT

    TDQS

    A3.6/5.0

    Scored across 3 tools

    Disambiguation3/5

    check_report and verify_report both validate a draft report and differ only in data source (raw source data vs. a metrics object from compute_metrics), which is a subtle boundary an agent can easily cross. The descriptions do state when to use each, but the near-synonymous names 'check' and 'verify' increase misselection risk. compute_metrics is clearly distinct.

    Naming Consistency5/5

    All three tools follow a clean verb_noun snake_case pattern: check_report, verify_report, compute_metrics. The convention is uniform and predictable, even if check/verify are semantically close.

    Tool Count4/5

    Three tools is a tight, well-scoped surface for a narrow report-proofing purpose. However, check_report and verify_report are close enough that one could arguably be folded into the other, making the set feel slightly redundant rather than minimal.

    Completeness4/5

    The compute-then-verify/check lifecycle covers the core workflow: derive exact metrics, then validate a draft against either raw data or computed metrics. Minor gaps exist (e.g., no way to fetch or inspect the source data itself, or to re-check only flagged lines), but agents can work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues