Is com.repondea/page-monitor 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 | 1236 ms |
| Endpoint checked | https://repondea.com/monitor/mcp |
| Redirected to | https://repondea.com/en/monitor/mcp |
| 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 wanted a credential (HTTP 401). Every listing’s result: index.ndjson (what the files hold: index.meta.json).
Agent discovery documents at this origin
| A2A agent card | Could not tell (fetch failed: 801ED4ED01000000:error:0A00010B:SSL routines:tls_validate_record_header:wrong version number:../deps/open…)./.well-known/agent-card.json |
|---|---|
| MCP server card (SEP-2127) | Could not tell (not asked: https://repondea.com did not answer the agent-card request).https://repondea.com/monitor/mcp/server-card |
| MCP server card (SEP-1649 location) | Could not tell (not asked: https://repondea.com did not answer the agent-card request)./.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026 |
| Web Bot Auth key directory | Could not tell (not asked: https://repondea.com did not answer the agent-card request)./.well-known/http-message-signatures-directory |
Read at https://repondea.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.repondea/page-monitor |
|---|---|
| Title | Repondea Page Monitor |
| Description | Read saved website changes, compare before and after, and cite source URLs and observation dates. |
| Endpoint | https://repondea.com/monitor/mcp |
| Publisher repository | none listed |
| Version | 0.1.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