Alphanume Datasets

com.alphanumePublished by alphanume.comOfficial publisherv1.8.0Updated Oct 29, 2026

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

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

Remote MCP server giving assistants point-in-time US equity and options datasets such as volatility premium, earnings moves, dilution, FDA events and splits.

What you can do
  • Access point-in-time US equity and options datasets through a hosted endpoint.
  • Work with volatility premium and earnings-move data.
  • Look into dilution, FDA event and stock split information.
  • No individual tools are listed, so the exact queries available are not documented here.
When to use it
Useful when an assistant needs historical or point-in-time US stock and options reference data for research, screening or analysis, rather than live trading or order execution.
Requirements
A remote streamable HTTP endpoint at mcp.alphanume.com with OAuth authentication. A required X-API-Key header carrying an Alphanume Pro API key (alp_...) obtained from the provider's pricing page.
Before you install
The server requires a paid Pro API key sent as the X-API-Key header, so expect a subscription or billing arrangement with the provider. Your queries and the key are sent to a third-party service. No tool list or documentation is provided, so review what data access the key grants before connecting.

Installation

In SourceWeft

  1. Open Alphanume Datasets in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.alphanume%2Fdatasets/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "alphanume-datasets": {
      "type": "http",
      "url": "https://mcp.alphanume.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

3
  1. v1.8.0LatestOct 29, 2026
  2. v1.7.0Oct 15, 2026
  3. v1.4.0Sep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.