Is com.epovest/ai-visibility up? Live MCP status
Not checked just now. The live check did not run for this request (more than 120 status pages asked for a fresh check in the last minute). Reload in a minute; the monthly census result is below.
| Endpoint | https://mcp.epovest.com/mcp |
|---|---|
| Page built |
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 answered a stock client with no credential. 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://mcp.epovest.com/mcp/server-card |
| 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://mcp.epovest.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
In the 2026-10 snapshot it listed 67 tools: accept_keyword_discovery, add_surface_check, archive_corroboration, archive_project, archive_tracker, complete_quest, contact_support, convert_corroboration_to_surface, convert_surface_to_corroboration, create_competitor_scan, create_corroboration, create_logbook_entry, create_project, create_quest, create_surface, create_tracker, delete_logbook_entry, delete_surface, delete_surface_check, dismiss_corroboration_candidate, dismiss_keyword_discovery, dismiss_quest, get_account_settings, get_canon, get_competitor_scan, get_credits, get_link_targets, get_logbook, get_responses, get_results, get_source, get_support_thread, get_usage, list_competitor_scans, list_corroboration_candidates, list_corroborations, list_keyword_discoveries, list_projects, list_quests, list_source_channels, list_sources, list_support_threads, list_surfaces, list_trackers, pause_tracker, rename_project, reopen_quest, restore_keyword_discovery, restore_logbook_entry, restore_surface, restore_surface_check, set_link_targets, start_competitor_scan, start_tracker, survey_now, tick_surface_checklist, topup_credits, update_account_settings, update_competitor_scan, update_corroboration, update_logbook_entry, update_project_canon, update_quest, update_surface, update_surface_check, update_tracker, verify_corroboration.
No change to its tools between 2026-09 and 2026-10.
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.epovest/ai-visibility |
|---|---|
| Endpoint | https://mcp.epovest.com/mcp |
| Publisher repository | not known: the registry did not return this listing within 4 seconds |
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