# Fathom Analytics MCP by usefulapi (remote · fathom-analytics.usefulapi.io)

Query Fathom Analytics sites, stats, current visitors and events, and manage sites and events.

- Trust score: 65/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- remote · `fathom-analytics.usefulapi.io`: 65/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-fathom-analytics/fathom-analytics.md), [page](https://verifymcp.io/servers/io-usefulapi-fathom-analytics/fathom-analytics)

## Channel facts

- Endpoint: `https://fathom-analytics.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- 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-10-17.

- **Endpoint Security**: 78/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 enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 80/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2669 tokens (~166/item across 16 items; 16 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Fathom Analytics MCP by usefulapi server?

Fathom Analytics MCP by usefulapi is a hosted endpoint at https://fathom-analytics.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http io-usefulapi-fathom-analytics 'https://fathom-analytics.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-fathom-analytics": {
      "url": "https://fathom-analytics.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-fathom-analytics": {
      "type": "http",
      "url": "https://fathom-analytics.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-fathom-analytics]
url = "https://fathom-analytics.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-fathom-analytics": {
      "type": "remote",
      "url": "https://fathom-analytics.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-fathom-analytics --url 'https://fathom-analytics.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-fathom-analytics:
    url: "https://fathom-analytics.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-fathom-analytics": {
      "Transport": "http",
      "Url": "https://fathom-analytics.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-fathom-analytics -t streamable-http -u 'https://fathom-analytics.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-fathom-analytics": {
      "type": "http",
      "url": "https://fathom-analytics.usefulapi.io/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-10-16 (score 65, +1)

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

### 2026-10-14 (score 64, +2)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] The server now declares the “prompts” capability
- [functional] First check of Schema quality: 100
- [functional] New prompt “getting_started”
- [functional] Server version: 1.1.0 → 1.2.0

### 2026-10-13 (score 62, +1)

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

### 2026-10-12 (score 61, +1)

- [functional improvement] Stability: unverified → 0.07

### 2026-10-10 (score 60)

First indexed and scored.

## MCP tools (16)

### `fathom_get_token` (~67 tokens)

Get the API token's permissions

The connected API token's name, permissions (abilities: "*" = Admin, "all-sites-readonly", or per-site read:<id> / manage:<id>) and timestamps. The secret value is never returned. Good first call to know which tools will work. GET /token.

### `fathom_get_account` (~40 tokens)

Get the account

The Fathom account that owns the API token: id, name and email. Needs an Admin token (the * scope). GET /account.

### `fathom_list_sites` (~155 tokens)

List sites

List the sites the token can read (id, name, sharing, timezone, created_at), oldest first. The site id is what every report tool takes. Needs an Admin or all-sites read-only token; a token scoped to a single site cannot list sites, so use fathom_get_site with that site id instead. Paged: pass next.starting_after. GET /sites.

Input parameters:

- `ending_before` (string): Page backward from this object id (newest first). Not together with starting_after.
- `limit` (integer): Items per page, 1-100 (default 10).
- `starting_after` (string): Page forward: pass next.starting_after from the previous reply (an object id).

### `fathom_get_site` (~70 tokens)

Get a site

One site: id, name, sharing (none/private/public), timezone and created_at. GET /sites/{site_id}.

Input parameters:

- `site_id` (string, required): The site id, the same string as in the tracking code (e.g. CDBUGS). fathom_list_sites lists them.

### `fathom_list_events` (~183 tokens)

List a site's events

List a site's events (conversions/goals): every event name the site has tracked plus events with a currency set, sorted by name. Identify events by name (use it as event_name in fathom_get_aggregation); the id is only a paging cursor. Paged: pass next.starting_after. GET /sites/{site_id}/events.

Input parameters:

- `ending_before` (string): Page backward from this object id (newest first). Not together with starting_after.
- `limit` (integer): Items per page, 1-100 (default 10).
- `site_id` (string, required): The site id, the same string as in the tracking code (e.g. CDBUGS). fathom_list_sites lists them.
- `starting_after` (string): Page forward: pass next.starting_after from the previous reply (an object id).

### `fathom_list_milestones` (~156 tokens)

List a site's milestones

List a site's milestones (dated annotations on reports, such as a redesign launch or a campaign start), oldest first. Paged: pass next.starting_after. GET /sites/{site_id}/milestones.

Input parameters:

- `ending_before` (string): Page backward from this object id (newest first). Not together with starting_after.
- `limit` (integer): Items per page, 1-100 (default 10).
- `site_id` (string, required): The site id, the same string as in the tracking code (e.g. CDBUGS). fathom_list_sites lists them.
- `starting_after` (string): Page forward: pass next.starting_after from the previous reply (an object id).

### `fathom_get_milestone` (~99 tokens)

Get a milestone

One milestone: id, name, milestone_date, created_at, updated_at. GET /sites/{site_id}/milestones/{milestone_id}.

Input parameters:

- `milestone_id` (string, required): The milestone id (a UUID, from fathom_list_milestones).
- `site_id` (string, required): The site id, the same string as in the tracking code (e.g. CDBUGS). fathom_list_sites lists them.

### `fathom_get_aggregation` (~549 tokens)

Run a traffic or event report

Fathom's custom report (the dashboard's numbers): aggregate pageviews or one event over a date range, optionally grouped by date and/or fields and filtered. Pageviews: aggregates visits (unique site visits), uniques (unique page visits), pageviews, avg_duration (seconds), bounce_rate. Events (entity event + event_name): conversions, unique_conversions, value (in cents). Examples: top pages = field_grouping [pathname], sort_by pageviews:desc; traffic sources = [referrer_source] or [referrer_hostname]; AI referrals = [ai_source]; daily trend = date_grouping day. All numbers come back as strings. Dates are in the site's timezone; hour grouping only for ranges up to 7 days. Grouped reports return at most 500 rows unless limit is set (max 1000, no paging), so narrow with filters or dates. Data before March 2021 cannot be grouped/filtered. GET /aggregations.

Input parameters:

- `aggregates` (array, required): Metrics. pageview: visits, uniques, pageviews, avg_duration, bounce_rate. event: conversions, unique_conversions, value.
- `date_from` (string): Start, YYYY-MM-DD (start of day) or "YYYY-MM-DD HH:MM:SS", in the site's timezone. Default: the first recorded data.
- `date_grouping` (string): Group by time (omit for one total). hour only for ranges up to 7 days.
- `date_to` (string): End, YYYY-MM-DD (end of day) or "YYYY-MM-DD HH:MM:SS", in the site's timezone. Default: now.
- `entity` (string, required): pageview = site traffic; event = one event's conversions (needs event_name).
- `event_name` (string): For entity event: the event's name, as listed by fathom_list_events.
- `field_grouping` (array): Group by these fields, e.g. [pathname] or [referrer_source, utm_campaign].
- `filters` (array): Filters, all applied (AND). Example: [{"property":"country_code","operator":"is","value":"GB"}].
- `limit` (integer): Row cap, 1-1000 (default 500 when grouping by fields).
- `site_id` (string, required): The site id, the same string as in the tracking code (e.g. CDBUGS). fathom_list_sites lists them.
- `sort_by` (string): "<field>:asc|desc" with a field from aggregates or field_grouping (or timestamp with date_grouping), e.g. pageviews:desc.

### `fathom_get_current_visitors` (~112 tokens)

Get current visitors

Live visitors on a site right now: the total, and with detailed true the top 150 pages (hostname, pathname, total) and top 150 referrers. GET /current_visitors.

Input parameters:

- `detailed` (boolean): true = also the top pages and referrers (default false: only the count).
- `site_id` (string, required): The site id, the same string as in the tracking code (e.g. CDBUGS). fathom_list_sites lists them.

### `fathom_create_site` (~180 tokens)

Create a site

Create a new site in the Fathom account (returns its id, used in the tracking code). Needs an Admin token. Sharing private needs share_password; multi_domain true needs multi_domain_option. POST /sites.

Input parameters:

- `multi_domain` (boolean): true = the site may track multiple domains.
- `multi_domain_option` (string): Required when multi_domain is true: report domains combined or separate.
- `name` (string, required): Site name (up to 255 characters; need not match the URL).
- `share_password` (string): Required when sharing is private: the password for the shared dashboard.
- `sharing` (string): Dashboard sharing: none (default), private (password) or public.
- `timezone` (string): Reporting timezone as a TZ database name, e.g. America/New_York, Europe/London, UTC.

### `fathom_update_site` (~201 tokens)

Update a site

Change a site's name, sharing, timezone or multi-domain setting (send only what changes). Changing the timezone changes how reports are bucketed. Needs a manage token for the site. POST /sites/{site_id}.

Input parameters:

- `multi_domain` (boolean): true = the site may track multiple domains.
- `multi_domain_option` (string): Required when multi_domain is true: combined or separate.
- `name` (string): New site name (up to 255 characters).
- `share_password` (string): Required when setting sharing to private.
- `sharing` (string): Dashboard sharing: none, private (needs share_password) or public.
- `site_id` (string, required): The site id, the same string as in the tracking code (e.g. CDBUGS). fathom_list_sites lists them.
- `timezone` (string): Reporting timezone as a TZ database name, e.g. America/New_York, Europe/London, UTC.

### `fathom_set_event_currency` (~154 tokens)

Set an event's currency

Set the currency of an event's value by event name (works before the event is first tracked). Needs a manage token for the site. POST /sites/{site_id}/events/currency.

Input parameters:

- `currency` (string, required): dollar, pound, euro, yuan, peso, shekel, yen, won, hryvnia, franc, rupee, integer (a plain number) or none.
- `event_name` (string, required): The event's name exactly as tracked (up to 255 characters; fathom_list_events lists them).
- `site_id` (string, required): The site id, the same string as in the tracking code (e.g. CDBUGS). fathom_list_sites lists them.

### `fathom_clear_event_currency` (~113 tokens)

Clear an event's currency

Remove the currency set for an event, so it uses the site's default again. The event and its completion data stay. Needs a manage token for the site. DELETE /sites/{site_id}/events?name=.

Input parameters:

- `event_name` (string, required): The event's name exactly as tracked (fathom_list_events lists them).
- `site_id` (string, required): The site id, the same string as in the tracking code (e.g. CDBUGS). fathom_list_sites lists them.

### `fathom_create_milestone` (~126 tokens)

Create a milestone

Add a milestone (a dated annotation shown on the site's reports, e.g. a launch or campaign start). Needs a manage token for the site. POST /sites/{site_id}/milestones.

Input parameters:

- `milestone_date` (string, required): The milestone's date, YYYY-MM-DD.
- `name` (string, required): Milestone name (up to 30 characters), e.g. Redesign launch.
- `site_id` (string, required): The site id, the same string as in the tracking code (e.g. CDBUGS). fathom_list_sites lists them.

### `fathom_update_milestone` (~145 tokens)

Update a milestone

Rename or re-date a milestone (both name and milestone_date are required). Needs a manage token for the site. POST /sites/{site_id}/milestones/{milestone_id}.

Input parameters:

- `milestone_date` (string, required): The milestone's date, YYYY-MM-DD.
- `milestone_id` (string, required): The milestone id (a UUID, from fathom_list_milestones).
- `name` (string, required): Milestone name (up to 30 characters), e.g. Redesign launch.
- `site_id` (string, required): The site id, the same string as in the tracking code (e.g. CDBUGS). fathom_list_sites lists them.

### `fathom_delete_milestone` (~111 tokens)

Delete a milestone

Permanently delete a milestone (only the annotation; traffic data is not touched). Cannot be undone. Needs a manage token for the site. DELETE /sites/{site_id}/milestones/{milestone_id}.

Input parameters:

- `milestone_id` (string, required): The milestone id (a UUID, from fathom_list_milestones).
- `site_id` (string, required): The site id, the same string as in the tracking code (e.g. CDBUGS). fathom_list_sites lists them.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-fathom-analytics/fathom-analytics#diagnostics

## Score history

- 2026-10-17: 65
- 2026-10-16: 65
- 2026-10-15: 64
- 2026-10-14: 64
- 2026-10-13: 62
- 2026-10-12: 61
- 2026-10-10: 60

## Common questions

### What is the Fathom Analytics MCP by usefulapi server?

Fathom Analytics MCP by usefulapi is listed in the public MCP registry as io.usefulapi/fathom-analytics. Query Fathom Analytics sites, stats, current visitors and events, and manage sites and events. This page covers its hosted endpoint (https://fathom-analytics.usefulapi.io/mcp).

### Is the Fathom Analytics MCP by usefulapi server safe to use?

Fathom Analytics MCP by usefulapi scores 65 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Fathom Analytics MCP by usefulapi server expose?

Fathom Analytics MCP by usefulapi exposes 16 tools: fathom_get_token, fathom_get_account, fathom_list_sites, fathom_get_site, fathom_list_events, and 11 more. Their descriptions and schemas cost roughly 2,461 tokens of context every time the server is loaded.

### Does the Fathom Analytics MCP by usefulapi server require authentication?

Yes. Fathom Analytics MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Fathom Analytics MCP by usefulapi server still maintained?

Fathom Analytics MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://fathom-analytics.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/fathom-analytics/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-fathom-analytics/fathom-analytics.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-fathom-analytics/fathom-analytics.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-fathom-analytics/fathom-analytics