https://agentwares-agentcheck.vercel.app/api/mcp ↗
Synthetic checks, nightly regression replay and model-drift alerts for AI agents
agentcheck is a remote MCP server published at agentwares-agentcheck.vercel.app. It has been probed 6 times since 9/12/2026. It answered in 6 of them (100.0%), a near-uninterrupted record. Median response time is 362 ms, placing it among the faster endpoints. It offers a narrow, focused set of 8 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
agentcheck_get_pricing — Description only states purpose without explaining when/why to use it.agentcheck_create_target — Parameters like 'auth' have type 'null' and no required/optional clarification.agentcheck_add_check — No mention of error scenarios for invalid 'golden' validation rules.Risk: low
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
Tools the server advertised in the latest measurement — measured, not catalog-claimed.
agentcheck_get_statusCurrent status of a public monitored target: overall state, uptime over 24h/7d/30d, last check time, last nightly scores, open incidents and the badge/status URLs. Use the owner (GitHub login) and target slug from the status page URL https://agentwares-agentcheck.vercel.app/<owner>/<slug>. No API key needed.
ownerstringrequiredslugstringrequiredagentcheck_get_pricingMachine-readable pricing for agentcheck: tiers with monthly USD price, target limits, check interval and features, plus per-run add-ons. Same data as /pricing.json. No API key needed.
agentcheck_create_targetEnroll something to monitor: an http endpoint (JSON or OpenAI-style chat), a remote MCP server (Streamable HTTP url) or an A2A agent (origin with /.well-known/agent-card.json). Pass `checks` to create checks in the same call (POST /api/v1/probe proposes three). Returns the target id, the public status page, the badge SVG URL and a README snippet. The first check runs on the next minute tick; call agentcheck_run_now to run immediately. Free tier: 1 target, hourly; Starter+: 5-minute checks. Requires an API key.
namestringslugstringkindstringrequiredurlstringpackageSpecstringagentCardUrlstringformatstringheadersobjectauthmodelVarstringmodelHeaderstringcorpusUrlstringalertsobjectisPublicbooleanchecksarrayagentcheck_add_checkAdd a check to one of your targets. A check runs an input (http path/prompt, mcp tool call, a2a message) on a schedule and judges the answer with a golden: exact, contains, regex and json_schema cost nothing; rubric and baseline use the LLM judge (baseline = same outcome as the last known-good answer). Returns the check id. Requires an API key.
namestringrequiredkindstringrequiredinputobjectgoldenobjectrequiredintervalSecintegertargetIdstringrequiredagentcheck_run_nowRun every check of one of your targets immediately (outside the schedule) and return pass/fail per check with latency, judge cost and any incident opened or closed. Use it right after enrolling, or to confirm a fix. Requires an API key.
targetIdstringrequiredagentcheck_recordRecord one production interaction with your agent (the prompt or messages, the final answer, the tools it called, optionally the model) as a trace on a target. Call it from your agent or from a proxy in front of it after each task; promote a good trace with agentcheck_promote_trace to replay it nightly and catch regressions. Requires an API key.
targetIdstringrequirednamestringinputrequiredoutputstringrequiredtoolCallsarraymodelstringagentcheck_promote_traceTurn an imported or recorded trace into a replayable check whose golden is the recorded outcome (tool sequence + final-answer rubric). The check runs daily and in the nightly replay (Pro). Returns the check. Requires an API key.
traceIdstringrequiredagentcheck_list_incidentsOpen and recent incidents across your targets (or one target): when they opened/closed, the failing check and the cause. Requires an API key.
targetIdstringDerived by comparing consecutive probes — changes in era, protocol version, build and reachability.
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/io-github-agentwares-agentcheck)<a href="https://mcpmetrics.io/servers/io-github-agentwares-agentcheck"><img src="https://mcpmetrics.io/badge/io.github.agentwares/agentcheck/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to seeThe catalog entries whose name and description are closest to this one, found with the same index the search box uses.
Dead-man switch for AI agents & cron jobs: heartbeat with state capsule, alerts + resume links
Validate tax IDs, IBANs, emails, and phones. Screen entities against sanctions lists (OFAC, EU, UK, UN). Verify companies, inspect domains, and run composite trust screens. Create accounts, check usage, and propose new capabilities. Free tools (tax-id, IBAN, email syntax, phone format, Chilean indicators) work without an API key. Paid checks need a funded MadTaco account — authenticate with your API key via X-Api-Key. Every response includes credits_charged; failed checks are never billed. Setup: madtaco.dev/mcp API docs: madtaco.dev/docs Pricing: madtaco.dev/pricing.json
Persistent memory and drift detection for AI agents across session restarts.
Signed drift reports for the ai-agents-for-beginners course. Free summary; $0.25 full report.
Monitor MCP servers, API contracts and AI outputs for schema drift. Alerts on breaking changes.
Behavioral drift context (Behavioral Load Map, hot paths, release brief) for coding agents, per PR.
| Run | Era | Modern | ms | Legacy | ms | Versions |
|---|---|---|---|---|---|---|
| 2026-09-13 01:33:33 | Legacy | 400 | 421 | 200 | 398 | 2025-11-25 |
| 2026-09-12 23:31:36 | Legacy | 400 | 376 | 200 | 729 | 2025-11-25 |
| 2026-09-12 21:29:15 | Legacy | 400 | 362 | 200 | 345 | 2025-11-25 |
| 2026-09-12 19:27:29 | Legacy | 400 | 218 | 200 | 235 | 2025-11-25 |
| 2026-09-12 17:24:09 | Legacy | 400 | 325 | 200 | 337 | 2025-11-25 |
| 2026-09-12 15:21:42 | Legacy | 400 | 483 | 200 | 214 | 2025-11-25 |
Each block is one measurement round. Green: working response. Amber: responded but the server was returning errors (5xx). Red: no response at all.
Each cell is one probe run. Faded cells are incomplete probes — one leg did not answer, so the era is inconclusive.
The two probe legs separately: modern server/discover and legacy initialize.
Comments
Sign in to write a comment
No comments yet. Be the first.