PRODUCT — PLATFORM

MCP Server for AI Agents

MCP

A Model Context Protocol server that gives Claude, Cursor, and other MCP clients native tools for every live dataset. One URL, no glue code.

Tools your agent already knows how to call

The Model Context Protocol is the standard way AI clients call external tools. Our MCP server exposes each live dataset as a typed tool: query insider transactions, pull 13F positions, check proposed sales, look up fund holdings, walk a supply chain, list IPOs.

Setup is one URL. Add it in Claude, Cursor, Claude Code, or OpenCode, authenticate through the OAuth flow with your API key, and the tools appear in the client.

The server respects your account. It exposes only the datasets you subscribe to, and your key travels through the OAuth flow, never through the chat context.

What you get

Protocol
Model Context Protocol (MCP)
Clients
Claude, Cursor, Claude Code, OpenCode
Auth
OAuth flow with your API key
Scope
Only the datasets on your account
Setup
One server URL

Why teams use it

Native tool-use for LLMs

Agents call structured tools with typed arguments instead of scraping pages or guessing at endpoints. Answers come from real filings.

Works where your agents work

Connect from Claude, Cursor, Claude Code, or OpenCode. Add the server URL once and the tools appear in the client.

OAuth with your API key

Connecting triggers an OAuth flow authenticated with your RyxelData API key. No tokens pasted into chat, no shared credentials.

Respects your subscriptions

The server only exposes tools for the datasets on your account, so access stays scoped to what you pay for.

See it in code

mcp.json
json
{
  "mcpServers": {
    "ryxel": {
      "url": "https://mcp.ryxel.io"
    }
  }
}

What teams build with it

Research assistants

Ask Claude who bought shares in a name last week and get an answer built from the Form 4 record, with the source filing attached.

Coding agents with domain context

Cursor and Claude Code can pull live data while they build your integration, so examples and tests use real response shapes.

Desk copilots

An analyst asks questions in plain language; the agent queries the datasets and cites the filings behind each number.

Verified answers

Every tool response traces back to an SEC filing, so the agent cites primary sources instead of parametric memory.

Frequently asked questions

Which AI clients can connect to the MCP server?

Claude, Cursor, Claude Code, and OpenCode are covered in the docs. Any MCP-compatible client can connect using the server URL.

How does authentication work?

Connecting triggers an OAuth flow where you authenticate with your RyxelData API key. Contact us at [email protected] to get one.

What can an agent do once connected?

Query insider transactions, institutional holdings, proposed sales, funds, supply chain relationships, and IPO data, limited to the datasets enabled on your account.

Can I limit what an agent can query?

Yes. The server exposes tools only for the datasets on your account, so a key scoped to insider transactions can't touch the other datasets.

TALK TO US

Talk to us about access

Tell us what you're building and which datasets you need — we'll set you up with an account, an API key, and access to the data.