mcp.epovest.com
https://mcp.epovest.com/
active Production-safe Score 96/100 http no auth
At a glance
| Endpoint | https://mcp.epovest.com/ |
|---|---|
| Source | https://epovest.com/ |
| Transport | http |
| Tools | 67 |
| Auth | none |
| First seen | 2026-09-13 15:21:03 |
| Last checked | 2026-11-17 21:52:12 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 241 / 389 ms |
| Last successful check | 2026-11-17 21:52:12 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (67)
list_trackers— List the trackers of the account, current versions: configuration, status, keywords, analysts, project and the recalculated cost per survey.create_tracker— Create a tracker in draft. It measures nothing yet: call start_tracker to launch it against the prepaid credit balance. Validation rules andupdate_tracker— Update the configuration of a tracker: only the fields you send change. Keywords, analysts and the title apply in place. Changing the promptstart_tracker— Start or restart the measurement of a tracker against the prepaid credit balance. The first survey runs there and then, whatever the frequensurvey_now— Run one survey of a measuring tracker right now, on top of its schedule. Its settings stay as they are: same anchor, same frequency, and thepause_tracker— Pause the measurement of an active tracker. The score series is kept; start_tracker resumes it.archive_tracker— File a finished tracker away: a campaign that ended, a brand that was sold, a trial that is over. It moves to the end of list_trackers withlist_projects— The projects of the account: the folders trackers are filed under (one project per tracker at most; pure organization, no effect on measuremcreate_project— Create a project to file trackers under: one project per BRAND, never per language. It can carry the brand canon: the reference wording everrename_project— Correct the name of a project: the folder keeps its id, its canon, its trackers, its surfaces and its logbook, and the name shown is the onlget_canon— The brand canon of a project and every revision it went through. canon is the CURRENT wording, under the same keys update_project_canon writupdate_project_canon— Revise the brand canon of a project. Field by field: a provided field replaces the current wording (an empty string clears it), an omitted fget_link_targets— The addresses of the brand that a watched page can link to. Two lists come back. derived: what is already covered without anyone typing it,set_link_targets— Set the addresses of the brand that are neither its canonical website nor a page of the surface registry: a satellite domain the customer doarchive_project— File a project away once the folder has served its purpose: a client that left, a brand that was sold. It moves to the end of list_projectslist_surfaces— The surface registry of a project: the pages about the brand where the customer has the FINAL SAY (website, GitHub, LinkedIn, X, YouTube, Wicreate_surface— Register a surface of a project: one page about the brand where the customer has the final say (their site, their profiles, their listings,update_surface— Update the registry sheet of a surface: only the fields you send change (a sent languages list replaces the previous one; an empty label ortick_surface_checklist— Record what a surface actually carries, cell by cell, as many moves as you want in one call. The items are listed by list_surfaces as checkladd_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 foupdate_surface_check— Correct a check of your own on a surface: its label, and whether it restates the canon. Only what you send changes. The key never moves, beidelete_surface_check— Take a check of your own out of the checklist of a surface: it leaves the list, stops holding the page short of aligned and stops acceptingrestore_surface_check— Bring a check of your own back to the checklist of a surface, with the cells it had: it becomes work again, so the page needs it verified todelete_surface— Take a surface out of the registry: the page stops being followed, and the registry stops asking to bring it in phase with the canon. Use itrestore_surface— Bring a surface back to the registry, with its sheet and its alignment journal as they were. Call list_surfaces with deleted set to "only" tconvert_surface_to_corroboration— Move the page to the corroboration registry: someone else has the final say on it (the customer lost, or never had, the hand on the content)list_corroborations— The corroborations recorded for a project: the pages about the brand where someone else has the FINAL SAY, each with its exact address, thecreate_corroboration— Record a page about the brand where someone else has the final say. URL-FIRST: the exact address of the page is the only thing needed, the supdate_corroboration— Update the sheet of a corroboration: only the fields you send change (an empty label goes back to the derived one, an empty notes or publisharchive_corroboration— Record that the page is no longer there (article unpublished, link dead), or put it back live with archived false. Nothing is deleted: the lverify_corroboration— Read the page again and report what it says today. One pass returns two findings, dated, and included at no cost. On the MENTION: the passagconvert_corroboration_to_surface— Move the page to the surface registry: the customer has, or takes, the final say on it (their own profile or listing recorded on the wrong slist_corroboration_candidates— The MENTIONS a search engine has shown the brand in, found in the text the engine itself returned next to each address. The list is recomputdismiss_corroboration_candidate— Refuse a suggested page: it is never proposed again for this project. Use it when the excerpt matched something else than the brand, or whenget_logbook— The logbook of a project, newest first: every dated move, composed from two sources. source=tool events are derived from the suite itself (ccreate_logbook_entry— Record an action in the logbook of a project: what was done, and WHEN it was done. occurred_at is the date of the ACTION itself, not of theupdate_logbook_entry— Edit a manual logbook entry: only the fields you send change (empty notes clear them). It is the customer's own logbook: a typo or a wrong ddelete_logbook_entry— Take a manual logbook entry out of the logbook, and the annotation it placed on the curves with it. Only do it when the user asked for it: irestore_logbook_entry— Bring an entry back to the logbook, with the annotation it placed on the curves. Call get_logbook with deleted set to "only" to find the entlist_quests— What there is to do for the GEO work, and where to resume it. Lists the quests of the account: moves the customer (or you, on their behalf)create_quest— Add a quest to the file of a project: a next move the customer decided, kept where the work resumes ("get our MCP server listed on the AI toupdate_quest— Edit a quest: only the fields you send change (empty notes clear them). It is the customer's own file: a typo or a sharpened wording is simpcomplete_quest— Mark a quest done: the move happened. Sets the state and the closing date; calling it again leaves it done, so a retry is safe, and a dismisdismiss_quest— Set a quest aside: the customer decided the move is off. Sets the state and the closing date; calling it again leaves it dismissed, so a retreopen_quest— Put a closed quest back in the file: it returns among the open moves with its sheet as it was, the date it was added, its author and its notget_results— The score series of a tracker: one row per analyst, keyword, engine, tracker version and survey period, in chronological order. Depending onget_responses— The raw answers of ONE AI engine for a tracker, newest surveys first, paginated. Every answer carries its cited sources and keyword mentionslist_keyword_discoveries— The keyword suggestions DISCOVERED on a tracker: domains the surveyed engines cite as sources again and again, that no tracked keyword coveraccept_keyword_discovery— Accept one discovered suggestion (domain) or a batch (domains): each becomes a tracked keyword of the tracker, in place, and its series stardismiss_keyword_discovery— Dismiss one discovered suggestion (domain) or a batch (domains): the domains are never proposed again on this tracker, and appear in the disrestore_keyword_discovery— Restore one dismissed domain (domain) or a batch (domains): it leaves the tracker dismissed list and becomes eligible for discovery again, slist_competitor_scans— The competitor scans of the account, newest first: a basket of up to 5 companies of one market, asked to one engine, from which the scan retget_competitor_scan— One scan and its list of PLACES: the domains the engine cited while answering about the basket, ranked by how many of its companies each placreate_competitor_scan— Prepare a competitor scan on a basket of up to 5 companies of the same market. Three or more is what the scan is built for: from there the pstart_competitor_scan— Arm a prepared scan: the engine is asked, and the prepaid balance is debited by the amount `estimated_cost_minor` announced on the scan. SPEupdate_competitor_scan— Correct a scan still in draft, and set the cadence of one already armed. `questions` is where the measurement is won: send the questions tolist_sources— The Atlas: the sources the AIs cite when they answer YOUR trackers. Each entry is a domain with its AI Authority on each AI, a 0 to 100 scalget_source— One entry of the Atlas, read by its id: the domain and its AI Authority on each AI. Call list_sources to find a source id, or to read the salist_source_channels— The channels behind one source of the Atlas: who published the videos the AIs cited when answering the questions of this account, with theirget_account_settings— The settings of the account: the legal name, billing country, postal address and intra-EU VAT number printed on its invoices, plus the langu
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:52:12 | ✓ | ✓ | 167 ms | 94 | active |
| 2026-11-17 21:36:59 | ✓ | ✓ | 345 ms | 91 | active |
| 2026-11-17 21:21:47 | ✓ | ✓ | 360 ms | 91 | active |
| 2026-11-17 21:06:37 | ✓ | ✓ | 164 ms | 94 | active |
| 2026-11-17 20:51:26 | ✓ | ✓ | 338 ms | 91 | active |
| 2026-11-17 20:36:25 | ✓ | ✓ | 162 ms | 94 | active |
| 2026-11-17 20:21:24 | ✓ | ✓ | 171 ms | 94 | active |
| 2026-11-17 20:06:23 | ✓ | ✓ | 334 ms | 91 | active |
| 2026-11-17 19:50:36 | ✓ | ✓ | 219 ms | 94 | active |
| 2026-11-17 19:35:28 | ✓ | ✓ | 343 ms | 91 | active |
| 2026-11-17 19:20:11 | ✓ | ✓ | 153 ms | 94 | active |
| 2026-11-17 19:04:52 | ✓ | ✓ | 379 ms | 91 | active |
| 2026-11-17 18:49:39 | ✓ | ✓ | 367 ms | 91 | active |
| 2026-11-17 18:34:28 | ✓ | ✓ | 176 ms | 94 | active |
| 2026-11-17 18:19:24 | ✓ | ✓ | 317 ms | 91 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://mcp.epovest.com/") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/mcp-epovest-com # JSON