Model Context Protocol server for Rollbar
Nothing to run from here
Fathom Analytics MCP by usefulapi is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
16
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Query Fathom Analytics sites, stats, current visitors and events, and manage sites and events.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http fathom-analytics-mcp-by-usefulapi https://fathom-analytics.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# fathom_get_token, fathom_get_account, fathom_list_sites and 13 more
Fathom Analytics MCP by usefulapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 334 servers
usefulapi334 servers
24 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http fathom-analytics-mcp-by-usefulapi https://fathom-analytics.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
16 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
No parameter schema on file.
The Fathom account that owns the API token: id, name and email. Needs an Admin token (the * scope). GET /account.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Items per page, 1-100 (default 10). |
| starting_after | string | no | Page forward: pass next.starting_after from the previous reply (an object id). |
| ending_before | string | no | Page backward from this object id (newest first). Not together with starting_after. |
One site: id, name, sharing (none/private/public), timezone and created_at. GET /sites/{site_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site_id | string | yes | The site id, the same string as in the tracking code (e.g. CDBUGS). fathom_list_sites lists them. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site_id | string | yes | The site id, the same string as in the tracking code (e.g. CDBUGS). fathom_list_sites lists them. |
| limit | integer | no | Items per page, 1-100 (default 10). |
| starting_after | string | no | Page forward: pass next.starting_after from the previous reply (an object id). |
| ending_before | string | no | Page backward from this object id (newest first). Not together with starting_after. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site_id | string | yes | The site id, the same string as in the tracking code (e.g. CDBUGS). fathom_list_sites lists them. |
| limit | integer | no | Items per page, 1-100 (default 10). |
| starting_after | string | no | Page forward: pass next.starting_after from the previous reply (an object id). |
| ending_before | string | no | Page backward from this object id (newest first). Not together with starting_after. |
One milestone: id, name, milestone_date, created_at, updated_at. GET /sites/{site_id}/milestones/{milestone_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site_id | string | yes | The site id, the same string as in the tracking code (e.g. CDBUGS). fathom_list_sites lists them. |
| milestone_id | string | yes | The milestone id (a UUID, from fathom_list_milestones). |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site_id | string | yes | The site id, the same string as in the tracking code (e.g. CDBUGS). fathom_list_sites lists them. |
| entity | string | yes | pageview = site traffic; event = one event's conversions (needs event_name). |
| event_name | string | no | For entity event: the event's name, as listed by fathom_list_events. |
| aggregates | array | yes | Metrics. pageview: visits, uniques, pageviews, avg_duration, bounce_rate. event: conversions, unique_conversions, value. |
| date_grouping | string | no | Group by time (omit for one total). hour only for ranges up to 7 days. |
| field_grouping | array | no | Group by these fields, e.g. [pathname] or [referrer_source, utm_campaign]. |
| sort_by | string | no | "<field>:asc|desc" with a field from aggregates or field_grouping (or timestamp with date_grouping), e.g. pageviews:desc. |
| date_from | string | no | 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_to | string | no | End, YYYY-MM-DD (end of day) or "YYYY-MM-DD HH:MM:SS", in the site's timezone. Default: now. |
| limit | integer | no | Row cap, 1-1000 (default 500 when grouping by fields). |
| filters | array | no | Filters, all applied (AND). Example: [{"property":"country_code","operator":"is","value":"GB"}]. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site_id | string | yes | The site id, the same string as in the tracking code (e.g. CDBUGS). fathom_list_sites lists them. |
| detailed | boolean | no | true = also the top pages and referrers (default false: only the count). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Site name (up to 255 characters; need not match the URL). |
| sharing | string | no | Dashboard sharing: none (default), private (password) or public. |
| share_password | string | no | Required when sharing is private: the password for the shared dashboard. |
| timezone | string | no | Reporting timezone as a TZ database name, e.g. America/New_York, Europe/London, UTC. |
| multi_domain | boolean | no | true = the site may track multiple domains. |
| multi_domain_option | string | no | Required when multi_domain is true: report domains combined or separate. |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site_id | string | yes | The site id, the same string as in the tracking code (e.g. CDBUGS). fathom_list_sites lists them. |
| name | string | no | New site name (up to 255 characters). |
| sharing | string | no | Dashboard sharing: none, private (needs share_password) or public. |
| share_password | string | no | Required when setting sharing to private. |
| timezone | string | no | Reporting timezone as a TZ database name, e.g. America/New_York, Europe/London, UTC. |
| multi_domain | boolean | no | true = the site may track multiple domains. |
| multi_domain_option | string | no | Required when multi_domain is true: combined or separate. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site_id | string | yes | The site id, the same string as in the tracking code (e.g. CDBUGS). fathom_list_sites lists them. |
| event_name | string | yes | The event's name exactly as tracked (up to 255 characters; fathom_list_events lists them). |
| currency | string | yes | dollar, pound, euro, yuan, peso, shekel, yen, won, hryvnia, franc, rupee, integer (a plain number) or none. |
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=.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site_id | string | yes | The site id, the same string as in the tracking code (e.g. CDBUGS). fathom_list_sites lists them. |
| event_name | string | yes | The event's name exactly as tracked (fathom_list_events lists them). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site_id | string | yes | The site id, the same string as in the tracking code (e.g. CDBUGS). fathom_list_sites lists them. |
| name | string | yes | Milestone name (up to 30 characters), e.g. Redesign launch. |
| milestone_date | string | yes | The milestone's date, YYYY-MM-DD. |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site_id | string | yes | The site id, the same string as in the tracking code (e.g. CDBUGS). fathom_list_sites lists them. |
| 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. |
| milestone_date | string | yes | The milestone's date, YYYY-MM-DD. |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site_id | string | yes | The site id, the same string as in the tracking code (e.g. CDBUGS). fathom_list_sites lists them. |
| milestone_id | string | yes | The milestone id (a UUID, from fathom_list_milestones). |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Fathom Analytics MCP by usefulapi or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Fathom Analytics MCP by usefulapi can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.