
Tally
markets.tallyPublished by tally.marketsOfficial publisherv1.8.0Updated Oct 27, 2026
AI risk officer: private trading theses, evidence, exit criteria and decision history. No execution.
Overview
Tally is a remote MCP server that keeps a private trading journal — theses, evidence, exit criteria and decision history — for AI-assisted trading, with no…
- What you can do
- Create, list and read private thesis records with criteria, then arm or close them with a reason
- Add sourced evidence readings and record triggered criteria against a thesis
- Log user-approved decisions, boundaries, rule deviations and linked corrections, then read decision history chronologically with pagination
- Run a checkup of active theses, deadlines, issues and history, plus archived execution evidence for an optional Propr account
- Retrieve an explicitly published receipt link and send user-approved product feedback to the Tally team
- Preserve optional mandate and agent-activity records for review
- When to use it
- For traders who want an assistant to keep a consistent, private record of trading theses, evidence, exit rules and decisions across conversations in Claude, ChatGPT or other MCP clients, and to review process rather than place trades.
- Requirements
- A remote Streamable HTTP endpoint with OAuth sign-in; no local package or environment variables. A Tally account and plan: free covers 3 active theses and 10 created in total, Sentinel is paid, and Connected is an optional paid tier for read-only broker snapshots. Tool availability depends on the AI app, plan and workspace permissions.
Installation
In SourceWeft
- Open Tally in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/markets.tally%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"tally": {
"type": "http",
"url": "https://tally.markets/api/mcp"
}
}
}README
Tally MCP
Your AI risk officer for AI-assisted trading. Tally keeps your private thesis, evidence, risk budget, exit criteria and decision history across conversations in Claude, ChatGPT and other compatible MCP clients.
Connect
See the setup guide. Endpoint: https://tally.markets/api/mcp, Streamable HTTP with OAuth. Tool availability depends on the AI app, plan and workspace permissions.
Start with: “Get started with Tally, then run my checkup.”
Free includes 3 active theses (including drafts) and 10 total created. Closing frees an active slot but does not reset the total. Saved records remain readable, reviewable and closable. Sentinel is $9/month or $49/year with no creation cap and supported monitoring across the active journal.
Connected is an optional $89/month tier adding read-only broker snapshots after
payment, provider activation and explicit owner consent. Every plan includes the
AI connection. If a paid customer's broker service is awaiting initial setup,
get_checkup.brokerage.status is activation_pending; explain that state and
continue the journal workflow. A Tally check time is separate from provider data
freshness. Transaction history can be delayed; this is not a live trading feed.
Tools
The morning-checkup, pre-register-trade and close-out prompts support reviews. Scheduling is client-dependent, not a guarantee of unattended operation. Keep user confirmation controls in place.
Execution boundary
No connector tool places, cancels, closes or modifies orders, changes protective stops, or resumes autonomous trading. Existing optional Propr controls remain in Tally Settings. Journal closure must never be represented as position closure. OpenAI execution capabilities remain disabled under current policy guidance.
Records are owner-scoped and private unless the user explicitly publishes a receipt. Read privacy and terms.
This repository contains public documentation and registry metadata only. Server implementation and secrets are not published here. Method: 2026-10-21.1. Server manifest: 1.8.0 (publication is a separate release step).
In get_checkup, brokerage is null without an eligible Connected subscription;
it can describe activation pending before a broker is connected. The retired
monitoring section is null. The optional agent section is null without a
Propr account. Journal users do not need either connection.
Transport safeguards: requests are limited to 128 KiB before JSON parsing, and tool arguments to 5,000 combined object keys/array entries. Split larger evidence updates into smaller calls. Each request gets its own MCP server instance.
Decision history
With the user’s agreement, save a concise sequence of what happened, what they decided, why, and which rule they followed or crossed. A boundary entry states the user’s line in the sand and their intended response. Corrections append and link to an earlier event. This works on every plan and does not consume a thesis slot.
Use get_decision_history alongside checkup data for process reviews. Records are oldest first; follow next_cursor until null for a complete period. Keep filters unchanged between pages. Date-range queries combine user reports and watcher alerts/readings; a session filter returns reported entries only because watcher records have no inferred session assignment. occurred_at and recorded_at distinguish an event from a retrospective report.
Tally does not receive the full Claude or ChatGPT transcript. Save only relevant summaries the user approved. Do not infer mental health, label a trading style from a small sample, or mistake a reported decision for a verified fill. Compare process with the rule that existed at the time, separately from P&L. Review possible tipping points with the user; a boundary entry does not control execution.
Product feedback is separate: show the exact feedback wording, get the user’s agreement to send it to Tally’s team, then call submit_product_feedback. Never include private journal content by default. Signed-in users can also use Feedback in their app footer.
Source: README.md at commit 526ae9c
Tools
0Version history
8- v1.8.0LatestOct 22, 2026
- v1.7.0Oct 18, 2026
- v1.6.0Oct 9, 2026
- v1.5.1Oct 9, 2026
- v1.5.0Oct 9, 2026
- v1.4.0Oct 4, 2026
- v1.1.0Oct 3, 2026
- v1.0.0Sep 16, 2026
Score
75% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.
Other Tally integrations

Zovo Tally Import
Published by GitHub account theluckystrike
Converts bank statements into Tally XML vouchers that can be imported into TallyPrime or Tally ERP 9.

Tally Mcp
Published by GitHub account mrfentmen
Query Tally (key; set TALLY_API_KEY, Bearer): forms, form details, submissions.

ComplyEaze Bridge
Published by GitHub account ComplyEaze
Claude Desktop extension that reads a local TallyPrime book and proposes Payment, Receipt and Contra vouchers from Indian bank statement PDFs.

FabTally Utility Belt
Published by GitHub account zvmzaretsky
A remote MCP server offering 13 deterministic utilities — unit conversion, hashing, encoding, IDs, regex, time zones, cron, RRULE, currency, diff, JSON Schema —

FabTally Decode
Published by GitHub account zvmzaretsky
Remote MCP server that decodes raw EVM data — event logs, calldata, selectors and contract ABIs — into readable JSON for six chains.