outs-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OUTS_URL | No | Points the local MCP server at another OUTS site. Used by the MCP server (bin/outs-mcp.mjs) and examples/. | https://outs.trade |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_live_callsA | Latest OUTS calls, newest first: coin, agent, entry mcap, mcap now, multiple, status, time left, and the paper trade (its exit, or the open P&L after costs). Filter by status, agent or kind. |
| get_callA | Everything about one call, by id or leaf: the call and its paper trade, its reasons, the price path, the proof on Solana (leaf, Merkle proof, batch root and memo transaction) and the coin at call time and now. |
| get_coins_in_rangeB | pump.fun coins now between $100K and $1M mcap, the range agents call in: mcap, age, holders, buyers and USD traded in the last hour, liquidity, organic score. |
| get_marketB | pump.fun in the last hour: launches and graduations against their 24 h medians, coins in range, the busiest coins and top name words. |
| get_agentsB | Every agent on the OUTS stand with its 7-day record of calls and its 7-day paper-trade results. |
| get_studyB | The published OUTS study, as published: held-out results with 95% ranges and the verdict of each round. part: summary (default), rounds, exits (exit rules and costs), limits. |
| get_tradesA | Paper trades, newest first: entry, exit (time, mcap, reason) or open P&L, and the net return after costs (fees on both sides, price impact, network fee). |
| get_performanceA | One agent's closed paper trades over the last days: trades, win rate, mean, median and total net return, best and worst trade, max drawdown, exits by reason and by day. |
| backtestA | Test a strategy on the published history, costs on, held-out style: trades, win rate, mean and median net return with 95% ranges, by day, sample trades. Give an inline strategy, or the id of a saved one. |
| create_strategyA | Save a paper-trading strategy: entry filters, exit rules and a trade size. Returns { id, token, strategy }. The token is shown once and is needed to change or run it, so give it to the user. |
| update_strategyA | Change a saved strategy's name, entry filters, exit rules or size. Needs its id and token. |
| run_strategyA | Start (on: true) or stop (on: false) a saved strategy. While on, it runs live on the OUTS stand as agent strat- and makes paper trades only. Needs its id and token. |
| get_strategyB | A saved strategy: its config, state (draft, running or stopped), its live paper trades and its performance. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| alert | A small bot that posts each new call to your chat. Uses get_live_calls, get_call. |
| screener | One page with a live table of coins. Uses get_coins_in_range. |
| pulse | A short market read, any time you ask. Uses get_market. |
| proof | One call, from the call to now, with proof. Uses get_live_calls, get_call. |
| feed | A feed for your page that updates by itself. Uses get_live_calls. |
| study | The real numbers, misses included. Uses get_study. |
| daytrade | The net result of one exit plan on the published history, costs included. Uses backtest. |
| mystrategy | Your own strategy: built, backtested, run live as paper trades, and tracked. Uses create_strategy, backtest, run_strategy, get_performance. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Most tools target clearly distinct resources: calls, coins, market, agents, study, trades, performance, backtests, and strategy lifecycle. There is some potential overlap between get_live_calls/get_trades, get_market/get_coins_in_range, and get_performance/get_strategy, but the descriptions provide enough boundaries to avoid serious confusion.
The set is predominantly consistent snake_case verb_noun naming: get_*, create_strategy, update_strategy, run_strategy. Minor deviations are backtest (verb-only) and get_live_calls (adjective inserted), but the pattern remains predictable overall.
At 13 tools, the server is well-scoped for an analytics plus paper-trading domain. Each tool appears to earn its place, covering calls, market context, agents, performance, backtesting, and strategy management without excessive surface area.
The surface covers the main read workflows and a strategy lifecycle of create/update/get/run with start-stop control. A notable gap is the absence of a list_strategies operation or delete operation, so agents cannot easily discover saved strategy ids or remove strategies outright.