Remote MCP setup

SEC API Remote MCP Client Setup

A hosted MCP setup guide for teams that want MCP-capable clients, IDEs, and internal agent runtimes to discover SEC filing tools without running a local EDGAR service.

POST /mcp
Remote MCP URL:
https://api.data-apis.com/mcp

Required headers for JSON-RPC requests:
  Accept: application/json, text/event-stream
  Content-Type: application/json

Authentication for tools/call:
  x-api-key: YOUR_DATA_APIS_API_KEY
  Authorization: Bearer YOUR_DATA_APIS_API_KEY

Discovery methods:
  initialize
  tools/list

Public demo tool:
  sec_demo_latest_filings

Public access info tool:
  sec_subscription_info

Workflow Setup

This recipe shows how to move SEC filing data into automation tools using live HTTPS endpoints and standard API credentials.

Endpoints Used

The integration uses live SEC Event Intelligence endpoints available through RapidAPI subscriptions.

Integration FAQ

Is this a local MCP server?

No. It is a hosted remote MCP endpoint. Buyers connect to the HTTPS URL instead of running a local EDGAR service.

Which clients can use it?

Use clients that support remote MCP URLs over Streamable HTTP and can send API key or bearer headers for data-returning tool calls.

Does the MCP endpoint provide investment advice?

No. It exposes public SEC filing metadata only and does not provide recommendations, ratings, signals, or personalized financial guidance.

No investment advice. These recipes move public SEC filing metadata into automation tools. They do not provide recommendations, ratings, signals, or personalized financial guidance.