Business operationsPublic source

Market Data MCP Server

A market-data platform for ADK-Rust Enterprise banking and energy agents. 26 MCP tools covering instruments across asset classes, real-time quotes and historical bars, analytics (returns, volatility, correlation, moving…

Open the source Read the official guide ↗

What it gives an agent

A purpose-built capability behind one MCP connection.

The server owns its domain logic and publishes a tool contract an MCP client can discover. ADK-Rust can load that contract into an agent, normalize each schema for the chosen model provider, and keep the connection lifecycle outside the agent’s business logic.

Instruments & quotes — instruments across equity/bond/fx/commodity/rate/energy/index; latest bid/ask/last quotes (resolvable by id or symbol).

Historical bars — daily OHLC history (the historian).

Analytics — period return, min/max/mean, daily and annualized volatility (×√252), simple moving averages, and return correlation (Pearson) between instruments.

Curves — yield and forward term structures with linear interpolation (flat extrapolation beyond the ends).

FX — convert between currencies using direct, inverse, or USD-triangulated rates.

Benchmarks — equal-weighted index levels with member contributions.

Watchlists & alerts — instrument watchlists with live quotes; price alerts (above/below) evaluated on every new quote.

Architecture

How Market Data MCP Server fits into an agent system.

The model never needs the implementation details or credentials of the system behind the server. It sees reviewed tool definitions. The MCP client handles discovery and calls, while the server keeps ownership of validation, policy, and communication with its domain system.

ADK-Rust agent

Chooses a capability from the reviewed tool catalog.

→

MCP client

Discovers schemas, sends calls, and receives typed content.

→

Market Data MCP Server

Validates the request and owns 26 documented tool contracts.

→

Domain system

Keeps the API, data, credentials, and business rules behind the server.

Connection: stdio · Server framework: ADK MCP SDK + rmcp

Market Data MCP Server architecture diagram from its official repository

Tool catalog

What can an agent ask Market Data MCP Server to do?

Each tool has a stable name, a human-readable purpose, and a JSON input contract discovered during MCP initialization. Risk classes come from the project’s registry manifest when one is available.

26 named tools

create_instrument

Define an instrument across asset classes

internal write

get_instrument

Resolve an instrument by id or symbol

read only

list_instruments

List instruments by asset class

read only

set_quote

Set latest quote (evaluates price alerts)

internal write

get_quote

Get the latest quote

read only

add_bar

Add/replace a daily OHLC bar

internal write

history

Historical OHLC bars

read only

analytics

Return/volatility/min/max analytics

read only

moving_average

Simple moving average of closes

read only

correlation

Return correlation between two instruments

read only

create_curve

Create a yield/forward term-structure curve

internal write

list_curves

List curves by kind

read only

Governance

Understand the effect of every tool.

A server connection inherits the authority of its credentials and deployment environment. The declarations below come from this project’s README and MCP registry manifest; your application still decides which tools an agent receives and where approval is required.

18 read only7 internal write1 external write

One gated write — publish_mark is external_write + requires_approval: an official mark feeds downstream valuation, P&L, NAV, and collateral, so it carries real-world weight. Every other…
Everything material is audited — mark publication and data changes append to an audit trail (audit_log).
This is a reference/analytics engine with fictitious seed data; forecasts and analytics are simple, transparent methods (not investment advice).

MCP surface

What the current documentation declares.

MCP can carry tools, resources, prompts, structured results, progress, cancellation, and long-running work. This record highlights the modern protocol features explicitly mentioned by this repository.

The current README concentrates on its tool surface. Check the source and release notes before relying on optional MCP capabilities beyond tool discovery and invocation.

ADK MCP SDKrmcpRegistry manifest

Install and connect

Follow the project’s documented starting point.

Install the server in the environment that owns its credentials and domain access. Add it to your MCP host, verify the discovered tools, and narrow the toolset before giving it to a production agent.

Install

cargo install mcp-market-data

ADK-Rust connection shape

let toolset = McpToolset::from_stdio(
    "mcp-market-data",
    ["mcp-market-data"],
).await?;

let agent = LlmAgentBuilder::new("agent")
    .tools(toolset.tools().await?)
    .build()?;

Commands and configuration are extracted from the public README. Confirm prerequisites, environment variables, and release-specific options in the official documentation before deployment.

Official documentation

Continue with the project maintainers’ source of truth.

This page provides an approachable map of the server. The repository remains authoritative for exact schemas, prerequisites, configuration, examples, tests, releases, and security updates.

Overview ↗README.md CHANGELOG ↗CHANGELOG.md Architecture ↗docs/architecture.svg Issues and support ↗github.com issues

Keep exploring