Tally by Outpost MCP server
com.tallybyoutpost/tallytallybyoutpost.comstreamable-httpv0.1.1Scanned
Read-only web and revenue analytics: visitors, sources, goals, funnels and sales tied to visits.
16 tools: 1 do something that can't be undone and 15 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Tally by Outpost MCP server can do
The Tally by Outpost MCP server is published by tallybyoutpost.com, a domain the MCP Registry verified. It has 16 tools. It can do things that cannot be undone, such as sending, paying or publishing (list_sales), but cannot delete data. 15 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 18, 2026, version 0.1.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
16 tools
Can't be undone 1Claude Code: ask
list_salesPayments newest first, each with its amount as charged and in US dollars, whether it is linked to a visitor, how (method and confidence), and why not when it isn't.1 finding
Why it is in this group
- The name "list_sales" says "list": a word for reading.
- The description's first verb is "payment": a word that usually means money moves, which cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "list_sales" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "list_sales" says "list": a word for reading.
Description, as the server wrote it Payments newest first, each with its amount as charged and in US dollars, whether it is linked to a visitor, how (method and confidence), and why not when it isn't. Filter to unlinked payments or refunds.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: List sales
Only reads 15Show 15 read-only tools
compare_periodsA period against the window just before it (previous) or the same dates a year earlier (year): every overview number for both, and the relative change.No findings
Why it is in this group
- The name "compare_periods" says "compare": a word for reading.
Description, as the server wrote it A period against the window just before it (previous) or the same dates a year earlier (year): every overview number for both, and the relative change. Changes are null where the site's records don't reach back far enough to compare.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Compare periods
get_breakdownThe top values of one dimension (source, channel, page, country, device, campaign …) by distinct visitors, or by revenue, each with its share of visitors and the revenue its visito…No findings
Why it is in this group
- The name "get_breakdown" says "get": a word for reading.
Description, as the server wrote it The top values of one dimension (source, channel, page, country, device, campaign …) by distinct visitors, or by revenue, each with its share of visitors and the revenue its visitors brought.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Breakdown
get_coverageHow much of the period's revenue is attributed to a visitor, by method, and the fix-it list for what isn't (with code to paste).No findings
Why it is in this group
- The name "get_coverage" says "get": a word for reading.
Description, as the server wrote it How much of the period's revenue is attributed to a visitor, by method, and the fix-it list for what isn't (with code to paste).
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Attribution coverage
get_customer_valueLifetime value by the source that first brought each customer: customers, revenue, average per customer, renewals and repeat rate, over every payment on record.No findings
Why it is in this group
- The name "get_customer_value" says "get": a word for reading.
Description, as the server wrote it Lifetime value by the source that first brought each customer: customers, revenue, average per customer, renewals and repeat rate, over every payment on record.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Customer lifetime value
get_engagementHow pages are read: views, median reading time, average scroll depth and the share read to the end, per page and overall, and the common entry and exit pages.No findings
Why it is in this group
- The name "get_engagement" says "get": a word for reading.
Description, as the server wrote it How pages are read: views, median reading time, average scroll depth and the share read to the end, per page and overall, and the common entry and exit pages.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Page engagement
get_funnelsThe site's funnels with each step's visitors, conversion from the step before and from the first, and drop-off; or one funnel with `funnel`.No findings
Why it is in this group
- The name "get_funnels" says "get": a word for reading.
Description, as the server wrote it The site's funnels with each step's visitors, conversion from the step before and from the first, and drop-off; or one funnel with `funnel`.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Funnels
get_goalsEvery goal completed in the period with completions, converting visitors, conversion rate and the revenue of converting visitors; give `goal` for one goal's properties.No findings
Why it is in this group
- The name "get_goals" says "get": a word for reading.
Description, as the server wrote it Every goal completed in the period with completions, converting visitors, conversion rate and the revenue of converting visitors; give `goal` for one goal's properties. Lists the site's funnels.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Goals
get_overviewVisitors, pageviews, visits, median engaged time and, when payments are connected, net revenue, sales, refunds, conversion rate and revenue per visitor, for a period and the window…No findings
Why it is in this group
- The name "get_overview" says "get": a word for reading.
Description, as the server wrote it Visitors, pageviews, visits, median engaged time and, when payments are connected, net revenue, sales, refunds, conversion rate and revenue per visitor, for a period and the window before it, with the change between them. Also the visitors live now.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Overview
get_peak_hoursVisits, sales and revenue by weekday and hour in the site's time zone, and the busiest three hours when the data is enough to say.No findings
Why it is in this group
- The name "get_peak_hours" says "get": a word for reading.
Description, as the server wrote it Visits, sales and revenue by weekday and hour in the site's time zone, and the busiest three hours when the data is enough to say.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Peak hours
get_purchase_pathsHow buyers got there: time from first visit to purchase, visits and pages before paying, first-touch to credited-source flows, and the pages buyers saw before paying.No findings
Why it is in this group
- The name "get_purchase_paths" says "get": a word for reading.
Description, as the server wrote it How buyers got there: time from first visit to purchase, visits and pages before paying, first-touch to credited-source flows, and the pages buyers saw before paying.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Path to purchase
get_realtimeWho is on the site in the last five minutes (page, place, source, device) and the sales of the last hour.No findings
Why it is in this group
- The name "get_realtime" says "get": a word for reading.
Description, as the server wrote it Who is on the site in the last five minutes (page, place, source, device) and the sales of the last hour.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Realtime
get_receiptOne payment's receipt: the evidence chain that ties it to a visit (first visit, visits before paying, the credited visit, the handle that matched and where), every provider id, and…No findings
Why it is in this group
- The name "get_receipt" says "get": a word for reading.
Description, as the server wrote it One payment's receipt: the evidence chain that ties it to a visit (first visit, visits before paying, the credited visit, the handle that matched and where), every provider id, and the payment it follows from.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Sale receipt
get_visitorOne visitor's whole journey: every visit with its pages, engaged time, goals and outbound clicks, their payments, first touch and the touch credited with the sale.No findings
Why it is in this group
- The name "get_visitor" says "get": a word for reading.
Description, as the server wrote it One visitor's whole journey: every visit with its pages, engaged time, goals and outbound clicks, their payments, first touch and the touch credited with the sale.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Visitor journey
list_sitesThe site this API key reads: its id, name, domain, time zone and how visitors are counted (cookie, cookieless or consent).No findings
Why it is in this group
- The name "list_sites" says "list": a word for reading.
Description, as the server wrote it The site this API key reads: its id, name, domain, time zone and how visitors are counted (cookie, cookieless or consent).
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: List sites
list_visitorsVisitors (visits on a cookieless site) of a period, most recent first or by revenue or likely to buy, with visits, pages, engaged time per visit, revenue and their latest visit.No findings
Why it is in this group
- The name "list_visitors" says "list": a word for reading.
Description, as the server wrote it Visitors (visits on a cookieless site) of a period, most recent first or by revenue or likely to buy, with visits, pages, engaged time per visit, revenue and their latest visit.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: List visitors
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 19, 2026, 17:19 UTC, unchanged since Nov 19, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 irreversible). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://tallybyoutpost.com/mcp: tools/list returned 16 tools to an anonymous client, including list_sales (irreversible)
Findings
Matches of fixed checks, with the text they matched.
- Warnlist_sales
The server marks "list_sales" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "list_sales" says "list": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.1.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http tally https://tallybyoutpost.com/mcp --header 'Authorization: <your-authorization>'claude mcp add --transport http tally https://tallybyoutpost.com/mcp --header 'Authorization: <your-authorization>'Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__tally__list_sites",
"mcp__tally__get_overview",
"mcp__tally__get_breakdown",
"mcp__tally__compare_periods",
"mcp__tally__get_receipt",
"mcp__tally__get_coverage",
"mcp__tally__list_visitors",
"mcp__tally__get_visitor",
"mcp__tally__get_realtime",
"mcp__tally__get_goals",
"mcp__tally__get_funnels",
"mcp__tally__get_customer_value",
"mcp__tally__get_peak_hours",
"mcp__tally__get_engagement",
"mcp__tally__get_purchase_paths"
],
"ask": [
"mcp__tally__list_sales"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as tally. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.tallybyoutpost/tally/verify?hash=f6d088672117903ea4922fe6218e6241bc87d832d92d09d3cac84f8431f68ffc" | jq -e '.changed == false'Pinned hash f6d088672117, from Nov 18, 2026, 19:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.tallybyoutpost/tally/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.tallybyoutpost/tally)Source: MCP Registry. Synced Nov 18, 2026, 19:17 UTC.
Tally by Outpost MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Tally by Outpost MCP server safe?
- No scan can promise that. What its definitions show: 16 tools, 1 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Tally by Outpost MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Tally by Outpost MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: list_sales.
What tools does the Tally by Outpost MCP server have?
- 16 tools: 1 irreversible, 15 read. list_sales, list_sites, get_overview, get_breakdown, compare_periods, get_receipt, get_coverage, list_visitors and 8 more.
Does the Tally by Outpost MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Tally by Outpost MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Tally by Outpost MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.