Is com.edgethirteen.www/cloakcheck up? Live MCP status
No, it is not answering as an MCP server. HTTP 404.
The endpoint did not answer as an MCP server: HTTP 404. Do not spend a call on it.
| Outcome | unreachable |
|---|---|
| HTTP status | 404 |
| Answered in | 127 ms |
| Endpoint checked | https://www.edgethirteen.com/api/mcp/cloakcheck |
| Checked |
One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.
Live status every few hours: Wellknown
Email me when this server changes
That was one look. To hear when it stops answering or its tools change, leave an address.
Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.
Monthly census, 6 October 2026
The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one was not an MCP server at that address (HTTP 404). Every listing’s result: index.ndjson (what the files hold: index.meta.json).
Agent discovery documents at this origin
| A2A agent card | Not published (HTTP 404)./.well-known/agent-card.json |
|---|---|
| MCP server card (SEP-2127) | Not published (HTTP 404).https://www.edgethirteen.com/api/mcp/altman-z-score-calculator/server-card (the one endpoint per origin the census asks, not this listing’s) |
| MCP server card (SEP-1649 location) | Not published (HTTP 404)./.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026 |
| Web Bot Auth key directory | Not published (HTTP 404)./.well-known/http-message-signatures-directory |
Read at https://www.edgethirteen.com with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.
Tool changes between snapshots
It is not in the 2026-10 snapshot. Snapshots record the tool list of every listing that answered a stock client with no credential in that month’s census.
Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.
The listing
| Registry name | com.edgethirteen.www/cloakcheck |
|---|---|
| Description | Scan a page for content planted to hijack an AI browsing/shopping agent before it acts on the page. |
| Endpoint | https://www.edgethirteen.com/api/mcp/cloakcheck |
| Publisher repository | none listed |
| Version | 1.0.0 |
| Listing updated |
Also
The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt