
tlly MCP server
Which MCP servers are tlly's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-30
- Registry namedev.tlly/tllyverified in the MCP registry
The registry name sits under tlly.dev. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-30
- Tools2
- Server calls itselftlly
- Server version1.0.0
- Protocol version2025-06-18
On 2026-10-30 the server answered initialize and tools/list without a sign-in. First answer in 317 ms.
- Whether its tools do the product's job has not been judged yet.
- Checked on 5 of the 7 days it takes to judge reliability.
Once connected
- create_dashboard, update_dashboard, publish_dashboard_version, delete_dashboard, delete_series change data without a sign-in: anyone with the address can call them.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 5 so far
- Answeredmeasuring5 of the 7 daily checks it takes to print a share
- Median first answer663 ms
- Space in an agent's context≈ 9,378 tokensthe definitions of all its tools (30), which an agent carries on every turn
- Tool definitionsA · 98 of 100
- Typed results0 of 30 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 4 of 30
What an agent can do with it
- not sure · Get a morning email when numbers cross your targets
- not sure · Watch failed payments and Stripe balance each day
- not sure · Check Shopify orders against the last few weeks
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
- Tools that change data, on a server that answers without a sign-in: create_dashboard, update_dashboard, publish_dashboard_version, delete_dashboard, delete_series
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
list_integration_skillsList integration setup playbooks (Stripe, Shopify, Sheets, and the other sources tlly can read). A spreadsheet starts from the KPI template. Make a copy…
get_integration_skillRead one integration playbook by id: what to track, the minimum credential and scopes, the exact tlly job, and gotchas. google-sheets and json-api also return a template field (Make a copy, public CSV, downloads). Make a copy…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"tlly": {
"type": "http",
"url": "https://tlly.dev/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http tlly https://tlly.dev/mcpclaude.ai, ChatGPT and other clients: add https://tlly.dev/mcp as a custom connector in the settings.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.