TradeOS Public Intelligence

io.github.agenticsrclabPublished by GitHub account agenticsrclabv0.1.3Updated Oct 24, 2026

Crypto market intelligence, evidence, watchlists, feedback, and paid x402 SKU routing.

VerifiedSTDIODesktop onlyFinanceData & Analytics

Overview

AI-generated overview

A local stdio MCP server that gives an assistant read-mostly access to TradeOS crypto market intelligence, evidence packets, watchlists and feedback tools.

What you can do
Retrieve market digests, public candidates, symbol theses and evidence or claim-proof packets for crypto research, plus credit state for the configured app key. Read saved watchlists, token snapshots, watchlist state, events and delivery records, and list watchlist capabilities. Create watchlists, add items and trigger watchlist deliveries. Submit digest, thesis, claim-outcome and watchlist feedback, optionally tagged with provenance fields such as agent model and confidence. Route explicit paid calls through an x402 gateway when configured.
When to use it
Useful when an assistant needs structured crypto market intelligence, supporting evidence for claims, or saved watchlists and delivery audits inside a desktop MCP client such as Claude Desktop or Cursor. It is aimed at research and awareness rather than trading.
Requirements
Runs locally over stdio, typically via npx with Node.js. Network access to the TradeOS public intelligence API, whose base URL can be set with TRADEOS_API_BASE. Watchlist tools require TRADEOS_ACCOUNT_TOKEN; TRADEOS_PUBLIC_INTEL_KEY is optional for attribution. Paid x402 calls use TRADEOS_X402_BASE_URL, TRADEOS_X402_AGENT_ID, TRADEOS_X402_WALLET_ADDRESS and TRADEOS_X402_PAYMENT_HEADER.
Before you install
The server states it does not place trades or accept exchange credentials, but watchlist tools write saved state and feedback tools submit data to TradeOS. Account, app-key and x402 payment header values are secrets; the payment header is described as buyer-signed and must not hold private keys. Paid x402 calls may incur charges, and the wallet address is sent with them.

Installation

In SourceWeft

  1. Open TradeOS Public Intelligence in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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

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

Official MCP Registry name:

text
io.github.agenticsrclab/tradeos-public-intel-mcp
bash
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:

text
tradeos.get_market_digesttradeos.get_public_candidatestradeos.get_thesis_watchlisttradeos.get_symbol_thesistradeos.get_evidence_packettradeos.get_public_claim_prooftradeos.watchlist_capabilitiestradeos.get_token_watchlist_snapshottradeos.list_watchliststradeos.create_watchlisttradeos.add_watchlist_itemtradeos.get_watchlist_statetradeos.list_watchlist_eventstradeos.list_watchlist_deliveriestradeos.trigger_watchlist_deliveriestradeos.submit_digest_feedbacktradeos.submit_thesis_feedbacktradeos.submit_claim_outcome_feedbacktradeos.submit_watchlist_feedback

Feedback tools accept optional provenance fields:

text
feedbackSource: human | human_assisted | agent | automation | hybridautomationLevel: none | assisted | automated | autonomousagentIdagentRunIdagentModelagentConfidence

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:

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

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.

Learn more:

text
Homepage: https://tradeos.techPublic docs: https://tradeos.tech/llms.txtKey setup: https://github.com/agenticsrclab/tradeos-public-intel-kit/blob/main/docs/getting-api-keys-and-scale.mdx402 discovery: https://tradeos.tech/.well-known/x402.json

Official MCP Registry Publishing

The registry metadata is in server.json. The package mcpName in package.json must stay equal to server.json.name.

Local metadata check:

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

Publish prerequisites:

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

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

bash
mcp-publisher validatemcp-publisher login githubmcp-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.

Source: packages/mcp-server/README.md at commit 11bab42

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.3LatestSep 16, 2026

Score

40% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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.