Skip to main content
Glama
research-mcp
by atlas-rwa

research-mcp

MCP server that exposes ATLAS research capability to other agents: live tokenized stock data on Robinhood Chain, on-chain source-of-truth reads, and the research atlases published by the autonomous ATLAS agent. Any MCP capable client (Claude Code, Claude Desktop, custom agents) connects over stdio.

Works out of the box against the public Robinhood Chain testnet endpoints, no API keys needed.

Tools

Market data:

  • list_markets: the tokenized stocks on the chain, discovered by merging the Blockscout ERC-20 index (ranked by holders) with GeckoTerminal's trading pools (ranked by liquidity), each classified as equity or not

  • get_token_market: price, 1h/24h change, market cap, liquidity, and volume for a ticker or contract address, via GeckoTerminal

  • chain_tvl: the chain's TVL landscape from DefiLlama, with DEX venues and the RWA category called out

On-chain source of truth:

  • get_token_supply: ERC-20 total supply read directly from chain JSON-RPC at the current block

  • verify_token_contract: bytecode, on-chain name/symbol/decimals, block, and chain id for an address

  • get_token_holders: holder count and top-10 concentration from the Blockscout index

Published research (set ATLAS_API_URL to a running ATLAS deployment):

  • list_research_atlases: the agent's published research atlases, newest first

  • get_observation_history: the agent's recorded time series for a ticker, chain-tvl, or a contract address

  • get_agent_status: model, chain config, publish interval, and memory stats

Tickers resolve through discovery, so TSLA finds the tokenized Tesla contract without a hand written registry. Classification is a heuristic over symbol and name (issuer suffixes, tokenized-equity wording, and company-name corroboration for plain names like "Tesla"), so anything surprising can be verified on chain with verify_token_contract.

Related MCP server: TradingView MCP

Setup

npm install
npm run build

Configuration

All optional, via environment variables:

Variable

Default

Purpose

CHAIN_NAME

Robinhood Chain

Display name used in tool output

GECKOTERMINAL_NETWORK

robinhood

GeckoTerminal network slug

DEFILLAMA_CHAIN

Robinhood Chain

DefiLlama chain name

RPC_URL

public testnet RPC

EVM JSON-RPC endpoint for on-chain reads

BLOCKSCOUT_URL

public testnet explorer

Blockscout instance for token index and holders

ATLAS_API_URL

unset

Base URL of an ATLAS deployment, enables research feed tools

Connect a client

Claude Code:

claude mcp add atlas-research -- node /path/to/research-mcp/dist/index.js

Or in any MCP client config:

{
  "mcpServers": {
    "atlas-research": {
      "command": "node",
      "args": ["/path/to/research-mcp/dist/index.js"],
      "env": {
        "ATLAS_API_URL": "https://your-atlas-deployment"
      }
    }
  }
}

Available Tools

9 tools
chain_tvlA

Where capital sits on Robinhood Chain, from DefiLlama: total TVL, the largest protocols with 1d/7d change, the DEX venues where tokenized stocks actually trade, and the RWA-category subset. Use for market structure, venue depth, and trend analysis.

Inputs: no named parameters.

get_agent_statusA

Status of the ATLAS research agent: model, chain configuration, publish interval, atlas count, and memory stats. Requires ATLAS_API_URL.

Inputs: no named parameters.

get_observation_historyA

The ATLAS agent's recorded observation time series, for trend detection and day-over-day comparison. Keys: a ticker like 'TSLA' (price snapshots), 'chain-tvl' (TVL), or a contract address (on-chain supply and holders). Requires ATLAS_API_URL.

Inputs: key (required), limit.

get_token_holdersA

Holder count and top-10 holder concentration for an ERC-20 on Robinhood Chain, from the Blockscout index. Use to analyze how concentrated ownership of a tokenized asset is. Accepts a ticker or contract address.

Inputs: token (required).

get_token_marketA

Market view of a tokenized stock on Robinhood Chain: price, 1h/24h price change, market cap, pool liquidity, and 24h volume, via GeckoTerminal. Accepts a ticker (TSLA finds TSLAx) or an ERC-20 contract address.

Inputs: token (required).

get_token_supplyA

Source of truth: read an ERC-20's total supply directly from Robinhood Chain JSON-RPC at the current block. Use to verify issuance and redemption of a tokenized stock. Accepts a ticker or contract address.

Inputs: token (required).

list_marketsA

The tokenized stocks that exist on Robinhood Chain, discovered from the chain's trading pools rather than a hand written list. Returns ticker, contract address, liquidity, and why each was classified as an equity or not. Call this first to learn what is available to research.

Inputs: refresh, includeNonEquity.

list_research_atlasesA

The ATLAS agent's published research atlases: autonomous analyses of tokenized stocks and the RWA ecosystem, one per cycle, newest first. Each records the current conclusion, what changed since the previous atlas, and the evidence behind it. Requires ATLAS_API_URL.

Inputs: limit.

verify_token_contractA

Source of truth: verify an ERC-20 contract on Robinhood Chain: whether bytecode is deployed at the address, its on-chain name/symbol/decimals, the current block, and the chain id the RPC reports. Use before trusting a market quote.

Inputs: token (required).

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    A4.2/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct resource: market listings, token market data, supply, contract verification, holders, chain-level TVL, research atlases, observation history, and agent status. Even tools that share a resource (e.g., supply vs. verify) return non-overlapping information, and descriptions make their purposes clear.

    Naming Consistency4/5

    Most tools follow verb_noun pattern with get_ and list_ prefixes, e.g., list_markets, get_token_market, get_observation_history. The exception is chain_tvl, which uses a bare noun phrase, deviating slightly from the otherwise consistent convention.

    Tool Count5/5

    Nine tools is well within the ideal range for a focused research MCP. Each tool covers a specific aspect of the domain—market discovery, token analytics, chain metrics, and agent research—without redundancy or unnecessary bloat.

    Completeness5/5

    The tool set covers the full research lifecycle: discovering available markets, getting current and historical data, verifying on-chain facts, analyzing holders and liquidity, and accessing agent-generated research. No obvious missing operations for the stated purpose of researching tokenized stocks on Robinhood Chain.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      MCP server for the At Par Trading API — trade crypto, manage portfolios, and access market data from any MCP-compatible AI agent.
      16
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      A local-first MCP server providing market data, deterministic technical analysis, chart rendering, and optional TradingView Supercharts browser workflows via stdio and a loopback REST API.
      38
      3
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables MCP clients to retrieve TradingView market data, including historical OHLCV candles, quotes, technical indicators, and screener results over stdio or SSE.
      4
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      This MCP server enables research agents to access read-only A-share and US-equity market data, including prices, fundamentals, financial statements, news, and shareholder activity. It operates over stdio without requiring an API key for initial public sources.
      7
      MIT