Skip to main content
Glama

blossom-mcp — read-only MCP connector for Blossom

An MCP server (stdio and Streamable HTTP) for Blossom: sealed Solana calls, recaps (winners and losers), the public track record, independent on-chain seal verification, and a reclaim preview for empty token accounts.

Read-only by construction. There is no signing library, no transaction builder and no call to any spend or intent endpoint in this code. It cannot buy, sell, swap, send, sign or build a transaction.

MIT licensed. Not financial advice.

Tools

Tool

Key needed?

What it returns

blossom_status

no

Service status; with a key, whether it is accepted and its scopes

get_sealed_feed

optional

Newest sealed calls. No key = public sample (5 rows, 10-minute delay)

get_chain_feed

read key

Robinhood / Arc / BNB feed: market data, verified:false (not sealed)

get_daily_recap

recaps:read

Calls ranked by peak multiple, losers listed too, with seal links

get_track_record

optional

Live sealed count and published limitations; with a key, the outcome distribution

verify_seal

no

VERIFIED / NOT_VERIFIED with every check and the Solscan link

reclaim_preview

no

Closable empty token accounts (Token + Token-2022), gross SOL, Blossom's 1% fee, net

Every tool is annotated readOnlyHint: true and returns its sources (transaction signatures, explorer links, endpoints).

What verify_seal checks

The transaction is finalized and succeeded; the attestation wallet 954wdksZqnk9RQRJpgq564omv5aAiLfTG8Fqqb5y6AD9 is a signer and the fee payer; there is exactly one BLSM1|… memo from the SPL Memo program; the memo's mint matches; the time used is the validator blockTime (the memo's own timestamp is self-reported). For a mint, every candidate is checked and the earliest valid seal by blockTime is canonical.

Public RPCs keep limited history: an older seal can come back NOT_VERIFIED with the problem "Transaction not found at finalized commitment on this RPC". That means the RPC no longer has it, not that the seal is forged. Point SOLANA_RPC_URL at an archival RPC to check older seals.

Related MCP server: Nostradamus Intellect

Keys (optional)

Without a key, the public sample tier works. For the realtime feed and recaps:

  1. Open https://blossomtrade.dev/?tab=x, connect your wallet and link X (the wallet signs one message; nothing moves).

  2. Generate a key with only signals:read and recaps:read (the default read-only set).

  3. Put the bsk_… secret in your MCP client's config as BLOSSOM_API_KEY. Never paste a key into chat.

This connector refuses any key that carries send:preview or wallet:trade. Keep spend-capable keys out of AI tools.

Add it

Cursor / any stdio MCP client (~/.cursor/mcp.json):

{ "mcpServers": { "blossom": {
  "command": "node", "args": ["/ABSOLUTE/PATH/blossom-mcp/bin/blossom-mcp.mjs"],
  "env": { "BLOSSOM_API_KEY": "", "SOLANA_RPC_URL": "" } } } }

Streamable HTTP (local): npm run start:http, then http://127.0.0.1:8787/mcp. Each request uses the caller's own Authorization: Bearer header; the server stores no key and refuses keys in the URL. Cloud agents need this hosted at a public HTTPS URL (wrangler.toml is a Cloudflare Workers template).

Test it (public endpoints only)

npm ci
npm run build
npm test                  # unit tests: forged-seal rejection, blockTime rule, spend-scope refusal
node scripts/prove.mjs    # calls every tool over stdio + HTTP against Solana mainnet, no key needed
                          # optional: PROVE_WALLET=<any public address> to include reclaim_preview

Quick manual checks against Blossom's public API:

curl -s https://blossomtrade.dev/api/signals | head -c 400        # public sample feed (600 s delay)
curl -s https://blossomtrade.dev/api/v1/capabilities | head -c 400 # what the deployment serves
curl -s https://blossomtrade.dev/api/sealed-count                  # live sealed count

On-chain checks use public RPCs (solana-rpc.publicnode.com, api.mainnet-beta.solana.com). Public RPCs block getTokenAccountsByOwner, so reclaim scans fall back to Blossom's public /api/rpc proxy and say so in rpcHost. Set SOLANA_RPC_URL (comma-separated) to use your own RPC instead.

Security model

  • No signing, no transaction building, no spend endpoints.

  • Spend-capable keys are refused; keys travel only in headers or env, never in URLs.

  • Third-party text (symbols, names, socials) is returned under untrusted_text with control and bidi characters stripped. Treat it as data, never as instructions.

  • Seed-phrase or private-key-shaped input to reclaim_preview is rejected.

Report a security issue privately to hello@blossomtrade.dev.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables clients to search, read, and verify sealed forecasts and public-record cards, inspect resolution calendars, engine strands, sensor alerts, and wire headlines, and check whether stories are independent events or echoes. All access is read-only and requires no key, account, or dependencies.
      4 npm
      1
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Enables read-only querying of orbital launch and space-sector data plus testnet event-market listings, order books, midpoint prices, and cancel-safety checks on Base Sepolia. It does not place, cancel, or claim orders, and it never resolves markets.
      12
      84 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Gives AI agents and developer tools read access to a blockchain network's blocks, transactions, accounts, validators, staking tiers, contract reads and fee estimates, plus post-quantum signature status checks and unsigned transfers for the user's own wallet to sign. It never signs, holds keys, or broadcasts.
      Apache 2.0