agentcheck
REMOTE · AGENTWARES-AGENTCHECK.VERCEL.APP
Synthetic checks, nightly regression replay and model-drift alerts for AI agents
Available components
Last scanned (12 hours ago)
Scores higher than 74% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Testing and QA
Recent critical change
Authorization (9 Oct 2026). See the changelog before you install this server.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (agentcheck_create_target). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2255 tokens (~205/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 11 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 −1
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Nov 26 +1
- Stability: 0.97 → pass security
- 4 Nov 26 −1
- Stability: pass → 0.97 functional
- 10 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “agentcheck_api_sunsets” rewrote its description, which is the text the model reads security
- Schema quality: 2008 → 2255 ▼ functional
- Server version: 0.1.1 → 0.1.2 functional
- New tool “agentcheck_statuspage_preview” functional
- 9 Oct 26 0
- Authorization: unverified → fail ▼ critical
- Stability: 0.90 → pass security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “agentcheck_create_target” is now declared destructive security
- Schema quality: 1489 → 2008 ▼ functional
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- MCP protocol version: 2025-11-25 → 2026-07-28 functional
- New tool “agentcheck_api_sunsets” functional
- New tool “agentcheck_model_retirements” functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://agentwares-agentcheck.vercel.app/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.vercel.app | CN=WR1,O=Google Trust Services,C=US | 31 Oct 2026 | 29 Jan 2027 | RSA 2048 | SHA256-RSA | 9c5f0e6a35c955e113044c86848e4cd5 |
| SANs: *.vercel.app | ||||||
| CN=WR1,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7fd9e2c2d2048a0474b627a26d0868a7 |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of agentwares-agentcheck.vercel.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| app. | DS published | 23684 | 8 | Verified |
| vercel.app. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agentwares-agentcheck.vercel.app/api/mcp | Verified | 200 | |
| http (plaintext) | http://agentwares-agentcheck.vercel.app/api/mcp | HTTPS enforced | 308 | https://agentwares-agentcheck.vercel.app/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
agentcheck_add_check ~277
Add 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.
| Name | Type | Req | Description |
|---|---|---|---|
| golden | object | yes | how the answer is judged. exact / contains / regex / json_schema are free and deterministic; rubric and baseline call the LLM judge, and baseline compares against the last known-good answer. |
| input | object | – | http: { path?, method?, body?, prompt? } · mcp_tool_call: { tool, args } · a2a_task: { message } |
| intervalSec | integer | – | seconds between runs; the tier's interval is the floor (Free hourly, Starter+ 5 min) |
| kind | string | yes | what to run: http (GET path or POST prompt), mcp_tools_list, mcp_tool_call (tool + args), a2a_task (message) |
| name | string | yes | short name shown on the status page |
| targetId | string | yes | id from agentcheck_create_target or GET /api/v1/targets |
No output schema declared.
No examples provided.
agentcheck_api_sunsets ~333
When does the API version this code pins stop working, and what happens then? Pass provider and version pairs as your code pins them (shopify 2025-10, meta v21.0, google-ads v22, hubspot v1, twilio-flex 2.16.2, twilio-notify v1, keap xml-rpc, exchange-online ews, stripe 2024-06-20). For each, returns every dated end the provider's own versioning, changelog or retirement page lists: status, end date (and whether the provider gives only a month), what happens after it (error, silent fall-forward to another version, app delisting, or unsupported), whether the failure is silent, the replacement version, the source URL with the date it was read, and a page with the details. Where the provider's own pages give different dates for the same end, other_dates lists each one with its page and date_note says which the counts run to. A pair with no entry comes back with the reason: older than every listed version, no end date published yet, or a provider that publishes none (Stripe). Covers Shopify, HubSpot, Meta Graph and Marketing APIs, Google Ads and Content API for Shopping, Twilio Flex UI and Notify, Thryv's Keap XML-RPC, and Exchange Web Services (EWS) in Exchange Online. No API key needed.
| Name | Type | Req | Description |
|---|---|---|---|
| pins | array | yes | provider and version pairs, e.g. [{"provider": "shopify", "version": "2025-10"}] |
No output schema declared.
No examples provided.
agentcheck_create_target ~528
Enroll 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 scheduled tick, within five minutes; call agentcheck_run_now to run immediately. Free tier: 1 target, hourly; Starter+: 5-minute checks. Requires an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| agentCardUrl | string | – | a2a: explicit agent card URL when it is not at /.well-known/agent-card.json |
| alerts | object | – | where to send an incident when a check starts failing. Any combination; omit it and incidents are visible only on the status page. |
| auth | – | – | credential the prober sends to your endpoint: {type:'bearer',token} or {type:'header',name,value}. Stored encrypted and never returned or logged. |
| checks | array | – | checks to create right away (the probe proposes three) |
| corpusUrl | string | – | RAG targets: public corpus URL for the nightly groundedness scorer (Pro) |
| format | string | – | http: openai_chat (POST /chat/completions body), json (raw POST), get (plain fetch) |
| headers | object | – | extra request headers |
| isPublic | boolean | – | public status page + badge (default true) |
| kind | string | yes | http (JSON or chat endpoint), mcp (Streamable HTTP url, or npx/uvx package spec), a2a (agent card) |
| modelHeader | string | – | request header your endpoint accepts to override the model (drift re-runs try the new model) |
| modelVar | string | – | the model your agent runs on (e.g. claude-sonnet-5); enables model-drift re-runs |
| name | string | – | display name; defaults to the host |
| packageSpec | string | – | mcp only: `npx @org/server` / `uvx server` — runs on the mcpcheck runner, not the scheduled checks |
| slug | string | – | URL slug for /<owner>/<slug>; defaults to a slug of the name |
| url | string | – | endpoint URL (http/mcp) or the agent's origin (a2a) |
No output schema declared.
No examples provided.
agentcheck_get_pricing ~50
Machine-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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
agentcheck_get_status ~118
Current 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.
| Name | Type | Req | Description |
|---|---|---|---|
| owner | string | yes | GitHub login of the target's owner, e.g. demo |
| slug | string | yes | target slug, e.g. demo |
No output schema declared.
No examples provided.
agentcheck_list_incidents ~63
Open and recent incidents across your targets (or one target): when they opened/closed, the failing check and the cause. Requires an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| targetId | string | – | narrow to one target; omit for incidents across every target on the account |
No output schema declared.
No examples provided.
agentcheck_model_retirements ~225
Is this model retiring? Pass model IDs as your code or config names them (gpt-5-mini, claude-sonnet-4-5-20250929, gemini-2.5-flash, openai/o3-mini). For each, returns every announced shutdown on OpenAI's, Anthropic's and Google's own deprecation pages (OpenAI API, Claude API, Gemini API, Vertex AI): status, shutdown date, recommended replacement, the replacement's list-price ratio per token, the API changes the provider documents, the source URL with the date it was read, and a page with the details. retiring: false means no shutdown for that ID is on those pages. Language models only. No API key needed.
| Name | Type | Req | Description |
|---|---|---|---|
| models | array | yes | model IDs exactly as your code or config names them, e.g. ["gpt-5-mini", "claude-sonnet-4-5"]; router prefixes such as openai/ or models/ are ignored, and fine-tuned IDs (ft:…) match their base model |
No output schema declared.
No examples provided.
agentcheck_promote_trace ~84
Turn 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.
| Name | Type | Req | Description |
|---|---|---|---|
| traceId | string | yes | trace id from agentcheck_record or POST /api/v1/targets/{id}/traces |
No output schema declared.
No examples provided.
agentcheck_record ~191
Record 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.
| Name | Type | Req | Description |
|---|---|---|---|
| input | – | yes | the prompt, the messages array, or an object with prompt/messages |
| model | string | – | the model that produced this answer, so drift re-runs can compare across models |
| name | string | – | short label, e.g. 'refund for order A-1029' |
| output | string | yes | the agent's final answer |
| targetId | string | yes | id from agentcheck_create_target or GET /api/v1/targets |
| toolCalls | array | – | tool calls in order |
No output schema declared.
No examples provided.
agentcheck_run_now ~70
Run 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.
| Name | Type | Req | Description |
|---|---|---|---|
| targetId | string | yes | target id |
No output schema declared.
No examples provided.
agentcheck_statuspage_preview ~180
Read a public Atlassian Statuspage page once: its name, overall status, components (id, name, status, group) and unresolved incidents, from the page's own /api/v2/summary.json. Pass any address on the page: status.example.com, https://status.example.com/history or the JSON URL. Use it before POST /api/v1/statuspage, which turns the components you give a URL into a live agentcheck status page checked by agentcheck itself, with no signup; the answer carries that request's body. Same read as /statuspage/preview: only public addresses, 5-second timeout, 512 KB cap. Private pages cannot be read. No API key needed.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | the status page's address, e.g. https://status.example.com or its summary.json |
No output schema declared.
No examples provided.
How do I install the agentcheck MCP server?
agentcheck is a hosted endpoint at https://agentwares-agentcheck.vercel.app/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · agentwares-agentcheck.vercel.app
claude mcp add --transport http agentwares-agentcheck 'https://agentwares-agentcheck.vercel.app/api/mcp'
What is the agentcheck MCP server?
agentcheck is an MCP server listed in the public MCP registry as io.github.agentwares/agentcheck. Synthetic checks, nightly regression replay and model-drift alerts for AI agents. This page covers its hosted endpoint (https://agentwares-agentcheck.vercel.app/api/mcp).
Is the agentcheck MCP server safe to use?
agentcheck scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the agentcheck MCP server expose?
agentcheck exposes 11 tools: agentcheck_get_status, agentcheck_get_pricing, agentcheck_model_retirements, agentcheck_api_sunsets, agentcheck_statuspage_preview, and 6 more. Their descriptions and schemas cost roughly 2,119 tokens of context every time the server is loaded.
Does the agentcheck MCP server require authentication?
No. We connected to agentcheck without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the agentcheck MCP server still maintained?
agentcheck is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the agentcheck MCP server?
VerifyMCP ran 13 checks on agentcheck, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.