# Epovest (remote · mcp.epovest.com)

With Epovest, businesses make AIs recommend them.

- Trust score: 78/100 (medium)
- Change this week: +8
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.epovest.com`: 78/100 (this document), [markdown](https://verifymcp.io/servers/com-epovest-ai-visibility/mcp.md), [page](https://verifymcp.io/servers/com-epovest-ai-visibility/mcp)

## Channel facts

- Endpoint: `https://mcp.epovest.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 97/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 54/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 15125 tokens (~252/item across 60 items; 60 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 24/100
  - Stability check failed: schema churn in the 8 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 11 additions.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 99% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### Claude

```bash
claude mcp add --transport http com-epovest-ai-visibility https://mcp.epovest.com/mcp
```

### Codex

```toml
[mcp_servers.com-epovest-ai-visibility]
url = "https://mcp.epovest.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-epovest-ai-visibility": {
      "type": "remote",
      "url": "https://mcp.epovest.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-epovest-ai-visibility --url https://mcp.epovest.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-epovest-ai-visibility:
    url: "https://mcp.epovest.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-epovest-ai-visibility": {
      "type": "http",
      "url": "https://mcp.epovest.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 78, −2)

- [functional] Schema quality: excellent → good
- [functional] New tool “rename_project”

### 2026-08-02 (score 80, +5)

- [security improvement] Authorization: partial → pass
- [functional regression] Schema quality: excellent → unverified
- [functional improvement] MCP protocol: fail → pass

### 2026-07-31 (score 75, +6)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 69, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 70, −1)

- [security regression] Stability: 0.07 → fail
- [security regression] A breaking change shipped without a version bump: still 1.0.0
- [security regression] Tool “mark_surface_aligned” was removed
- [security] Tool “update_surface” rewrote its description, which is the text the model reads
- [security] Tool “create_surface” rewrote its description, which is the text the model reads
- [security] Tool “list_quests” rewrote its description, which is the text the model reads
- [security] Tool “list_surfaces” rewrote its description, which is the text the model reads
- [security] Tool “tick_surface_checklist” rewrote its description, which is the text the model reads
- [functional] Schema quality: excellent → good
- [cosmetic] “get_responses” added an optional parameter “tone”
- [cosmetic] “tick_surface_checklist” reworded the description of “ticks”
- [cosmetic] Tool “tick_surface_checklist” changed its title: Tick the checklist of a surface → Verify or set aside checklist cells of a surface

### 2026-07-28 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 70, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 70)

First indexed and scored.

## MCP tools (60)

### `list_trackers` (~122 tokens)

List trackers

List the trackers of the account, current versions: configuration, status, keywords, analysts, project and the recalculated cost per survey. Start here to find a tracker id. Filter by project with project_id. The ones still followed come first, then the ones filed away (archive_tracker), each with archived true and its archived_at.

Input parameters:

- `project_id` (string): Only the trackers of this project: the UUID of a project of the account (call list_projects), or "default" for the trackers without a project. Omitted, every tracker is listed.

### `create_tracker` (~412 tokens)

Create a tracker

Create a tracker in draft. It measures nothing yet: call start_tracker to launch it against the prepaid credit balance. Validation rules and messages are the same as the app configurator. Omitted, next_survey_at means the first survey runs at start_tracker.

Input parameters:

- `analysts` (array): The lenses that score every survey. keyword_presence and share_of_voice are deterministic; sentiment and custom_prompt are AI analysts billed per analyzed response.
- `custom_prompt` (string): The instruction of the custom_prompt analyst. Required when that analyst is selected.
- `discovery` (boolean): Suggest new keywords spotted in the answers.
- `engines` (array, required): The AI engines surveyed.
- `frequency` (string, required): How often a survey runs.
- `keywords` (array): Names to detect in the answers: your brand and the names you compare against. Flag yours as favorite.
- `next_survey_at` (string): When the next survey runs, ISO 8601, strictly in the future; read as UTC without an offset. Later surveys keep that day and time at the pace of the frequency.
- `notify_on_survey` (boolean): Email the account owner and managers each time a survey closes with fresh data, so the results reach them on their own. Off by default.
- `project_id` (string): The project the tracker is filed under: the UUID of a project of the account (call list_projects), or "default" for none. Pure organization, editable at any time. Omitted on creation the tracker file…
- `prompts` (array, required): The questions asked to the AI engines at every survey, phrased exactly as a customer would ask them.
- `resolution` (string, required): Repetitions of every question per engine and survey: hd=1, full_hd=3, 4k=6, 8k=9. Answers are stochastic; more repetitions sharpen the rates.
- `title` (string, required): Display name of the tracker.

### `update_tracker` (~455 tokens)

Update a tracker

Update the configuration of a tracker: only the fields you send change. Keywords, analysts and the title apply in place. Changing the prompts, engines, frequency or resolution of a tracker that has measured creates a new version: the score series continues across versions, and the response carries the new tracker id (version_created says when). A sent list replaces the previous one entirely.

Input parameters:

- `analysts` (array): The lenses that score every survey. keyword_presence and share_of_voice are deterministic; sentiment and custom_prompt are AI analysts billed per analyzed response.
- `custom_prompt` (string): The instruction of the custom_prompt analyst. Required when that analyst is selected.
- `discovery` (boolean): Suggest new keywords spotted in the answers.
- `engines` (array): The AI engines surveyed.
- `frequency` (string): How often a survey runs.
- `keywords` (array): Names to detect in the answers: your brand and the names you compare against. Flag yours as favorite.
- `next_survey_at` (string): When the next survey runs, ISO 8601, strictly in the future; read as UTC without an offset. Later surveys keep that day and time at the pace of the frequency.
- `notify_on_survey` (boolean): Email the account owner and managers each time a survey closes with fresh data, so the results reach them on their own. Off by default.
- `project_id` (string): The project the tracker is filed under: the UUID of a project of the account (call list_projects), or "default" for none. Pure organization, editable at any time. Omitted on creation the tracker file…
- `prompts` (array): The questions asked to the AI engines at every survey, phrased exactly as a customer would ask them.
- `resolution` (string): Repetitions of every question per engine and survey: hd=1, full_hd=3, 4k=6, 8k=9. Answers are stochastic; more repetitions sharpen the rates.
- `title` (string): Display name of the tracker.
- `tracker_id` (string, required): The UUID of the tracker: call list_trackers to find it.

### `start_tracker` (~66 tokens)

Start a tracker

Start or restart the measurement of a tracker against the prepaid credit balance. Refused with insufficient_credits when the balance does not cover one survey. Starting an already active tracker changes nothing.

Input parameters:

- `tracker_id` (string, required): The UUID of the tracker: call list_trackers to find it.

### `survey_now` (~163 tokens)

Survey a tracker 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 the next scheduled survey keeps its date. It debits the prepaid credit balance like any survey, and the point joins the score series marked on_demand. The answer carries the survey id: read the results back with get_results, or the raw answers with get_responses. While one is still running, calling again answers that survey instead of starting a second one. Refused with insufficient_credits when the balance does not cover it, and with tracker_not_active when the tracker is not measuring yet: start_tracker first.

Input parameters:

- `tracker_id` (string, required): The UUID of the tracker: call list_trackers to find it.

### `pause_tracker` (~48 tokens)

Pause a tracker

Pause the measurement of an active tracker. The score series is kept; start_tracker resumes it.

Input parameters:

- `tracker_id` (string, required): The UUID of the tracker: call list_trackers to find it.

### `archive_tracker` (~179 tokens)

File a tracker away

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 with archived true, stops asking for anything, and its measurement pauses in the same call if it was still running, so the spending stops there. Bring it back with archived false: the tracker returns to the list as it was, and start_tracker restarts the measurement when the user asks for it. The sheet and the score series are kept and stay readable throughout (get_results answers as usual). Filing away an already filed tracker answers the same.

Input parameters:

- `archived` (boolean): true files the tracker away and pauses its measurement, false brings it back. Omitted, it files it away.
- `tracker_id` (string, required): The UUID of the tracker: call list_trackers to find it.

### `list_projects` (~91 tokens)

List projects

The projects of the account: the folders trackers are filed under (one project per tracker at most; pure organization, no effect on measurement or billing). Each carries its id, name, brand canon with its current version number (canon_version), archived flag and tracker count. The folders still in use come first, then the ones filed away (archive_project). Trackers without a project live under the virtual Default project.

### `create_project` (~590 tokens)

Create a project

Create a project to file trackers under: one project per BRAND, never per language. It can carry the brand canon: the reference wording every publication reuses as is, written in ONE language, its canonical language (carried at creation, it is recorded as canon version 1). The canon is never translated: localized expressions on the pages are outputs, not a second canon. Nothing is filed by this call: pass the returned id as project_id when creating or updating a tracker. Refused with project_exists when a project with this name already exists, and the answer carries the existing project: reuse its id instead of duplicating.

Input parameters:

- `canon_address` (string): Postal address, as written on a listing. Language-neutral: the same string everywhere, like the other facts.
- `canon_category` (string): Category label for listings and structured data.
- `canon_email` (string): Public email address of the brand.
- `canon_language` (string): Short code of the ONE language the canon is written in, like "en" or "pt-br". The canonical language settles every language call (the llms.txt of a multilingual site is written in it). It travels WIT…
- `canon_legal_name` (string): Registered name of the company that operates the brand, with its jurisdiction when the user states it ("Acme Holdings, LLC, Delaware, United States"). Language-neutral, like the other facts: the AIs…
- `canon_long` (string): The two-sentence version, when the surface allows it.
- `canon_one_liner` (string): One-sentence signature of the brand.
- `canon_perks` (array): The distinctive claims of the brand, in the order they should be hammered, written in the canonical language. Facts that hold and can be corroborated ("works without a subscription"), never superlati…
- `canon_phone` (string): Phone number, international prefix included.
- `canon_short` (string): THE one-sentence description third-party pages reuse as is.
- `canon_website` (string): The canonical address of the brand website, the one that identifies the entity. A bare domain is enough ("example.com" completes to "https://example.com"). ONE URL only: the other addresses of the br…
- `canon_whatsapp` (string): WhatsApp number, international prefix included.
- `name` (string, required): Name of the project, as the user calls it (a client, a brand, a website...).

### `rename_project` (~199 tokens)

Rename a 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 only thing that changes. Names are unique per account: a name another project already goes by answers project_exists with that project, so read it back and settle another name with the user. Case, accents and spacing do not make two different names, which is why a project can always take back its own capitalisation. Sending the name it already carries answers the same, and a project filed away renames like any other. Use it for the name of the folder; the wording of the brand itself is the canon, and it moves with update_project_canon.

Input parameters:

- `name` (string, required): The name the project takes, as the user calls it (a client, a brand, a website...).
- `project_id` (string, required): UUID of the project: call list_projects to find it.

### `update_project_canon` (~586 tokens)

Update the canon of a project

Revise the brand canon of a project. Field by field: a provided field replaces the current wording (an empty string clears it), an omitted field is kept as is. Any actual change records the NEXT canon version (numbered, immutable; version_created true in the answer); sending identical wording records nothing. The canon lives in ONE language, its canonical language (canon_language): it is never translated, changing the language is a revision like any other. The canon is meant to be STABLE: revising it is a rare and deliberate move, and every surface that reuses the wording will need to be brought back in phase with the new version. Confirm with the user before revising.

Input parameters:

- `canon_address` (string): Postal address, as written on a listing. Language-neutral: the same string everywhere, like the other facts.
- `canon_category` (string): Category label for listings and structured data.
- `canon_email` (string): Public email address of the brand.
- `canon_language` (string): Short code of the ONE language the canon is written in, like "en" or "pt-br". On a project whose canon is not posted yet, send it with at least one wording: the canon is the wording, and the language…
- `canon_legal_name` (string): Registered name of the company that operates the brand, with its jurisdiction when the user states it ("Acme Holdings, LLC, Delaware, United States"). Language-neutral, like the other facts: the AIs…
- `canon_long` (string): The two-sentence version, when the surface allows it.
- `canon_one_liner` (string): One-sentence signature of the brand.
- `canon_perks` (array): The distinctive claims of the brand, in the order they should be hammered, written in the canonical language. Facts that hold and can be corroborated ("works without a subscription"), never superlati…
- `canon_phone` (string): Phone number, international prefix included.
- `canon_short` (string): THE one-sentence description third-party pages reuse as is.
- `canon_website` (string): The canonical address of the brand website, the one that identifies the entity. A bare domain is enough ("example.com" completes to "https://example.com"). ONE URL only: the other addresses of the br…
- `canon_whatsapp` (string): WhatsApp number, international prefix included.
- `project_id` (string, required): UUID of the project: call list_projects to find it.

### `get_link_targets` (~182 tokens)

List the addresses of the brand a link can point to

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, each row with its source, "canon" (the canonical website of the brand) or "surface" (a page of the surface registry: the site, the LinkedIn or X profile, a directory listing, an app store page). free: the addresses set on the project on top of those. Read it before setting anything: an address already derived does not need to be added, and the derived list is what the customer gets for free from work already done. A link towards any of these is what the reading pass reports on, with its rel tokens, its anchor, its destination and its place on the page.

Input parameters:

- `project_id` (string, required): UUID of the project: call list_projects to find it.

### `set_link_targets` (~182 tokens)

Set the free addresses of the brand

Set the addresses of the brand that are neither its canonical website nor a page of the surface registry: a satellite domain the customer does not want to keep aligned, a tracking link, a partner page. They are set ONCE for the project and serve every line of the corroboration registry, present and future, so there is nothing to set line by line. The list you send REPLACES the previous one, and the answer returns what the project now holds, derived addresses included: read it back to confirm. An empty list keeps only the derived ones. Call get_link_targets first, and confirm with the user before replacing.

Input parameters:

- `link_targets` (array, required): The FULL list of the free addresses, as absolute http(s) URLs. It replaces the previous one.
- `project_id` (string, required): UUID of the project: call list_projects to find it.

### `archive_project` (~203 tokens)

File a project away

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_projects with archived true, and stops being offered when filing a tracker. Bring it back with archived false. Nothing is deleted and nothing cascades: the trackers filed under it keep their status, keep measuring and keep showing up in list_trackers, and the answer carries tracker_count, how many are still filed under it, so you can go on with archive_tracker on each one when that is what the user meant. Filing away an already filed project answers the same. Default is where trackers without a folder live: it has no id, so this tool always takes the UUID of a project of the account.

Input parameters:

- `archived` (boolean): true files the project away, false brings it back. Omitted, it files it away.
- `project_id` (string, required): UUID of the project: call list_projects to find it.

### `list_surfaces` (~799 tokens)

List the surfaces of a project

The surface registry of a project: the pages about the brand where the customer has the FINAL SAY (website, GitHub, LinkedIn, X, YouTube, Wikidata, directories, app stores...). The split with corroborations is control, never who wrote the page: a page the customer can change is a surface, a page where someone else has the final say is a corroboration (list_corroborations). Each surface carries its type, url, label, languages, notes, its checklist and a status DERIVED from the checklist CELLS that hold it: checklist.required lists exactly those, the canon items of the template plus every check the customer added of their own. checklist.kinds answers a different question, what PERISHES a tick: "canon" items restate the canon, so their verification perishes when the wording moves; "presence" ones, such as site_link, hold. A check of the customer holds the status whatever its kind, so read checklist.required and deduce nothing from checklist.kinds. checklist.custom lists those checks, each with its key, label, scope and restates_canon, and the ones taken out with deleted true, which restore_surface_check brings back; add_surface_check is how a new one is posed. Each cell is verified (dated, stamped with the canon version whose WORDING it restated: it stays fresh until the wording moves, and a revision that touches no wording, such as declaring the canonical language, perishes nothing) or set aside with its reason (the item does not apply on THIS surface). Three statuses, never a fourth: aligned when every required cell not set aside is verified at the current wording; needs_update when some verification is missing or stale; never_aligned when none exists. There is no state for a page the canon does not apply to, because setting aside the LAST canon cell is refused with not_a_surface, because a page that carries none of the canon is not a surface: turn it into a corroboration if someone else has the final say on it, or take it out of the registry. checklist.state keeps…

Input parameters:

- `deleted` (string): Set to "only" for the surfaces taken out of the registry (delete_surface), most recently taken out first, each with its deleted_at. Omitted, the registry is listed.
- `project_id` (string, required): UUID of the project: call list_projects to find it.
- `sort` (string): Order of the registry. "registry", the default, is the order of the binder, by shown name, the one where a known line is found again. "authority" orders by the measured authority of the DOMAIN of eac…

### `create_surface` (~325 tokens)

Register a 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, wherever they can change the content). URL-FIRST: the url is the only thing needed, type and label are derived from it; pass them only to correct a derivation. It is born never_aligned: bring the page in phase with the canon, then record what it carries with tick_surface_checklist, cell by cell. The aligned status DERIVES from those verifications and is never declared: verifying the last canon cell aligns the surface on its own.

Input parameters:

- `label` (string): Display name of the surface. OMIT IT on creation: it is derived from the url (the handle on a known place, the host and path on a website).
- `languages` (array): Languages of the surface, as short codes like "en" or "pt-br". A sent list replaces the previous one.
- `notes` (string): Free registry notes: who owns the account, access, context.
- `project_id` (string, required): UUID of the project: call list_projects to find it.
- `type` (string): What kind of surface this is; it picks the checklist to come. OMIT IT on creation: the type is derived from the url by the catalogue of places (github.com is GitHub, an unknown host is the brand webs…
- `url` (string, required): Absolute http(s) address of the surface.

### `update_surface` (~368 tokens)

Update a 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 or notes clears it). No journal line is ever written here: an alignment is earned with tick_surface_checklist, cell by cell. Languages ARE the columns of the checklist, so declaring the language of a single-language page renames its column and carries its verified cells along. When the change leaves no single destination (a language dropped from a page that keeps others, one column split into several), the columns that leave the model come back in dropped_checklist_columns with what they held; their cells stay stored, and declaring the language again brings them back. The status of the answer is derived from the cells that read NOW, so read it back rather than assuming it held.

Input parameters:

- `label` (string): Display name of the surface. OMIT IT on creation: it is derived from the url (the handle on a known place, the host and path on a website).
- `languages` (array): Languages of the surface, as short codes like "en" or "pt-br". A sent list replaces the previous one.
- `notes` (string): Free registry notes: who owns the account, access, context.
- `surface_id` (string, required): The UUID of the surface: call list_surfaces to find it.
- `type` (string): What kind of surface this is; it picks the checklist to come. OMIT IT on creation: the type is derived from the url by the catalogue of places (github.com is GitHub, an unknown host is the brand webs…
- `url` (string): Absolute http(s) address of the surface.

### `tick_surface_checklist` (~518 tokens)

Verify or set aside checklist cells of a surface

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 checklist.items: the template of the surface type (stable keys such as title_tag or llms_txt), then the checks the customer added of their own (add_surface_check), which tick here exactly like the rest, at their key. Most of them are yours to check (a title tag, JSON-LD, an llms.txt all read with a simple fetch). Three moves per cell. VERIFY (done true, or nothing): the item is constated on the page; an item of canon kind (checklist.kinds) is stamped with the current canon version and wording, so its verification stays fresh until the wording moves, and needs the canon set first. SET ASIDE (dismissed true plus a short reason): the item does not apply on THIS surface (an author bio, a field the platform does not offer); durable across canon revisions, reversible, never hidden from the counts. CLEAR (done false, or dismissed false): the cell returns to blank. A site-wide item (checklist.site_items: the llms.txt, one file at the root of the site, written in the canonical language of the project) is one cell for the whole site, without a language. Only the cells you send change; an unknown item or language, a set-aside without reason or a contradictory move refuses the whole batch and says what exists. The ALIGNED status derives from the cells listed in checklist.required, the canon items plus the checks of the customer: verifying the last one aligns the surface and dates it in the journal. The goal is a surface with no required cell left undecided: work every one of them to a verdict, verified when the page carries it or set aside with a reason when the item does not apply here. Leaving a cell untouched is not a neutral skip, it holds the surface in needs_update and hides whether the page was ever checked, so go through the whole checklist and not only the cells easy to confirm. And setting aside the LAST canon cell is refused, because…

Input parameters:

- `surface_id` (string, required): The UUID of the surface: call list_surfaces to find it.
- `ticks` (array, required): The cell moves. Nothing else on the checklist changes.

### `add_surface_check` (~391 tokens)

Add a check of your own to the checklist of a surface

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.

Input parameters:

- `label` (string, required): What the check says, as the person would read it on their checklist: one line, up to 120 characters ("The FAQ block quotes the canon boilerplate").
- `restates_canon` (boolean): true when the check restates the WORDING of the canon, so its verification perishes when the wording moves. false by default, for a check that constates something else.
- `scope` (string): How many cells the check gets: "language" by default, one per language of the surface; "site" for what exists once for the whole site whatever the number of languages.
- `surface_id` (string, required): The UUID of the surface: call list_surfaces to find it.

### `update_surface_check` (~195 tokens)

Correct a check of your own

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, being the coordinate of the cells already recorded, so renaming a check keeps every tick it carries. Turning restates_canon on makes a tick recorded without a canon stamp perish, which is the honest reading: the page was never checked against a wording.

Input parameters:

- `check` (string, required): The key of the check of your own, exactly as listed by list_surfaces in checklist.custom (add_surface_check returns it too).
- `label` (string): The new wording of the check, up to 120 characters.
- `restates_canon` (boolean): true when the check restates the WORDING of the canon, false when it constates something else.
- `surface_id` (string, required): The UUID of the surface: call list_surfaces to find it.

### `delete_surface_check` (~158 tokens)

Take a check of your own out of a checklist

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 accepting ticks. Use it when the requirement no longer applies to that page. Nothing is lost: the check and the cells it carries are kept, read back in checklist.custom with deleted true, and restore_surface_check brings both back, so a check taken out by mistake costs nothing. Taking out an already taken out check answers the same.

Input parameters:

- `check` (string, required): The key of the check of your own, exactly as listed by list_surfaces in checklist.custom (add_surface_check returns it too).
- `surface_id` (string, required): The UUID of the surface: call list_surfaces to find it.

### `restore_surface_check` (~130 tokens)

Bring a check of your own back to a checklist

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 to count as aligned. The checks to bring back are listed by list_surfaces in checklist.custom, with deleted true. Restoring a check already in the checklist answers the same.

Input parameters:

- `check` (string, required): The key of the check of your own, exactly as listed by list_surfaces in checklist.custom (add_surface_check returns it too).
- `surface_id` (string, required): The UUID of the surface: call list_surfaces to find it.

### `delete_surface` (~122 tokens)

Take a surface out of the registry

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 it for a page that is gone (account closed, listing removed) or for a line that had no place there. The sheet and the alignment journal are kept, and restore_surface brings the surface back with them, so a line taken out by mistake costs nothing. Taking out an already taken out surface answers the same.

Input parameters:

- `surface_id` (string, required): The UUID of the surface: call list_surfaces to find it.

### `restore_surface` (~79 tokens)

Bring a surface back to the registry

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" to find the surfaces to bring back. Restoring a surface already in the registry answers the same.

Input parameters:

- `surface_id` (string, required): The UUID of the surface: call list_surfaces to find it.

### `convert_surface_to_corroboration` (~172 tokens)

Move a surface to the corroboration registry

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). Nothing is retyped: url, label and notes travel, the publication date stays unknown (set it with update_corroboration when known). The surface leaves its registry for the trash, alignment journal attached, and the reverse move exists (convert_corroboration_to_surface): nothing is lost, and replaying the move finds the same line instead of duplicating it. The own site of the brand is refused (own_domain): it stays a surface. It moves a line the customer declared: confirm with the user first.

Input parameters:

- `surface_id` (string, required): The UUID of the surface: call list_surfaces to find it.

### `list_corroborations` (~174 tokens)

List the corroborations of a project

The corroborations recorded for a project: the pages about the brand where someone else has the FINAL SAY, each with its exact address, the source it sits on (domain), the publication date when known, and free notes. Live ones first, then the ones taken down (archived true). The twin registry of Surfaces, where the customer has the final say: the split is control, never who wrote the page or who paid for it. Asking such a source for a change stays a normal move; record the outcome in the logbook. What comes back is what the customer DECLARED: the registry is theirs to fill, and list_corroboration_candidates proposes pages the engines already showed the brand on.

Input parameters:

- `project_id` (string, required): UUID of the project: call list_projects to find it.

### `create_corroboration` (~387 tokens)

Record a 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 source on the map and the display name are derived from it. It is a statement of fact: only record a page you have actually read, and confirm with the user. A page the customer controls (their own profile, their own listing) belongs to Surfaces instead: use create_surface. Three refusals answer with their own slug: unplaceable_url (the address has no registrable domain), own_domain (this is the own site of the brand, where they have the final say: use create_surface), duplicate (the page is already in the registry, 409).

Input parameters:

- `label` (string): Display name of the page. OMIT IT: it is derived from the address (domain and path). Send an empty string to go back to the derived one.
- `notes` (string): Free notes: the passage that mentions the brand, the contact, how the page came about.
- `project_id` (string, required): UUID of the project: call list_projects to find it.
- `published_on` (string): The day the page was PUBLISHED, as YYYY-MM-DD. Distinct from the recording day, and the one that means something against the citation curves. Omit it when unknown: it is never guessed.
- `request_channel` (string): Whether someone can be asked to change the page: "available" (a contact or a process exists), "none" (nobody to ask), "unknown" (not filled in, the default). It gates the refresh suggestions of the q…
- `url` (string, required): Absolute http(s) address of the EXACT page where the third party talks about the brand, never the home page of the site.

### `update_corroboration` (~488 tokens)

Update a 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 published_on clears it). Correcting the url ALWAYS recomputes the source: the two never drift apart. It also carries monitoring, the cadence at which the page is read again on its own, which is why watching a page needs no tool of its own. To say a page is gone, use archive_corroboration instead: editing never takes anything down.

Input parameters:

- `corroboration_id` (string, required): The UUID of the corroboration: call list_corroborations to find it.
- `label` (string): Display name of the page. OMIT IT: it is derived from the address (domain and path). Send an empty string to go back to the derived one.
- `monitoring` (string): How often the page is read again on its own: "off" (the default), "daily", "weekly" or "monthly". Each executed check costs 0.02 USD from the prepaid balance and returns the same two findings as veri…
- `notes` (string): Free notes: the passage that mentions the brand, the contact, how the page came about.
- `published_on` (string): The day the page was PUBLISHED, as YYYY-MM-DD. Distinct from the recording day, and the one that means something against the citation curves. Omit it when unknown: it is never guessed.
- `request_channel` (string): Whether someone can be asked to change the page: "available" (a contact or a process exists), "none" (nobody to ask), "unknown" (not filled in, the default). It gates the refresh suggestions of the q…
- `url` (string): Absolute http(s) address of the EXACT page where the third party talks about the brand, never the home page of the site.

### `archive_corroboration` (~141 tokens)

Take a corroboration down, or put it back live

Record that the page is no longer there (article unpublished, link dead), or put it back live with archived false. Nothing is deleted: the line stays, and so does the history, because "they talked about us from March to July" is information. A page taken down stops counting as a presence on that source. Only take down after actually re-reading the address and finding it gone.

Input parameters:

- `archived` (boolean): true takes the page down, false puts it back live. Omitted, it takes it down.
- `corroboration_id` (string, required): The UUID of the corroboration: call list_corroborations to find it.

### `verify_corroboration` (~497 tokens)

Check a corroboration against its page, now

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 passage around the brand is archived on the line (the sentence that names it, one before, one after), and the finding says unchanged, changed (the passage moved, worth re-reading), figures (the passage moved on NUMBERS only, such as a rank or a counter: a fact to read, and changed_at stays where it was) or gone (the page did not answer). When a change was found, excerpt_before carries the passage as it stood BEFORE changed_at: compare it with excerpt to state what moved, in words, without reading the whole page. On the LINK: every link of the page towards an address of the brand, derived from the canon website and from the surface registry of the project, with its rel tokens (nofollow, sponsored, ugc, or none), its target and title attributes, its anchor text, its exact destination with the resolved redirect chain and the HTTP code of that destination, whether it sits in the main content or outside it, and its dates; the finding says unchanged, changed (changes lists what moved: rel, anchor, target, placement, appeared), gone, or none, which means the page carries no such link and is a normal state. The reply also carries how the page reads (readability: "html" when it reads, "blocked" when an anti-bot stands in front of it, "unreachable" when it did not answer, "no_page" when the address answers with something that is not a page, "unreadable" when it answers HTML with no text in it, "pending" while no reading has completed yet), the number of outbound links of the page, and what the page declares about itself (noindex, page_nofollow, canonical_elsewhere). Read readability before deciding a move: an anti-bot is a fact of the world, while a page that did not answer is worth reading again. Everything here is a FACT: the third party has the final say, so nothing closes, nothing counts, and nothing is taken down on its own. Use it to dec…

Input parameters:

- `corroboration_id` (string, required): The UUID of the corroboration: call list_corroborations to find it.

### `convert_corroboration_to_surface` (~164 tokens)

Move a corroboration to the surface registry

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 side, or a source that became a reliable channel). Nothing is retyped: url, label and notes travel, the publication date is copied into the notes, the type derives from the address. The corroboration is taken down, sheet intact, and the reverse move exists (convert_surface_to_corroboration): nothing is lost, and replaying the move finds the same line instead of duplicating it. It moves a line the customer declared: confirm with the user first.

Input parameters:

- `corroboration_id` (string, required): The UUID of the corroboration: call list_corroborations to find it.

### `list_corroboration_candidates` (~370 tokens)

List pages where the engines showed the brand

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 recomputed on every read from the raw payloads of the latest surveys, and surveys_scanned says how many were read. Pages already filed in either registry (corroborations or surfaces) are left out. Each row carries the excerpt as proof, matched_by ("website" means the full domain of the brand appears in it, near proof; "name" means only the name did, weaker, homonyms exist: read the page before recording) and suggested: the registry the filing is proposed in ("surface" when the host is a known profile place, a page the customer usually has the final say on; "corroboration" otherwise). Once the page itself has been read, the row also carries page_check: result is "website" or "name" when the page carries the brand, "absent" when the page reads without it, and it names the cause when the text did not come: "blocked" (an anti-bot stands in front of the page), "unreachable" (the page did not answer), "no_page" (the address answers with something that is not a page), "unreadable" (the page answers HTML with no text in it). In those four the engine excerpt above stays the proof shown. excerpt is a full passage taken from the page, and checked_at dates the reading. It is a suggestion, never a filing: to file one, call create_corroboration or create_surface with its url; to refuse one, dismiss_corroboration_candidate.

Input parameters:

- `project_id` (string, required): UUID of the project: call list_projects to find it.

### `dismiss_corroboration_candidate` (~135 tokens)

Refuse a 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 when the page is not worth recording. Nothing is created or deleted. Accepting is the opposite move and has no tool of its own: call create_corroboration with the url of the candidate, or create_surface when the page is one the customer controls.

Input parameters:

- `project_id` (string, required): UUID of the project: call list_projects to find it.
- `url` (string, required): The address of the candidate, exactly as list_corroboration_candidates gives it.

### `get_logbook` (~302 tokens)

Read the logbook of a project

The logbook of a project, newest first: every dated move, composed from two sources. source=tool events are derived from the suite itself (canon moved to a version, surface marked aligned, corroboration recorded); source=manual entries are actions the customer recorded (only these carry an id, a category, a label and notes). Each move also lands as an annotation on the citation curves of the trackers of the project: read the logbook to tell what was done when the curves moved. On a corroboration item, occurred_at is the PUBLICATION date when known and the recording date otherwise: published_on sits next to it, and it tells which of the two dates the move carries. Set deleted to "only" to read the trash of the logbook instead of it.

Input parameters:

- `category` (string): Only the manual entries of this category (tool events carry no category and never match).
- `deleted` (string): Set to "only" for the entries taken out of the logbook (delete_logbook_entry), most recently taken out first, each with its deleted_at. It carries recorded entries only, so it goes without source and…
- `project_id` (string, required): UUID of the project: call list_projects to find it.
- `source` (string): Only the items of this source: "tool" for suite events, "manual" for recorded entries. Omitted, both.

### `create_logbook_entry` (~322 tokens)

Record an action in the logbook

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 the recording: recording after the fact is the normal case ("record: site translated into Spanish yesterday" means occurred_at is yesterday). The entry joins the tool events in the logbook and lands as an annotation on the citation curves of the trackers of the project, so the action can be read against the measures. Recording is idempotent on the project, the label and occurred_at: calling again with the same three returns the entry already recorded instead of a second copy, so a retry is safe. The same move recorded in two languages has two labels, so it stays two entries.

Input parameters:

- `category` (string, required): What kind of action this is; it files the entry for filtering. "other" covers anything else.
- `label` (string, required): Short wording of the action, e.g. "Site translated into Spanish": it is what the annotation shows next to the citation curves.
- `notes` (string): Free notes: context, links, details of the action.
- `occurred_at` (string): When the action HAPPENED, ISO 8601 date or datetime, read as UTC without an offset. Distinct from the recording time: when the user says "yesterday" or "last week", compute and pass that date. Omitte…
- `project_id` (string, required): UUID of the project: call list_projects to find it.

### `update_logbook_entry` (~237 tokens)

Edit a 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 date is simply corrected. Tool events cannot be edited: they are derived from the canon and surface registries.

Input parameters:

- `category` (string): What kind of action this is; it files the entry for filtering. "other" covers anything else.
- `entry_id` (string, required): The UUID of the logbook entry: call get_logbook to find it (only manual entries carry an id).
- `label` (string): Short wording of the action, e.g. "Site translated into Spanish": it is what the annotation shows next to the citation curves.
- `notes` (string): Free notes: context, links, details of the action.
- `occurred_at` (string): When the action HAPPENED, ISO 8601 date or datetime, read as UTC without an offset. Distinct from the recording time: when the user says "yesterday" or "last week", compute and pass that date. Omitte…

### `delete_logbook_entry` (~116 tokens)

Delete a 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: it is their logbook. The entry waits in the trash, so restore_logbook_entry brings it back with its annotation. Tool events stay as they are: they are derived from the canon and surface registries.

Input parameters:

- `entry_id` (string, required): The UUID of the logbook entry: call get_logbook to find it (only manual entries carry an id).

### `restore_logbook_entry` (~90 tokens)

Bring a logbook entry back

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 entries to bring back. Restoring an entry already in the logbook answers the same.

Input parameters:

- `entry_id` (string, required): The UUID of the logbook entry: call get_logbook to find it (only manual entries carry an id).

### `list_quests` (~297 tokens)

Read the quest file

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) decided and recorded, open by default, newest first; status=done or dismissed reads the closed history, which answers with its quests, each one reopened with reopen_quest. Every project by default; scope to one project with project_id. Alongside the open file, `pending` carries the files the measurement is holding for review, each acted through its own tool: surfaces whose canon moved since their last alignment (list_surfaces, then tick_surface_checklist to verify the cells the new wording perished), keyword discoveries waiting on a tracker (list_keyword_discoveries, then accept_keyword_discovery or dismiss_keyword_discovery). Scoped to one project, `pending` also carries the corroboration candidates of that project, computed per project (list_corroboration_candidates, then create_corroboration or dismiss_corroboration_candidate). An empty file with the measurement running means there is nothing to correct today.

Input parameters:

- `project_id` (string): Only the file of this project: the UUID of a project of the account (call list_projects). Omitted, the file covers every active project.
- `status` (string): Which quests to list: "open" (the file, default), "done" or "dismissed" (the closed history).

### `create_quest` (~193 tokens)

Add a 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 tool directories"). title says the move; notes carry context and links. Adding is idempotent on the project and title while the quest is open: calling again returns the quest already in the file instead of a second copy, so a retry is safe. A closed quest with the same title does not block: doing the move again later is a new quest, with its own history.

Input parameters:

- `notes` (string): Free notes: context, links, what done looks like.
- `project_id` (string, required): UUID of the project whose file takes the quest: call list_projects to find it.
- `title` (string, required): Short wording of the move, e.g. "Get our MCP server listed on the AI tool directories": it is what the file shows.

### `update_quest` (~136 tokens)

Edit a 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 simply corrected. The status changes through its own moves, complete_quest, dismiss_quest and reopen_quest.

Input parameters:

- `notes` (string): Free notes: context, links, what done looks like.
- `quest_id` (string, required): The UUID of the quest: call list_quests to find it.
- `title` (string): Short wording of the move, e.g. "Get our MCP server listed on the AI tool directories": it is what the file shows.

### `complete_quest` (~105 tokens)

Complete a 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 dismissed quest that was done after all becomes done (the last move is what the file remembers). The quest stays readable in the closed history of list_quests, and reopen_quest puts it back in the file.

Input parameters:

- `quest_id` (string, required): The UUID of the quest: call list_quests to find it.

### `dismiss_quest` (~88 tokens)

Dismiss a 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 retry is safe. The quest stays readable in the closed history of list_quests, and reopen_quest puts it back in the file.

Input parameters:

- `quest_id` (string, required): The UUID of the quest: call list_quests to find it.

### `reopen_quest` (~113 tokens)

Reopen a 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 notes, so a quest closed by mistake or taken up again keeps its own history. Clears the closing date; calling it again leaves it open, so a retry is safe. Call list_quests with status done or dismissed to find the quest to reopen.

Input parameters:

- `quest_id` (string, required): The UUID of the quest: call list_quests to find it.

### `get_results` (~128 tokens)

Get the score series

The score series of a tracker: one row per analyst, keyword, engine, tracker version and survey period, in chronological order. Depending on the analyst, a row carries citation_rate and weighted_score, share_of_voice, or sentiment counts.

Input parameters:

- `analyst` (string): Only the rows of this analyst. The custom_prompt analyst yields a text note per response, so the score series is built from the three scored lenses listed here.
- `engine` (string): Only the rows of this engine.
- `tracker_id` (string, required): The UUID of the tracker: call list_trackers to find it.

### `get_responses` (~259 tokens)

Get raw responses

The raw answers of ONE AI engine for a tracker, newest surveys first, paginated. Every answer carries its cited sources and keyword mentions, plus uncited_sources (the pages the engine read without citing them) and searched (whether the engine went to the web to write that answer; null when undetermined). Set include_raw to add the full engine payload; heavy, ask for it only when needed.

Input parameters:

- `engine` (string, required): The engine whose answers are read.
- `include_raw` (boolean): Add the full engine payload to every answer.
- `page` (integer): Page number, 1 by default.
- `per_page` (integer): Answers per page, 25 by default, 100 at most.
- `q` (string): Full-text filter on the answer text.
- `question` (string): Exact text of one tracked question.
- `survey` (string): Only the answers of this survey.
- `tone` (string): Only the answers where the sentiment analyst judged a keyword mention with this tone. Reads the negative answers of a week in one call, when the tracker carries the sentiment analyst that sets the to…
- `tracker_id` (string, required): The UUID of the tracker: call list_trackers to find it.

### `list_keyword_discoveries` (~139 tokens)

List discovered keyword suggestions

The keyword suggestions DISCOVERED on a tracker: domains the surveyed engines cite as sources again and again, that no tracked keyword covers. Recomputed on every read, from the recurrences the surveys have accumulated. Also carries dismissed, the domains this tracker has set aside: what was refused stays readable, so you can restore one with restore_keyword_discovery if the user changes their mind. The two lists are disjoint (a dismissed domain is never suggested). Relay the suggestions to the user: the decision to track a name is theirs.

Input parameters:

- `tracker_id` (string, required): The UUID of the tracker: call list_trackers to find it.

### `accept_keyword_discovery` (~221 tokens)

Accept discovered suggestions

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.

Input parameters:

- `domain` (string): One domain to act on, exactly as listed by list_keyword_discoveries. Send this OR domains, never both.
- `domains` (array): 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 ha…
- `tracker_id` (string, required): The UUID of the tracker: call list_trackers to find it.

### `dismiss_keyword_discovery` (~210 tokens)

Dismiss discovered suggestions

Dismiss one discovered suggestion (domain) or a batch (domains): the domains are never proposed again on this tracker, and appear in the dismissed list until restored. All-or-nothing on unknown domains: one that is not currently suggested refuses the whole batch (not_found). Dismissing an already dismissed domain is fine, it does not fail the batch. The answer carries dismissed as the domain for a single call, the list for a batch.

Input parameters:

- `domain` (string): One domain to act on, exactly as listed by list_keyword_discoveries. Send this OR domains, never both.
- `domains` (array): 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 ha…
- `tracker_id` (string, required): The UUID of the tracker: call list_trackers to find it.

### `restore_keyword_discovery` (~213 tokens)

Restore dismissed suggestions

Restore one dismissed domain (domain) or a batch (domains): it leaves the tracker dismissed list and becomes eligible for discovery again, suggested anew while the engines keep citing it (accepting it stays a distinct move). The counterpart of dismiss, for when the user changes their mind. Idempotent and never refused: restoring a domain that was not dismissed simply leaves it eligible. The answer carries restored as the domain for a single call, the list for a batch.

Input parameters:

- `domain` (string): One domain to act on, exactly as listed by list_keyword_discoveries. Send this OR domains, never both.
- `domains` (array): 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 ha…
- `tracker_id` (string, required): The UUID of the tracker: call list_trackers to find it.

### `list_sources` (~509 tokens)

Search the Atlas of 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 scale over the last 30 days where 100 is the source that AI cites the most. An engine with no value has not cited the domain lately, which is not a zero. Each AI has its own leader, so its own scale: each column ranks the sources on its own AI, the rankings being almost disjoint. The map carries the sources surfaced by the surveys of this account, so it grows as the account measures more; filter it to one brand with project_id. The scale, on the other hand, is computed across every measurement Epovest runs, which is what makes it stable. Use it to see where an answer comes from on a subject, and which places are worth existing on. The unit is the registrable domain, so a subdomain is folded into it and a hosting platform counts as one source, not one per author.

Input parameters:

- `domain` (string): Keep only the domains containing this text, e.g. "wikipedia" or ".fr".
- `engine` (string): Keep only the sources this engine has cited at least once.
- `page` (integer): Page number, from 1.
- `per_page` (integer): Entries per page, 25 by default, 100 at most.
- `project_id` (string): Only the sources surfaced by the trackers of this project: the UUID of a project of the account (call list_projects), or "default" for the trackers without a project. Use it to read the map of one br…
- `sort` (string): Order of the page: "aa_chatgpt", "aa_claude", "aa_gemini", "aa_perplexity", "aa_mistral" or "aa_grok" for the ranking of one AI, which also keeps only the sources that AI cites; "detections" ranks ac…

### `get_source` (~68 tokens)

Read one source of the Atlas

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 same entries filtered and ranked.

Input parameters:

- `source_id` (string, required): The UUID of the source: call list_sources to find it.

### `get_account_settings` (~98 tokens)

Read the 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 language we write to it in and the time zone its hours are shown in. `member` names the person the language and the time zone belong to. Read it before update_account_settings: the answer gives every setting as it stands, so you change the one the user named and leave the others alone.

### `update_account_settings` (~387 tokens)

Update the account settings

Change the settings of the account. Send only what the user is changing: every setting you leave out keeps its value. `billing_country`, `billing_address` and `intra_eu_vat_number` clear when you send null; `name`, `language` and `timezone` keep their value on null, so name the language or the time zone you want. A postal address and a VAT number travel with `billing_country`: send the country in the same call. What you write here goes on the next invoices of the account, and the invoices already issued keep the details they carry.

Input parameters:

- `billing_address` (array): Postal address of the account, one string per line, like ["12 Example Street", "75001 Paris"]. The list replaces the previous address; [] or null clears it. Three lines at most, so the address block…
- `billing_country` (string): Billing country, as an ISO 3166-1 alpha-2 code: "FR", "US", "BR". It decides the tax treatment of the next invoices, so it is the country of the entity being billed, not where the user happens to be.
- `intra_eu_vat_number` (string): Intra-EU VAT number, for an account billed in an EU member state: the two-letter country code followed by the national number, like "FR12345678901". It goes on the invoices of the account.
- `language` (string): The language we write to this account in: emails, and the hosted payment page of a top-up.
- `name` (string): Legal name of the account, the one printed on its invoices.
- `timezone` (string): The time zone the hours of the account are shown in, as an IANA identifier: "Europe/Paris", "America/New_York", "UTC".

### `get_credits` (~212 tokens)

Get the credit balance

The prepaid credit balance of the account: available credits, the amount reserved by surveys in progress with the detail of each reservation, when the credits expire and until when the data-access window is open. Read it before starting a tracker, or when a call fails with insufficient_credits or data_access_expired. It also carries what a top-up is worth here, so you never have to work it out: `monthly_estimate_minor` is what the account has set up to consume in a month, and `suggested_topups[]` gives three amounts derived from it, each with `amount_minor`, `amount` (major units) and `covers_months`, the runway it buys at that pace. `min_topup_minor` is the floor a top-up has to clear. When the account consumes nothing yet, `monthly_estimate_minor` is 0 and the suggestion, if any, carries `covers_months: null`: it buys twelve more months of the data-access window rather than runway.

### `get_usage` (~662 tokens)

Get what the account has spent

What the account SPENDS: one call, three answers, and they must never be mixed up. (1) THIS MONTH, a FORECAST: `this_month_forecast` gives `total_minor` for the month in progress, which is `spent_minor` (already debited) plus `remaining_minor` (what the active trackers and monitored corroborations will still run before month end, counted as real occurrences and recomputed from their configuration). Report it as a forecast, never as spend, and say the month. (2) PER MONTH, actual: `by_month[]` gives, for each of the last 12 months, `month` (YYYY-MM), `spent_minor`, and the same amount by project and by tracker. This is what the wallet was really debited. `months_total` says how many months have spend, so you can tell whether 12 covered everything. (3) OVER THE WINDOW, actual: `total_spent_minor` with `by_project[]` and `by_tracker[]` (biggest spender first) is a cumulative total over `period` (`from` and `to`, the first and last debit counted), never a monthly figure: quote the period alongside the amount. `entries[]` carries the ledger itself. Spend is broken down by COST LINE everywhere, in `lines` and `by_category`: `survey` (the checks themselves), `ai_analyst` (the supplement of the AI analysts grafted onto them), `corroboration_check` (monitored corroborations, one debit per check run) and `other` for a line the tool does not name yet, which stays visible rather than dropping out of a total. Amounts are in minor units of the wallet currency. Filter a single month with `month` (YYYY-MM), and the entries alone with `type` (`in` for top-ups, `out` for spend). Every tracker line carries `tracker_id`, ready for get_results or get_responses, and `listed` says whether that tracker is still in the account list. Each entry is stamped with `created_at`, the exact instant it was posted (RFC 3339, to the second, with the fraction the ledger recorded): an active account posts dozens of entries a day, so quote the time along with the date and let it order the entries of one…

Input parameters:

- `month` (string): A single month, YYYY-MM. Omitted: every month the account has entries for.
- `page` (integer)
- `per_page` (integer)
- `type` (string): Which entries to return: all (default), in (top-ups and adjustments), out (spend and expiries).

### `topup_credits` (~354 tokens)

Buy credits

Prepare a top-up of the prepaid credit balance and return the hosted payment link. Nothing is charged by this call: hand payment_url to the user, the payment happens there, and they approve the amount on that page. When the user names an amount, that amount wins: pass it as `amount`, exactly the number they said. Amounts are always in the wallet currency of the account, which get_credits gives: if they name another currency, tell them, never convert one currency into another yourself. When they leave it to you, take one of the amounts get_credits already suggests in `suggested_topups[]` and pass its `amount_minor`: they are derived from what this account consumes, they clear the floor, and each says the runway it buys in `covers_months`. Name the one you picked and what it covers. Nothing to compute, and nothing to convert. Send one of the two, never both. The minimum top-up is 10.00 (1000 minor units). Once paid, the balance updates on its own, paused trackers resume and the data-access window reopens.

Input parameters:

- `amount` (number): Credits to buy, in MAJOR units of the wallet currency: what a person says. 50 means 50.00, and 12.5 means 12.50. Use this one when the user names the amount, exactly as they said it. Minimum 10.00.
- `amount_minor` (integer): Credits to buy, in MINOR units of the wallet currency: 5000 means 50.00. Use this one when you compute the amount from the cost grid, which is in minor units too. Minimum 1000.

### `contact_support` (~204 tokens)

Write to the Epovest support team

Send a message to the humans behind Epovest: report a problem, suggest an improvement, ask a question. Use it when a tool refuses what should work, when the product is missing something the user needs, or when the user asks you to tell us something. The message lands in the support threads of the account, which the members also see in the app, and a human answers there. Reply to an ongoing thread with thread_id, and read the answer with get_support_thread.

Input parameters:

- `kind` (string): What this message is: sorts it on arrival.
- `message` (string, required): What you want to tell the support team, in the words of the user when they dictated it. Include what you tried and what happened.
- `subject` (string): Title of the thread. Derived from the message when omitted; ignored when replying.
- `thread_id` (string): Reply to this thread instead of opening a new one: call list_support_threads to find it.

### `list_support_threads` (~47 tokens)

List support threads

The support threads of the account, most recent first: what was asked, and whether the support team has answered. The threads are shared by the members of the account, whatever wrote them.

### `get_support_thread` (~60 tokens)

Read a support thread

One support thread with its messages, including the answers of the support team. Read it back after contact_support to relay the answer to the user.

Input parameters:

- `thread_id` (string, required): The UUID of the support thread: call list_support_threads to find it.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-epovest-ai-visibility/mcp#diagnostics

## Score history

- 2026-08-03: 78
- 2026-08-02: 80
- 2026-08-01: 75
- 2026-07-31: 75
- 2026-07-30: 69
- 2026-07-29: 70
- 2026-07-28: 71
- 2026-07-27: 70
- 2026-07-26: 70

## Links

- Remote endpoint: https://mcp.epovest.com/mcp
- Website: https://epovest.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-epovest-ai-visibility/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-epovest-ai-visibility/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-epovest-ai-visibility/mcp