Epovest
v1.0.0With Epovest, businesses make AIs recommend them.
Endpoint health
online- Last checked
- 11/20/2026, 6:17:44 AM
- Latency
- 285 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:com.epovest%2Fai-visibility
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"com.epovest/ai-visibility": {
"url": "https://mcp.epovest.com/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
25 shown · authentication unknown
Accept discovered suggestions
accept_keyword_discovery
Accept one discovered suggestion (domain) or a batch (domains): each becomes a tracked keyword of the tracker, in place, and its series starts at the next survey. Refused with keyword_cap_reached when the batch would exceed the keyword cap, and with not_found when a domain is not currently suggested (the batch is all-or-nothing, nothing is added then). The answer carries keyword for a single domain, keywords for a batch. Accept on behalf of the user only when they said yes.
Schema valid · SHA-256 b2ee159d0113…
View input schema
{ "type": "object", "properties": { "tracker_id": { "type": "string", "format": "uuid", "description": "The UUID of the tracker: call list_trackers to find it." }, "domain": { "type": "string", "description": "One domain to act on, exactly as listed by list_keyword_discoveries. Send this OR domains, never both." }, "domains": { "type": "array", "items": { "type": "string" }, "description": "Several domains to act on in one call, each exactly as listed by list_keyword_discoveries. Send this OR domain, never both. ALL-OR-NOTHING: one invalid domain refuses the whole batch, so you never have to guess which half took." } }, "required": [ "tracker_id" ] }Add a check of your own to the checklist of a surface
add_surface_check
Add a check of your own to the checklist of one surface: a requirement the person holds on THAT page, in their words. It becomes REQUIRED for the page to count as aligned, exactly like the canon items of the template, and it is ticked with tick_surface_checklist at the key returned here. Reach for it whenever the person states something a page must carry that is theirs to decide: the pricing block quotes the canon boilerplate, the OG image is the current one, the footer carries the legal name, the pinned post links to the launch page. restates_canon is the one judgement to make, and the question is simple: does the tick become FALSE when the wording of the canon changes? True for a check that restates the canon, and its verification then perishes with the wording, putting the page back in the queue; false, the default, for a check that constates anything else, and the tick then stands until someone clears it. Sending the same label again returns the check already there, and brings it back from the trash if it was in it, so a replay never duplicates. Up to 20 checks on a surface.
Connections
streamable-http
https://mcp.epovest.com/mcp