MCP.Market

Alphanume Datasets MCP server

online · 100% uptime
by alphanume.com·com.alphanume/datasets·v1.8.0

Point-in-time US equity & options data: vol premium, earnings moves, dilution, FDA events, splits

B79/100grade B
What users say
No reviews yet
Be the first
Safety scan
B79/100

not scanned yet

Adoption
New

Little public usage data yet

Reviews

Write one

Nobody has reviewed Alphanume Datasets yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Alphanume Datasets tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Alphanume Datasets compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
79/100
higher than 58% of 48,243 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
331 ms
faster than 48% of 30,027 servers

Release history: 3 versions in the registry since 2026-09-13, latest 2026-10-28, typically one every 32 days.

Install Alphanume Datasets in Claude Code, Cursor or VS Code

claude mcp add --transport http datasets https://mcp.alphanume.com/mcp
Add to Cursor

Alphanume Datasets: common questions

Is Alphanume Datasets MCP server safe?
Mostly: it is graded B (79/100). Read the Alphanume Datasets safety report
How do I install Alphanume Datasets?
It runs remotely at mcp.alphanume.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Alphanume Datasets need an API key?
Yes. The registry entry asks for X-API-Key.
Is Alphanume Datasets maintained?
The latest release is v1.8.0.
Is Alphanume Datasets up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Alphanume Datasets compare with other MCP servers?
safety score 79/100 (higher than 58% of 48,243 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 331 ms (faster than 48% of 30,027 servers). Full comparison.