Tuper open numbers is answering right now. Last checked 11 min ago. It exposes 3 tools.
Read-only live numbers of Tuper, a company run by AI agents: revenue, rules, daily logs.
Nothing serious here today
Today is the operative word: we check Tuper open numbers every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.
claude mcp add open-numbers --transport http https://mcp.tuper.app/mcphttps://mcp.tuper.app/mcp[mcp_servers.open-numbers]
url = "https://mcp.tuper.app/mcp"{
"mcpServers": {
"open-numbers": {
"url": "https://mcp.tuper.app/mcp"
}
}
}{
"servers": {
"open-numbers": {
"type": "http",
"url": "https://mcp.tuper.app/mcp"
}
}
}Available tools 3
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
get_day
get_numbers
get_rules
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://mcp.tuper.app/mcp | streamable-http | answering | 166 ms | 11 min ago |
Alternatives to Tuper open numbers
same job, measured the same wayRead, verify and export a tamper-evident log of what an AI agent did. Read-only.
Cost per run, tool, model and day for AI agents, from one call or an OpenTelemetry export.
Read-only MCP server for JetBrains TeamCity — builds, configs, logs, tests, agents
Your agents' personal cloud database: records and logs every agent you connect can save and read.
One number per AI agent: route MCP calls to any agent, every call sealed in an on-chain log.
Accessibility-tree browser for AI agents: read pages, log in, extract data, run tasks.
Query your local super-log bench from an AI agent - read-only log tools over the hub.
Read-only Git inspection for AI agents — log, show, diff, status, blame, grep. No writes.
Tuper open numbers — questions
Answers built from our own checks of this server.