Should my agent depend on the MCP server com.epovest/ai-visibility?

Verdict: allow — rich-slow-solo — safe to depend on As of 2026-08-15T11:28:18Z: a dated observation with receipts, not a warranty.

Epovest

com.epovest/ai-visibility

With Epovest, businesses make AIs recommend them.

— the operator's own registry description reported

Publisher com.epovest · first seen 2026-08-12 · endpoint https://mcp.epovest.com/mcp

allow

verdict

rich-slow-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — rich-slow-solo — safe to depend on

Cluster rich-slow-solo · distinctiveness 0.527 (moderate). Every figure is a percentile or class within the 11,094-server census — see the whole spectrum.

Reach — can an agent get to it?

answersalive_tools

latency415 ms

vs populationslow

protocolcurrent

authopen

Use — can it use it?

tools66

vs populationhigh

capabilities1

harnessA

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_8a074a81d10ab9cc6986acf2 · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Tools last seen

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_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

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band A — an agent can pick and call these reliably.

legibility check	tools passing	ok
name is clear & specific	66/66	✓
has a description	66/66	✓
description is substantive	66/66	✓
parameters are typed	66/66	✓
parameters are described	65/66	65/66

66 of 66 tools graded · 66 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18

protocol version

—

session model

1.0.0

server version epovest

Capabilities: tools

Drift

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (2 events)

date	type	what changed
2026-08-14	inventory	tools 61 → 66
2026-08-12	outcome	first probe: ok_tools

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-14T19:58:06Z	ok_tools	200	415	2025-06-18
2026-08-12T05:33:21Z	ok_tools	200	208	2025-06-18

Watch or embed this verdict

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/com.epovest/ai-visibility.svg)](https://robinsaige.com/s/com.epovest/ai-visibility)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview