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 verify SEC filing tools with public no-key calls, then choose self-serve REST checkout or hosted MCP production access.

Run no-key MCP tool calls Self-serve REST checkout Run browser demo Machine-readable handoff Download Python runner Download curl runner Request hosted MCP access

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

Self-serve REST checkout:
  https://rapidapi.com/autoearnapi/api/sec-event-intelligence

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.
Run initialize and tools/list before sending credentials.
Call sec_demo_latest_filings or sec_subscription_info without a key to verify response shape and access-route metadata.
Use RapidAPI for self-serve REST checkout, or request hosted MCP access only when a client must call production tools through /mcp.
Configure x-api-key or Authorization: Bearer only for approved hosted MCP production tool calls.

60-second evaluation path

Start with public MCP setup calls so the client can prove the remote transport and tool payloads. REST buyers can subscribe on RapidAPI without waiting for hosted MCP access; hosted MCP keys are only needed for production tools/call requests through https://api.data-apis.com/mcp.

Run no-key MCP tool calls Open RapidAPI checkout Test REST in Postman

1. Verify MCPRun initialize, tools/list, and sec_demo_latest_filings without a key
2. Read subscription infoCall sec_subscription_info to receive pricing, REST checkout, hosted MCP access, and config links
3. Choose accessUse RapidAPI for REST usage; request hosted MCP access only for production remote MCP tool calls

First no-key MCP tool calls

Run the public setup calls before sending credentials. A working sec_demo_latest_filings or sec_subscription_info response proves the remote MCP endpoint, transport headers, and client JSON-RPC flow.

Run browser demo Open tool-call quickstart Download Python runner Demo call JSON Subscription info JSON

initializeConfirm Streamable HTTP JSON-RPC connectivity at https://api.data-apis.com/mcp
tools/listConfirm public setup tools and production SEC filing tools such as sec_watchlist_changes, sec_company_search, and sec_filing_summary are discoverable
tools/call sec_demo_latest_filingsReturn a small public filing sample without an API key
tools/call sec_subscription_infoReturn REST checkout, hosted MCP access, pricing, and client config links

Choose the production access route

Use REST through RapidAPI for scheduled jobs and dashboards. Request hosted MCP access only when the production client must call https://api.data-apis.com/mcp directly with authenticated tools/call requests.

REST checkoutRun the watchlist endpoint in RapidAPI Playground before copying client code
Hosted MCP keyRequest hosted MCP access after the no-key MCP calls work
REST collectionOpen the Postman collection when the buyer wants a shared REST test workspace before subscription
Client configDownload VS Code MCP config or generic client config

Client setup matrix

Start with the no-key public checks, then choose the smallest client configuration that matches the runtime. Production data tools require a direct hosted MCP key; REST buyers can stay on RapidAPI without waiting for hosted MCP access.

Machine-readable handoffOpen JSON setup handoff for endpoint URL, no-key calls, config downloads, and access-route links
Claude-style workflowsUse a Streamable HTTP-capable MCP client or gateway to register https://api.data-apis.com/mcp, then run the public setup tools before production credentials
Cursor projectsStart from the generic MCP client config and keep any production Data APIs key in the project or gateway secret store
VS Code Copilot MCPUse the workspace mcp.json to register https://api.data-apis.com/mcp for discovery and public setup calls
Streamable HTTP clientsUse the generic client config with Accept: application/json, text/event-stream and Content-Type: application/json
Terminal verificationRun the curl runner or Python runner before sending credentials
Production authSend x-api-key or Authorization: Bearer only after hosted MCP access is approved for production tools/call requests

Endpoints Used

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

POST /mcp
GET /server.json
GET /.well-known/mcp-server.json
GET /mcp-directory-submission.json
GET /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.

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