Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Tally

REMOTE · TALLYCATALOG.COM

Company and open-source numbers (valuation, revenue, prices, stars) with history and sources.

Available components

71 Trust /100

Last scanned (15 hours ago)

Scores higher than 56% of remote servers

Reachable. Last reached 21 Nov 2026.

Trust breakdown (7 categories)

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 Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • 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
Transport & Reachability100
Schema Quality & AI Usability73
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 593 tokens (~98/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
  • Stability observed for 3 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
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 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.

  • 19 Nov 26 +1
    • Schema quality: 464 → 593 ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • New tool “get_value_on” functional
  • 18 Nov 26 69

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://tallycatalog.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=tallycatalog.com CN=YE2,O=Let's Encrypt,C=US 14 Nov 2026 12 Feb 2027 ECDSA 256 ECDSA-SHA384 507ed551c527190a74e168cb46472ffb5ac
SANs: tallycatalog.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of tallycatalog.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
tallycatalog.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://tallycatalog.com/mcp Verified 200
http (plaintext) http://tallycatalog.com/mcp HTTPS enforced 308 https://tallycatalog.com/mcp
MCP tools · 6 exposed · ~504 tokens

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 →

Tool Tokens
get_company ~58

Every number Tally keeps about one company, project, sector or investor, each with its current value and id.

NameTypeReqDescription
namestringyesThe name, for example 'Anthropic', 'Stripe', 'LangChain', or a stock ticker.

No output schema declared.

No examples provided.

get_history ~120

The dated past values of one number, oldest first, each with the page it was read from. Use it for trends, growth rates and 'what was it on a given date'.

NameTypeReqDescription
idinteger–The number's id, from search_numbers.
limitinteger–How many of the latest points to return (default 200, at most 1000).
pagestring–Or the number's page address on tallycatalog.com.
sincestring–Only values on or after this date, YYYY-MM-DD.

No output schema declared.

No examples provided.

get_number ~85

One number's current value with its date, the page it was read from, when it last changed and by how much, and where its history and chart are. Cite the 'page' address when you use the value.

NameTypeReqDescription
idinteger–The number's id, from search_numbers.
pagestring–Or the number's page address on tallycatalog.com.

No output schema declared.

No examples provided.

get_value_on ~129

What a number was on a given past day, from the record: the last value on or before that day, the date it was recorded, what set it when known (for example a funding round), its source, and when it next changed. Nothing is interpolated. Use it for questions like 'what was X's valuation in March 2025'.

NameTypeReqDescription
datestringyesThe day to look up, YYYY-MM-DD.
idinteger–The number's id, from search_numbers.
pagestring–Or the number's page address on tallycatalog.com.

No output schema declared.

No examples provided.

search_numbers ~77

Find numbers in the Tally record by words, for example 'anthropic valuation', 'openai revenue', 'langchain stars', 'cursor plan price'. Returns each match with its id, current value and page, and any company whose name matches.

NameTypeReqDescription
querystringyesA company or project name, optionally with what to measure.

No output schema declared.

No examples provided.

what_moved_this_week ~35

The numbers whose value changed in the last seven days: funding rounds, valuations and prices first, then the biggest moves.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Tally MCP server?

Tally is a hosted endpoint at https://tallycatalog.com/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 · tallycatalog.com

# add to Claude Code
claude mcp add --transport http verkyyi-tally 'https://tallycatalog.com/mcp'
Common questions

What is the Tally MCP server?

Tally is an MCP server listed in the public MCP registry as io.github.verkyyi/tally. Company and open-source numbers (valuation, revenue, prices, stars) with history and sources. This page covers its hosted endpoint (https://tallycatalog.com/mcp).

Is the Tally MCP server safe to use?

Tally scores 71 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 Tally MCP server expose?

Tally exposes 6 tools: search_numbers, get_number, get_history, get_value_on, get_company, what_moved_this_week. Their descriptions and schemas cost roughly 504 tokens of context every time the server is loaded.

Does the Tally MCP server require authentication?

No. We connected to Tally without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Tally MCP server still maintained?

Tally is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Tally MCP server?

VerifyMCP ran 13 checks on Tally, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.