@agenticsrclab/tradeos-public-intel-mcp-server

@agenticsrclab/tradeos-public-intel-mcp-server

Read-mostly MCP server for the TradeOS public Data Intelligence layer.

Official MCP Registry name:

io.github.agenticsrclab/tradeos-public-intel-mcp

TRADEOS_API_BASE=https://api.tradeos.tech/v1/public-intel \
TRADEOS_ACCOUNT_TOKEN=<optional-account-token-for-watchlist-tools> \
TRADEOS_PUBLIC_INTEL_KEY=<optional-app-key-for-attribution> \
npx @agenticsrclab/tradeos-public-intel-mcp-server

Use it from Claude Desktop, Cursor, or another stdio MCP client to give an agent access to:

tradeos.get_market_digest
tradeos.get_public_candidates
tradeos.get_thesis_watchlist
tradeos.get_symbol_thesis
tradeos.get_evidence_packet
tradeos.get_public_claim_proof
tradeos.get_thesis_feedback
tradeos.get_credit_state
tradeos.watchlist_capabilities
tradeos.get_token_watchlist_snapshot
tradeos.get_symbol_cockpit
tradeos.bot_preflight
tradeos.list_x402_skus
tradeos.get_x402_sku_listing
tradeos.get_x402_sku_sample
tradeos.plan_x402_sku_call
tradeos.request_x402_payment_challenge
tradeos.call_x402_sku
tradeos.list_watchlists
tradeos.create_watchlist
tradeos.add_watchlist_item
tradeos.get_watchlist_state
tradeos.list_watchlist_events
tradeos.list_watchlist_deliveries
tradeos.trigger_watchlist_deliveries
tradeos.submit_digest_feedback
tradeos.submit_thesis_feedback
tradeos.submit_claim_outcome_feedback
tradeos.submit_watchlist_feedback

Feedback tools accept optional provenance fields:

feedbackSource: human | human_assisted | agent | automation | hybrid
automationLevel: none | assisted | automated | autonomous
agentId
agentRunId
agentModel
agentConfidence

tradeos.get_credit_state can return app reputation DTI for the configured public-intel app key. It does not expose personal human DTI; human DTI remains a signed-in TradeOS dashboard and Review Lab lifecycle.

The server does not place trades, accept exchange credentials, or expose private TradeOS telemetry.

Access model:

Free public kit: bounded reads, token snapshots, and feedback writes
Human DTI: public dashboard depth, public Ask packs, or read-only Review Lab where enabled
App reputation DTI: app-key feedback quality and quota confidence, not personal balance
Account token: saved watchlists, events, channels, delivery audit, and user-owned feedback
Paid TradeOS/x402: automation, exports, high-volume alerts, premium data, validation APIs

Paid x402 tools are explicit and buyer-controlled:

tradeos.list_x402_skus: discover free and paid TradeOS x402 SKUs
tradeos.get_x402_sku_listing: inspect one SKU listing
tradeos.get_x402_sku_sample: inspect a free synthetic sample
tradeos.plan_x402_sku_call: build method, body, endpoint, and headers without spending
tradeos.request_x402_payment_challenge: retrieve the x402 PAYMENT-REQUIRED challenge without payment
tradeos.call_x402_sku: execute only with execute=true and a caller-supplied signed payment header

The MCP server does not custody keys or sign wallet transactions. It tags paid call plans and requests with marketplace=mcp, X-TradeOS-Source-Type: agent, and X-TradeOS-Traffic-Class: external unless the caller chooses an operator test class.

TRADEOS_PUBLIC_INTEL_KEY is optional and used only when TradeOS has issued a public-intel app key for attribution. This MCP server can use the key, but it does not create keys.

Watchlist tools require TRADEOS_ACCOUNT_TOKEN. They expose research awareness, saved user state, and delivery audit only; they do not place trades or connect exchanges.

Optional x402 environment:

TRADEOS_X402_BASE_URL=https://tradeos.tech
TRADEOS_X402_AGENT_ID=<stable-agent-host-id>
TRADEOS_X402_PAYMENT_HEADER=<optional one-time buyer-signed payment header>
TRADEOS_X402_WALLET_ADDRESS=<optional buyer wallet address for paid calls>
TRADEOS_X402_PAYMENT_ID=<optional buyer payment id>

Learn more:

Homepage: https://tradeos.tech
Public docs: https://tradeos.tech/llms.txt
Key setup: https://github.com/agenticsrclab/tradeos-public-intel-kit/blob/main/docs/getting-api-keys-and-scale.md
x402 discovery: https://tradeos.tech/.well-known/x402.json

Official MCP Registry Publishing

The MCP Registry entry is already active for io.github.agenticsrclab/tradeos-public-intel-mcp. The registry metadata is in server.json; package mcpName in package.json must stay equal to server.json.name.

Local metadata check:

npm --workspace @agenticsrclab/tradeos-public-intel-mcp-server run registry:check

Publish prerequisites:

GitHub namespace: io.github.agenticsrclab/*
NPM package: @agenticsrclab/tradeos-public-intel-mcp-server
MCP registry name: io.github.agenticsrclab/tradeos-public-intel-mcp

Manual registry update from this directory after the npm package version is public:

mcp-publisher validate
mcp-publisher login github
mcp-publisher publish

CI publish uses .github/workflows/publish-mcp-registry.yml and GitHub OIDC for the MCP Registry. The workflow still needs an NPM_TOKEN repository secret when it is also publishing the npm package version. The npm package uses the @agenticsrclab scope because that scope is controlled by the same public distribution org used for GitHub registry authentication.