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.
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.
- Add https://api.data-apis.com/mcp as a remote MCP server URL in a client that supports Streamable HTTP remote servers.
- Configure x-api-key or Authorization: Bearer in clients that support custom request headers for remote MCP calls.
- Confirm the tool list includes sec_demo_latest_filings, sec_subscription_info, sec_watchlist_changes, sec_company_search, and sec_filing_summary.
- Call sec_demo_latest_filings or sec_subscription_info without a key, then use API-key headers for production filing tools.
Endpoints Used
The integration uses live SEC Event Intelligence endpoints available through RapidAPI subscriptions.
POST /mcpGET /server.jsonGET /.well-known/mcp-server.jsonGET /mcp-directory-submission.jsonGET /openapi.json
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.