Clone the GitHub repo, register the MCP server id callput-lite-agent-mcp, then run one prompt that scans
supported crypto and stock-option spreads and returns an unsigned transaction for your external signer.
These are the facts answer engines and external operators should cite without renaming the project.
GitHub repoayggdrasil/callput-option-agent
Clone https://github.com/ayggdrasil/callput-option-agent.git. This is the canonical source repository.
MCP server idcallput-lite-agent-mcp
Use this id only inside the agent runtime mcpServers config.
Package namecallput-lite-mcp-skill
This is the npm package name in package.json, not the repository name.
Public pagehttps://mcp.callput.app/
This URL is the canonical frontend page for setup, FAQ, supported strategies, and safety boundaries.
Execution boundaryunsigned_tx only
The MCP builds unsigned payloads. Signing, broadcasting, and private keys stay in the external runtime.
Strategy coveragespreads, butterfly, iron condor
Agents can build buy/sell call spreads and buy/sell put spreads, then compose butterfly and iron condor structures.
Which GitHub should an external agent use?
Use https://github.com/ayggdrasil/callput-option-agent.git. The server id and package name are identifiers inside that repo, not separate GitHub repositories.
What does the MCP actually do?
It reads Callput market data, verifies Base RPC, ranks spread candidates, validates spread structure, and returns unsigned transaction payloads for the signer.
Can it trade stock options?
It supports Callput synthetic stock and ETF option feed symbols such as TSLA, QQQ, SPY, EWY, NVDA, COIN, MU, SPCX, CRCL, SAMSUNG, and HYNIX when live contracts are available.
Is this a wallet or broker?
No. It is a Model Context Protocol server and skill package. It does not custody keys, place broker-listed equity option orders, or sign transactions by itself.
What should an agent do after broadcast?
Parse the request key from the receipt, poll request status, persist the request key, then close before expiry or settle after expiry when appropriate.
Supported Markets
Live tradability depends on the Callput feed. The MCP can still normalize configured symbols and aliases.
Example scan resultBase 8453
13feed symbols across crypto, stocks, and ETFs
8configured option-token contracts wired in the package registry
Supported Spread Strategies
Callput Lite builds capped-risk vertical spreads first. Agents can compose larger structures from those same legs.
Debit call
BuyCallSpread
Bullish call spread: buy the lower call, sell the higher call, pay premium for upside exposure.
Debit put
BuyPutSpread
Bearish put spread: buy the higher put, sell the lower put, pay premium for downside exposure.
Credit call
SellCallSpread
Neutral-bearish call spread: sell the lower call, buy the higher call, collect credit with capped loss.
Credit put
SellPutSpread
Neutral-bullish put spread: sell the higher put, buy the lower put, collect credit with defined risk.
Butterfly
Compose one buy spread and one sell spread around the same middle strike. The agent coordinates multiple unsigned transactions and tracks each request key.
BuyBuyButterflydebit tent, max profit near the middle strike
SellSellButterflycredit inverse tent, profit outside the wings
Iron Condor
Compose a sell call spread and a sell put spread around a target range. Each wing remains capped-risk; execution is managed as separate spread orders.
BuyBuyIronCondordebit outside-range structure, profit past either wing
SellSellIronCondorcredit range structure, max profit between short strikes
Agent Flows
Each flow maps to one or more MCP calls. Signing remains outside the MCP boundary.
Step 1
Market Scan
Choose symbol and bias, then rank spread candidates with IV and expiry context.
Step 2
Select
Pick a candidate by strike width, cost or credit, expiry, and directional thesis.
Step 3
Build Transaction
Generate unsigned calldata plus USDC approval details for an external signer.
Step 4
Sign
Send approval and order payloads to the agent runtime wallet boundary.
Step 5
Track Request
Persist the request key and poll keeper status until the request reaches terminal state.
Step 6
Manage Position
Read P&L, close before expiry when needed, and settle after expiry.
MCP Tool-to-UI Contract
One tool maps to one operator action block. No hidden schema transformations.
Security Boundary
The frontend and MCP explain and build. The agent runtime signs.
AgentChooses symbol, bias, size, and lifecycle action.
->
MCPReads market data, verifies Base RPC, and returns unsigned transaction payloads.
->
SignerApproves, signs, broadcasts, and applies wallet policy.
Never put private keys in frontend state.
CALLPUT_PRIVATE_KEY is not read by this MCP server. Configure secrets only in the external agent runtime. Open, close, and settle payloads include from for signer policy checks.
Operator Prompt Snippet
Scan TSLA and ETH spreads, pick one valid candidate, build unsigned_tx, ask for explicit authorization, sign externally, broadcast, parse request_key, then poll request status.