Fathom Analytics MCP by usefulapi
REMOTE · FATHOM-ANALYTICS.USEFULAPI.IO
Query Fathom Analytics sites, stats, current visitors and events, and manage sites and events.
Available components
Last scanned (1 hour ago)
Scores higher than 47% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Data and Analytics
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. How we score → Why this is hard to score →
Endpoint Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 16 Oct 26 +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.
- 14 Oct 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- 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 functional
- 13 Oct 26 +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.
- 12 Oct 26 +1
- Stability: unverified → 0.07 ▲ functional
- 10 Oct 26 60
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Probed https://fathom-analytics.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of fathom-analytics.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://fathom-analytics.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://fathom-analytics.usefulapi.io/.well-known/oauth-protected-resource/mcp" Protected resource metadata
| Document | https://fathom-analytics.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://fathom-analytics.usefulapi.io/mcp |
| Authorisation server | https://fathom-analytics.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://fathom-analytics.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/fathom-analytics/ |
| http (plaintext) | http://fathom-analytics.usefulapi.io/mcp | Inconclusive | 302 | http://fathom-analytics.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
fathom_clear_event_currency Clear an event's currency ~113
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=.
| Name | Type | Req | Description |
|---|---|---|---|
| event_name | string | yes | The event's name exactly as tracked (fathom_list_events lists them). |
| site_id | string | yes | The site id, the same string as in the tracking code (e.g. CDBUGS). fathom_list_sites lists them. |
No output schema declared.
No examples provided.
fathom_create_milestone Create a milestone ~126
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.
| Name | Type | Req | Description |
|---|---|---|---|
| milestone_date | string | yes | The milestone's date, YYYY-MM-DD. |
| name | string | yes | Milestone name (up to 30 characters), e.g. Redesign launch. |
| site_id | string | yes | The site id, the same string as in the tracking code (e.g. CDBUGS). fathom_list_sites lists them. |
No output schema declared.
No examples provided.
fathom_create_site Create a site ~180
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
fathom_delete_milestone Delete a milestone ~111
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| milestone_id | string | yes | The milestone id (a UUID, from fathom_list_milestones). |
| site_id | string | yes | The site id, the same string as in the tracking code (e.g. CDBUGS). fathom_list_sites lists them. |
No output schema declared.
No examples provided.
fathom_get_account Get the account ~40
The Fathom account that owns the API token: id, name and email. Needs an Admin token (the * scope). GET /account.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
fathom_get_aggregation Run a traffic or event report ~549
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.
| Name | Type | Req | Description |
|---|---|---|---|
| aggregates | array | yes | 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 | yes | 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 | yes | 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. |
No output schema declared.
No examples provided.
fathom_get_current_visitors Get current visitors ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| detailed | boolean | – | true = also the top pages and referrers (default false: only the count). |
| site_id | string | yes | The site id, the same string as in the tracking code (e.g. CDBUGS). fathom_list_sites lists them. |
No output schema declared.
No examples provided.
fathom_get_milestone Get a milestone ~99
One milestone: id, name, milestone_date, created_at, updated_at. GET /sites/{site_id}/milestones/{milestone_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| milestone_id | string | yes | The milestone id (a UUID, from fathom_list_milestones). |
| site_id | string | yes | The site id, the same string as in the tracking code (e.g. CDBUGS). fathom_list_sites lists them. |
No output schema declared.
No examples provided.
fathom_get_site Get a site ~70
One site: id, name, sharing (none/private/public), timezone and created_at. GET /sites/{site_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| site_id | string | yes | The site id, the same string as in the tracking code (e.g. CDBUGS). fathom_list_sites lists them. |
No output schema declared.
No examples provided.
fathom_get_token Get the API token's permissions ~67
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
fathom_list_events List a site's events ~183
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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). |
No output schema declared.
No examples provided.
fathom_list_milestones List a site's milestones ~156
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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). |
No output schema declared.
No examples provided.
fathom_list_sites List sites ~155
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
fathom_set_event_currency Set an event's currency ~154
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.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | yes | dollar, pound, euro, yuan, peso, shekel, yen, won, hryvnia, franc, rupee, integer (a plain number) or none. |
| event_name | string | yes | The event's name exactly as tracked (up to 255 characters; fathom_list_events lists them). |
| site_id | string | yes | The site id, the same string as in the tracking code (e.g. CDBUGS). fathom_list_sites lists them. |
No output schema declared.
No examples provided.
fathom_update_milestone Update a milestone ~145
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| milestone_date | string | yes | The milestone's date, YYYY-MM-DD. |
| milestone_id | string | yes | The milestone id (a UUID, from fathom_list_milestones). |
| name | string | yes | Milestone name (up to 30 characters), e.g. Redesign launch. |
| site_id | string | yes | The site id, the same string as in the tracking code (e.g. CDBUGS). fathom_list_sites lists them. |
No output schema declared.
No examples provided.
fathom_update_site Update a site ~201
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
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.
remote · fathom-analytics.usefulapi.io
claude mcp add --transport http io-usefulapi-fathom-analytics 'https://fathom-analytics.usefulapi.io/mcp'
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.