Ground Truth First Tool Call
Smoke-test live URLs and keep optional scheduled endpoint checks with evidence history from your coding agent without wiring a full observability stack first.
Overview
Ground Truth is an Operate-phase MCP server that lets your agent call check_endpoint on live URLs, with optional API-key monitors and scheduled checks for ongoing evidence.
What is this MCP server?
- Run check_endpoint against any URL with no API key for the activation smoke test (e.g. https://example.com).
- Streamable HTTP MCP at ground-truth-mcp.anishdasmail.workers.dev with X-API-Key only for team and paid capabilities.
- Paid tier adds monitors, scheduled checks, and evidence history beyond one-off probes.
- Low-friction first tool call designed as “Ground Truth - First Tool Call” onboarding.
- Version 0.5.1 remote server schema 2025-12-11—no local clone required.
- MCP server version 0.5.1
- Primary free tool: check_endpoint (no API key for activation)
- Paid features: monitors, scheduled checks, evidence history
What problem does it solve?
After deploy you are not sure a URL or API is truly reachable from the outside, and ad-hoc curls in terminal do not stay in your agent workflow or history.
Who is it for?
Solo builders who want a zero-key smoke test of MCP monitoring, then light recurring URL checks tied to agent conversations.
Skip if: Teams needing deep APM, distributed tracing, log aggregation, or private-network-only probes without public HTTP targets.
What do I get? / Deliverables
Your agent can prove endpoints respond in one MCP call without a key, then optionally keep scheduled monitors and evidence once you add an API key.
- Confirmed MCP activation via check_endpoint on a chosen URL
- One-off reachability result usable in ship or operate checklists
- Optional ongoing monitors with scheduled checks and evidence when keyed
Recommended MCP Servers
Journey fit
Endpoint verification, recurring monitors, and historical evidence are production concerns after you ship, not ideation or greenfield build work. The server centers on check_endpoint plus monitors and scheduled checks—classic uptime and health monitoring in the operate phase.
How it compares
HTTP endpoint monitoring MCP, not an in-repo testing skill or full observability platform.
Common Questions / FAQ
Who is Ground Truth for?
Indie and solo builders using Claude Code, Cursor, or Codex who want agent-driven URL health checks before investing in heavier monitoring tools.
When should I use Ground Truth?
Right after deploy or when debugging “is it live?”—start with check_endpoint without a key, then add monitors when you need scheduled checks and evidence history.
How do I add Ground Truth to my agent?
Register the streamable-http remote https://ground-truth-mcp.anishdasmail.workers.dev/mcp in your MCP client, run check_endpoint with a public url, and set X-API-Key only for paid team features.