Finance · Remote MCP server
Tallymeter
Time tracking and invoicing for AI agents and their humans: track, log and bill work by agent.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.tallymeter/tallymeter- Version
- 1.0.0
- Status
- Active
- Category
- finance
- Transport
- Streamable HTTP
- Published
- 2026-07-11
- Updated
- 2026-07-11
- Publisher
- com.tallymeter
- Namespace
- Namespace verified by the MCP Registry via the domain tallymeter.com · how
- Website
- tallymeter.com
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://tallymeter.com/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; a Bearer token is asked for
- Checked on
- 2026-10-05
How to connect Tallymeter
Tallymeter is a remote MCP server: there is nothing to install. Its endpoint is https://tallymeter.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More finance servers
| Server | Runs |
|---|---|
| TAG IT VerifyVerify on-chain lifecycle state and provenance of NFC-tagged physical products. | Remote · HTTPLive check: ✓ handshake |
| Taiwan Payments & E-Invoice (ECPay 綠界 / NewebPay 藍新)Taiwan payments (ECPay 綠界 + NewebPay 藍新) & e-invoices for AI agents. Stateless, never holds funds. | Remote · HTTPLive check: ✗ no handshake |
| TalliedLog hours and invoice clients from your AI chat. Time tracking and invoicing for freelancers. | Remote · HTTPLive check: sign-in required |
| tally.marketsThe risk officer for AI trading: an independent, read-only watcher for your trading agent. | Remote · HTTPLive check: sign-in required |
| TallystickRead, validate and write e-invoices on your own machine. XRechnung, ZUGFeRD, Factur-X, UBL, CII. | Local · stdio |
| TalvalValue-investing research: fair values, valuation verdicts, quality scores and 13F portfolios. | Remote · HTTPLive check: ✓ handshake |
| taokeh.myMalaysian SME accounting, e-Invoice and payroll for your AI. 64 tools; writes are approved drafts. | Remote · HTTPLive check: sign-in required |
| TapeAPI: signed BNB Chain readsSigned BNB Chain reads (balances, tokens, NFTs, prices, TapeOut names) with verifiable receipts. | Remote · HTTPLive check: ✓ handshake |