Tally
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@TallyRun my morning checkup and show me active theses."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Tally — the risk officer for AI-assisted trading
Every trading connector makes your AI more capable. Tally makes it accountable.
Tally (tally.markets) is a trading-discipline layer that mounts inside Claude, ChatGPT, Claude Code, and any MCP-capable agent. Your AI is the analyst — it researches, monitors, and gathers evidence. Tally holds the record neither you nor the model can rewrite: pre-registered theses, exit rules that freeze before capital moves, a 24-hour cooling-off, an override ledger for rule-breaking exits, and a public receipt for every closed trade.
Tally never executes trades. Every broker and venue connection is read-only at the API level — no order placement, no custody, by architecture and by policy.
Connect
Server URL (Streamable HTTP · OAuth 2.0 with dynamic client registration):
https://tally.markets/api/mcpClient | How |
Claude | Settings → Connectors → Add custom connector → name it |
ChatGPT | Plugins → New plugin → name it |
Claude Code |
|
Any MCP agent | Point it at the URL above; OAuth discovery does the rest. |
Then say: "Get started with Tally, then run my checkup." The server teaches your AI the whole protocol on first contact.
Full walkthrough (skill, scheduled morning checkup, broker linking): tally.markets/connect
Related MCP server: trading-mcp-server
Tools
Tool | What it does |
| Returns the discipline protocol — the AI teaches itself |
| Morning briefing: active theses, deadlines, evidence, closed history and lifetime R |
| Read the journal |
| Pre-register a trade: statement, mechanism, risk budget, exit criteria (starts the 24h cooling-off) |
| Freeze the criteria after cooling-off — from here they fire, never edit |
| Log evidence against a criterion (the generic sensor primitive) |
| Mark a rule objectively triggered, with cited evidence — one-way |
| Close a trade; discretionary closes require a written justification, logged forever |
| The public receipt for a closed thesis |
Reads are safe to always-allow; writes are guarded by the protocol itself (cooling-off, criteria minimums, override justifications).
Proof
A real receipt — pre-registered thesis, venue-verified entry and exit, −0.22R, graded Process B / Outcome D, closing note verbatim: "Wrong on thesis, right on process."
How it compares
Market-data connectors inform your AI. Execution connectors let it trade. Journal connectors show it your past. Tally is the one built to constrain — it runs alongside all of them: tally.markets/compare
Privacy & security
OAuth per user; your AI sees your journal only, under a grant you can revoke any time.
Brokerage data (via SnapTrade) is read-only; broker credentials never touch Tally.
Details: privacy · terms · support@tally.markets
This repository contains documentation and the public server manifest only — the hosted server lives at tally.markets. No secrets, keys, or server source belong here, ever.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Alicense-qualityDmaintenanceEnables AI agents to execute stock trading operations with built-in risk controls and human approval workflows. Supports paper trading simulation, real brokerage integration (Alpaca, Tradier), backtesting, sentiment analysis, and portfolio management while maintaining strict separation between AI intelligence and trade execution.MIT
- AlicenseBqualityAmaintenanceProvides a safe trading toolkit for AI agents with market data, indicators, paper trading, and guarded broker integration.63MIT
- Alicense-qualityCmaintenanceEnforces pre-trade planning discipline by checking entry, stop, target, and risk/reward via a gate tool, and provides proof receipts, terminal links, and risk prompts for AI assistants.MIT
- Alicense-qualityFmaintenanceEnables AI agents to execute prediction-market trades through a risk-control gateway that enforces signed mandates and generates proof trails for accountability.0MIT
Related MCP Connectors
No-KYC managed MCP for AI agents: sandboxed TypeScript trading SDK, isolated sub-accounts, futures.
Build, backtest, and deploy quantitative trading strategies from your AI agent.
Validated trading edges across futures, equities, crypto. Live signals, full audit trail.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/worldclasstom/tally-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server