Skip to main content
Glama

Ground Truth

Live fact-checking tools for AI agents.

Ground Truth gives AI agents read-only verification tools for live public data: free endpoint reachability checks, free security-header inspection, pricing-page scans, pricing-page comparisons, evidence-backed claim checks, package-market sizing, compliance scans, named package comparisons, and multi-step hypothesis tests.

You can use Ground Truth three ways:

  • Free endpoint and security-header checks for lightweight verification

  • Agentic pay-per-use with x402-compatible clients or an xpay proxy

  • A team subscription with X-API-Key billing and predictable monthly usage

MCP Cloudflare Workers ground-truth-mcp MCP server

Live: https://ground-truth-mcp.anishdasmail.workers.dev


Try This First

These two tools work without signup or an API key:

  • check_endpoint: verify that a public URL or API endpoint responds.

  • inspect_security_headers: inspect HSTS, CSP, frame protections, and related browser-facing security headers.

Example prompts:

  • "Use Ground Truth to check whether https://api.github.com responds."

  • "Use Ground Truth to inspect security headers for https://example.com."

  • "Before recommending this API, use Ground Truth to verify the endpoint is reachable."


Related MCP server: Demaciains MCP Server

What Ground Truth Verifies

Ground Truth helps agents check facts before they answer, recommend, or act.

Verification

What it checks

Example

Pricing claims

Pulls live pricing from product pages

"Does Stripe have a free tier?"

Pricing comparisons

Compares multiple pricing pages side by side

"Which vendor shows a free trial right now?"

Compliance posture

Scans trust pages for enterprise signals

"Does this vendor mention SOC 2, GDPR, and SCIM?"

Security posture

Inspects browser-facing security headers

"Does this app expose HSTS and CSP?"

Competitor existence

Checks whether real alternatives show up in npm or PyPI

"Are there edge-first Prisma alternatives?"

API endpoints

Confirms a URL exists and responds

"Does this endpoint return 200?"

All results come from live data and are cached for 5 minutes for faster repeat checks.


Complementary MCP Servers

Ground Truth is strongest when paired with a broader discovery or browser tool:

  • Tavily MCP Server for real-time web search and content discovery before you run a claim or pricing check.

  • Firecrawl MCP Server for deeper crawling and JS-heavy page extraction when raw HTML heuristics are not enough.

  • mcp-server-browserbase for interactive browser verification on pages that need clicks, auth, or client-side rendering.

These are complementary to Ground Truth rather than substitutes: they help you find or render the page, while Ground Truth helps you verify the resulting claim.

If you are filling in Glama related servers for this project, start with these three:

  • Tavily MCP Server

  • Firecrawl MCP Server

  • mcp-server-browserbase


Why AI Agents Need Verification

Training data goes stale. Docs change. Pricing changes. Competitors appear. Endpoints break. Policies move.

Ground Truth gives agents a way to check before they commit:

  • Before quoting a price, pull the live pricing page

  • Before comparing vendors, scan their live pricing pages side by side

  • Before repeating a compliance claim, scan the live trust page

  • Before asserting a security baseline, inspect the response headers

  • Before saying a competitor does not exist, search the live registry

  • Before recommending an API, confirm the endpoint responds

  • Before calling one package more popular, compare real package metadata

  • Before repeating a policy, verify the language on the current public page

The result is simple: agents that are less confident for the wrong reasons and more reliable when it matters.


Example Workflows

Verify a pricing claim

"Notion costs $8 per user per month for teams."

Use check_pricing on the live pricing page before repeating the number.

Check whether a competitor exists

"There is no good edge ORM alternative to Prisma."

Use estimate_market to search npm for edge orm and see what already exists.

Compare vendor pricing pages

"Vendor A is cheaper than Vendor B."

Use compare_pricing_pages to compare live pricing pages before repeating the claim.

Scan a trust page

"This vendor supports SOC 2, GDPR, and SCIM."

Use assess_compliance_posture before treating that as current fact.

Inspect browser-facing security headers

"This app has a strong public security baseline."

Use inspect_security_headers before making the claim.

Validate an API endpoint

"Use the OpenAI /v1/models endpoint to list available models."

Use check_endpoint before recommending it in docs, code, or support replies.

Compare package popularity

"Vue has overtaken React."

Use compare_competitors to compare live package metadata instead of guessing.

Test a market assumption

"There are fewer than 50 MCP tools on npm."

Use test_hypothesis with a count-based check and return the actual result.

Confirm whether a support policy applies

"AWS Business support includes 24/7 phone support."

Use verify_claim against the current AWS support page before treating that as fact.


Access Modes

Free

Free tier includes limited monthly endpoint and security-header checks.

  • check_endpoint

  • inspect_security_headers

  • 100 requests per calendar month

  • Tracked by Cloudflare client IP in production, or X-Anonymous-Client-Id for local/dev testing

  • No signup or API key required

Agentic pay-per-use

Paid tools also support agentic pay-per-use.

  • Use an x402-compatible MCP client, or put an xpay MCP proxy in front of this server

  • Tool pricing starts at $0.01 per call and varies by tool

  • Best for autonomous agents or variable workloads

  • Includes estimate_market, check_pricing, compare_pricing_pages, compare_competitors, verify_claim, assess_compliance_posture, and test_hypothesis

Team

Team subscription uses API-key billing with predictable monthly usage.

  • Requires X-API-Key with active billing

  • Default quota of 5,000 requests per calendar month

  • Monthly usage tracked per API key and tool

  • Includes all paid verification tools

View pricing


API Examples

Direct API with curl

Direct HTTP calls to /mcp are session-based. Initialize once, keep the returned mcp-session-id, then call tools with that header.

The examples below use the team plan with X-API-Key. For agentic pay-per-use, use an x402-capable MCP client or put an xpay proxy in front of this server.

SESSION_ID="$(curl -i -s -X POST https://ground-truth-mcp.anishdasmail.workers.dev/mcp \
  -H "Accept: application/json, text/event-stream" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "method": "initialize",
    "params": {
      "protocolVersion": "2025-03-26",
      "capabilities": {},
      "clientInfo": {
        "name": "ground-truth-example",
        "version": "1.0.0"
      }
    },
    "id": 0
  }' | tr -d '\r' | awk '/^mcp-session-id:/ {print $2}')"

curl -X POST https://ground-truth-mcp.anishdasmail.workers.dev/mcp \
  -H "Accept: application/json, text/event-stream" \
  -H "Content-Type: application/json" \
  -H "Mcp-Session-Id: $SESSION_ID" \
  -H "X-API-Key: $GROUND_TRUTH_API_KEY" \
  -d '{
    "jsonrpc": "2.0",
    "method": "tools/call",
    "params": {
      "name": "check_pricing",
      "arguments": {
        "url": "https://stripe.com/pricing"
      }
    },
    "id": 1
  }'

JavaScript fetch

const initResponse = await fetch("https://ground-truth-mcp.anishdasmail.workers.dev/mcp", {
  method: "POST",
  headers: {
    "Accept": "application/json, text/event-stream",
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    jsonrpc: "2.0",
    method: "initialize",
    params: {
      protocolVersion: "2025-03-26",
      capabilities: {},
      clientInfo: {
        name: "ground-truth-example",
        version: "1.0.0",
      },
    },
    id: 0,
  }),
});

const sessionId = initResponse.headers.get("mcp-session-id");

if (!sessionId) {
  throw new Error("Missing mcp-session-id from initialize response");
}

const response = await fetch("https://ground-truth-mcp.anishdasmail.workers.dev/mcp", {
  method: "POST",
  headers: {
    "Accept": "application/json, text/event-stream",
    "Content-Type": "application/json",
    "Mcp-Session-Id": sessionId,
    "X-API-Key": process.env.GROUND_TRUTH_API_KEY,
  },
  body: JSON.stringify({
    jsonrpc: "2.0",
    method: "tools/call",
    params: {
      name: "compare_competitors",
      arguments: {
        packages: ["react", "vue"],
        registry: "npm",
      },
    },
    id: 1,
  }),
});

const result = await response.json();
console.log(result);

Free endpoint check

curl -X POST https://ground-truth-mcp.anishdasmail.workers.dev/mcp \
  -H "Accept: application/json, text/event-stream" \
  -H "Content-Type: application/json" \
  -H "Mcp-Session-Id: $SESSION_ID" \
  -d '{
    "jsonrpc": "2.0",
    "method": "tools/call",
    "params": {
      "name": "check_endpoint",
      "arguments": {
        "url": "https://api.github.com"
      }
    },
    "id": 1
  }'

Lightweight request checks for free access, team-plan billing, invalid keys, inactive billing, quota enforcement, and active paid access live in test-usage-enforcement.sh.


MCP Setup

If you use Claude Desktop, Cursor, or another MCP client, Ground Truth can plug in as a verification tool for your agent.

MCP stands for Model Context Protocol. It is the standard that lets AI apps call external tools.

If you want agentic pay-per-use without changing your app code, register this MCP URL with xpay and share the resulting proxy URL instead.

Claude Desktop

Add this to ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "ground-truth": {
      "url": "https://ground-truth-mcp.anishdasmail.workers.dev/mcp",
      "headers": {
        "X-API-Key": "gt_live_your_key_here"
      }
    }
  }
}

Cursor

Add this to .cursor/mcp.json in your project or ~/.cursor/mcp.json globally:

{
  "mcpServers": {
    "ground-truth": {
      "url": "https://ground-truth-mcp.anishdasmail.workers.dev/mcp",
      "headers": {
        "X-API-Key": "gt_live_your_key_here"
      }
    }
  }
}

Claude Code skill

If you want the same workflow without running a server, see claude-skill/.


Use Cases

Support

  • Verify a pricing claim before sending it to a customer

  • Check whether a support policy applies before escalating

  • Confirm an API endpoint exists before recommending it in a reply

  • Inspect public security headers before repeating a security claim

Product

  • Test whether a market assumption is true before writing a spec

  • Check whether a competitor exists before framing a roadmap

  • Compare package popularity before making a platform choice

  • Compare pricing pages before telling a team one vendor is cheaper

Compliance

  • Scan trust pages for SOC 2, GDPR, HIPAA, DPA, SSO, and SCIM signals

  • Verify pricing or packaging claims before repeating them internally

  • Check that a public terms or policy URL is reachable and current

Security & vendor diligence

  • Compare competitor pricing across live pages

  • Inspect browser-facing security headers before recommending or approving a vendor

  • Validate positioning claims with structured checks


Tool Reference

Tool

Tier

What it does

check_endpoint

Free

Checks whether a URL or API endpoint exists and responds

estimate_market

Paid

Counts packages in npm or PyPI for a search term

check_pricing

Paid

Extracts prices, plans, and free-tier signals from a page

inspect_security_headers

Free

Checks common browser-facing security headers on a public URL

compare_pricing_pages

Paid

Compares multiple live pricing pages side by side

compare_competitors

Paid

Compares packages side by side with live metadata

verify_claim

Paid

Checks whether live sources support or contradict a claim

assess_compliance_posture

Paid

Scans a trust page for compliance and enterprise-security signals

test_hypothesis

Paid

Runs pass/fail tests against a live-data assumption

Full reference: API_USAGE.md


Architecture

Ground Truth keeps the current Cloudflare Workers architecture:

  • Runtime: Cloudflare Workers

  • Storage: Durable Objects with SQLite for cache and usage logs

  • API keys: Cloudflare KV

  • Billing: Stripe team subscriptions plus x402-compatible pay-per-use

  • Protocol: MCP

  • Language: TypeScript


Distribution

Ground Truth is set up for multiple discovery and monetization paths:

  • Official MCP Registry publishing through server.json for ecosystem-wide discovery.

  • Smithery URL publishing. This server exposes Streamable HTTP at /mcp and a static server card at /.well-known/mcp/server-card.json for metadata fallback.

  • xpay MCP monetization. You can register the live /mcp URL with xpay to get a managed pay-per-tool proxy without changing the server code.

  • MCP Market directory listing for additional discovery.

  • Apify is optional if you want a separate marketplace-native Actor version later; the current project stays optimized for remote MCP delivery rather than an Actor-first runtime.


Development

cd ground-truth-mcp
npm install
npx wrangler dev

Deployment notes live in SETUP.md.


GitHub Releases

Stable GitHub releases are created automatically when you push a version tag that matches v*.

git tag v0.4.0
git push origin v0.4.0

That tag triggers .github/workflows/release.yml, which typechecks the project and publishes a GitHub release from the tag. This is the repo-side piece Glama uses to detect stable releases during maintenance scans.


Glama Release

Glama releases are Docker-based, not GitHub releases. This repo includes a Dockerfile that starts the Worker locally through Wrangler on port 3000.

docker build -t ground-truth-mcp .
docker run --rm -p 3000:3000 ground-truth-mcp

For the Glama flow:

  1. Claim the server in Glama.

  2. Open the Dockerfile admin page, use this repository Dockerfile, and run the deploy test.

  3. After the deploy test succeeds, click Make Release, choose a version, and publish.

  4. If the score page still shows No LICENSE, trigger a re-scan in the Glama admin interface after GitHub has recognized the root LICENSE file.

  5. If the score page still shows No related servers, use Add related servers in the claimed Glama UI and add Tavily MCP Server, Firecrawl MCP Server, and mcp-server-browserbase. That checklist item is managed on Glama's side rather than in glama.json.

If Glama generates an mcp-proxy-based build spec instead of using the repository Dockerfile, point the command at npm run start:glama:stdio. That bridge exposes the existing remote Ground Truth MCP endpoint over stdio so mcp-proxy can host it.


Documentation


Support


License

MIT — see LICENSE


Made by Anish Das

Last updated: April 29, 2026

Available Tools

16 tools
assess_compliance_postureCompliance Signal ScanA
Read-onlyIdempotent
Inspect

Scan a public security, trust, compliance, or legal page for common enterprise buying signals before you claim a vendor supports a particular compliance posture. It looks for public references to SOC 2, ISO 27001, GDPR, HIPAA, DPA terms, subprocessors, SSO, SCIM, encryption, and data residency language. This is a signal scanner, not proof of certification or legal sufficiency.

Inputs: url (required). Returns: url, cached, matchedSignals, signals, +2 more

check_endpointEndpoint Reachability CheckA
Read-onlyIdempotent
Inspect

Perform one live, unauthenticated fetch against a public URL or API endpoint before you recommend it, document it, or build on top of it. Use this when the question is simply whether an endpoint currently responds and what kind of response it returns. It reports HTTP status, content type, elapsed time, likely auth/rate-limit signals, and a short response sample. A successful result only proves basic reachability at fetch time. Do not use it to validate authenticated flows, POST side effects, JavaScript execution, or deeper business logic.

Inputs: url (required). Returns: inputUrl, url, accessible, status, +6 more

check_pricingPricing Page ScanA
Read-onlyIdempotent
Inspect

Fetch a public pricing page and extract first-pass pricing signals before you quote plan costs, free tiers, or plan names. Use this when you already have a likely pricing URL and need a quick live scan of visible page text. It returns price-like strings, heuristic plan labels, free or free-trial signals, and cache information. It does not map prices to exact plans, normalize currencies, execute checkout flows, or guarantee that a price applies to a specific region or customer type. JavaScript-rendered, logged-in, or heavily obfuscated pricing details can be missed. Results are cached for 5 minutes.

Inputs: url (required). Returns: url, cached, pricesFound, plansDetected, +4 more

compare_competitorsNamed Package ComparisonA
Read-onlyIdempotent
Inspect

Compare two or more exact package names side by side using live npm or PyPI metadata. Use this when you already know the candidate packages and need evidence for claims such as 'tool A is newer', 'tool B is still maintained', or 'these packages use different licenses'. It returns per-package registry metadata in input order, with field availability varying by registry. Missing or unpublished packages return found=false. Do not use it to discover unknown alternatives, estimate market size, or compare packages across different registries. Registry responses are cached for 5 minutes.

Inputs: packages (required), registry. Returns: packages, registry, comparisons

compare_pricing_pagesPricing Page ComparisonA
Read-onlyIdempotent
Inspect

Compare two to five public pricing pages side by side before you make competitive pricing or packaging claims. Use this when you want a quick, live comparison of visible prices, free-plan signals, and plan-name hints across vendors. The output is heuristic and page-level: it does not map every price to every plan or normalize regional billing differences.

Inputs: pages (required). Returns: pages, summary

create_monitorCreate MonitorAInspect

Create a persistent monitor that tracks a URL, pricing page, package version, endpoint status, vendor claim, or custom keyword pattern over time. Monitors run automatically on their configured schedule (hourly/daily/weekly) via the Cloudflare cron trigger, or on demand with run_monitor_now. Results are stored in the Durable Object SQLite database. Requires a team API key.

Inputs: name (required), target_type (required), target_value (required), instructions, +2 more. Returns: id, name, target_type, target_value, +3 more

delete_monitorDelete MonitorA
DestructiveIdempotent
Inspect

Permanently delete a monitor and all its stored results. This action cannot be undone. Requires a team API key.

Inputs: monitor_id (required). Returns: monitor_id, deleted, results_deleted, error

estimate_marketPackage Market SearchA
Read-onlyIdempotent
Inspect

Search npm or PyPI to estimate how crowded a package category is before you claim that a market is empty, niche, or competitive. Use this when you have a category or search phrase such as 'edge orm' and want live result counts plus representative matches. Do not use it to compare exact known package names or to infer adoption from downloads; it reflects search results, not market share. Registry responses are cached for 5 minutes.

Inputs: query (required), registry. Returns: query, registry, totalResults, topResults

generate_change_reportGenerate Change ReportA
Read-onlyIdempotent
Inspect

Generate a summary report of monitor activity for a time window. Shows monitors run, changes detected, failures, risk levels, and recommended follow-up actions. Requires a team API key.

Inputs: period, include_unchanged. Returns: period, from, to, summary, +4 more

get_monitor_resultGet Monitor ResultsA
Read-onlyIdempotent
Inspect

Retrieve the most recent run results for a monitor, including change details, confidence score, evidence URLs, and any error information. Requires a team API key.

Inputs: monitor_id (required), limit. Returns: monitor_id, results, total, error

inspect_security_headersSecurity Header InspectionA
Read-onlyIdempotent
Inspect

Fetch a public URL and inspect security-relevant response headers before you claim that a product or endpoint has a strong browser-facing security baseline. Use this for quick due diligence on public apps and docs sites. It checks for common headers such as HSTS, CSP, X-Frame-Options, Referrer-Policy, Permissions-Policy, and X-Content-Type-Options. It does not replace a real security review, authenticated testing, or vulnerability scanning.

Inputs: url (required). Returns: inputUrl, url, accessible, status, +6 more

list_monitorsList MonitorsA
Read-onlyIdempotent
Inspect

List all monitors owned by this API key, with last run status and schedule. Requires a team API key.

Inputs: active_only. Returns: monitors, total, error

list_resourcesServer Resource DiscoveryA
Read-onlyIdempotent
Inspect

List all available Ground Truth tools and their access tiers. Zero-cost schema discovery. Call this to explore what verification tools are available before making a tool call. No quota consumption, no API key required.

Inputs: no named parameters. Returns: freeTools, paidTools, monitorTools, serverVersion

run_monitor_nowRun Monitor NowAInspect

Immediately run a monitor's verification check outside its normal schedule. Records the result and returns whether the observed value changed since the last run. Counts against your monthly quota. Requires a team API key.

Inputs: monitor_id (required). Returns: monitor_id, result_id, status, changed, +6 more

test_hypothesisMulti-step Hypothesis TestA
Read-onlyIdempotent
Inspect

Run a small verification plan made of concrete live checks and summarize whether a hypothesis is supported. Use this when one conclusion depends on multiple simple checks such as endpoint reachability, npm search counts, or whether a page contains an exact substring. This is a coordination tool, not an open-ended research agent: every test must be explicitly defined in advance, and tests run in order with no branching or early exit. The final verdict is mechanical: all tests passing => SUPPORTED, zero passing => REFUTED, otherwise PARTIALLY SUPPORTED. Use verify_claim when you already have evidence URLs, estimate_market for category sizing, and compare_competitors when you already know exact package names.

Inputs: hypothesis (required), tests (required). Returns: hypothesis, tests, verdict

verify_claimClaim Support CheckA
Read-onlyIdempotent
Inspect

Check whether a factual claim is supported by a specific set of public evidence URLs that you already have. For each source, the tool performs a case-insensitive keyword match over the fetched page body, then marks that source as supporting the claim when at least half of the supplied keywords appear. Use this for evidence-backed claim checks on known pages, not for open-ended search, semantic reasoning, or contradiction extraction. The aggregate verdict is driven only by the per-page keyword support ratio. Fetched pages are cached for 5 minutes.

Inputs: claim (required), evidence_urls (required), keywords (required). Returns: claim, sources, verdict

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.4/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each tool has a clearly defined purpose with minimal overlap. While some tools like verify_claim and test_hypothesis might seem similar, their descriptions distinctly separate them: verify_claim does keyword matching on given URLs, while test_hypothesis runs a small plan of varied checks. Other tools like check_pricing and compare_pricing_pages are also well-differentiated by scope.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., assess_compliance_posture, check_endpoint, list_monitors). There are no deviations or mixed conventions, making it easy for an agent to predict tool names.

    Tool Count5/5

    With 16 tools, the server covers a wide range of verification scenarios without being bloated. The count is well-scoped for the domain of ground truth checking, including monitoring, pricing, compliance, and endpoint verification.

    Completeness4/5

    The tool set is comprehensive for the stated purpose, covering most common verification needs. Minor gaps might include the absence of a tool for checking social proof or user reviews, but overall the surface covers the core workflows (monitoring, pricing, compliance, security headers, package comparison, and claim verification).

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      C
      maintenance
      This server enables AI systems to integrate with Tavily's search and data extraction tools, providing real-time web information access and domain-specific searches.
      4
      21,321 npm
      2,497
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides 19 AI-powered business intelligence tools for tasks such as SEO audits, company enrichment, and market analysis. These services are accessible through a pay-per-use model utilizing the x402 protocol on the Base network.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Trust layer for AI agents: 22 pay-per-call x402 tools for scam and fraud checks, payment pre-flight, wallet screening, policy approvals, contact extraction and company research. Free preview with no wallet; paid calls settle in USDC on Base.
      22
      80 npm
      MIT