MCP access handoff
Choose access after your MCP setup call
If sec_demo_latest_filings or
sec_subscription_info sent you here, the remote MCP
server is reachable. Choose RapidAPI for REST endpoint usage, or
request hosted MCP access when your client must call production
MCP tools against https://api.data-apis.com/mcp.
{
"mcpUrl": "https://api.data-apis.com/mcp",
"publicTools": [
"sec_demo_latest_filings",
"sec_subscription_info"
],
"restCheckout": "https://rapidapi.com/autoearnapi/api/sec-event-intelligence",
"hostedMcpProductionAuth": "x-api-key or Authorization: Bearer",
"recommendedNextStep": "Use RapidAPI for REST endpoint access. Use hosted MCP direct access when an MCP client must call production data tools."
}
Pick the route that matches your client
REST clients should use RapidAPI for checkout, billing, quotas, and generated request snippets. MCP clients can run public setup calls without a key, then use a Data APIs key for production hosted MCP data tools.
REST self-serveSubscribe on RapidAPI when your app calls REST endpoints such as/v1/sec/watchlist/changesHosted MCP directRequest hosted MCP access when your MCP client needs productiontools/calldata throughhttps://api.data-apis.com/mcpNo-key verificationRuninitialize,tools/list,sec_demo_latest_filings, andsec_subscription_infobefore sending credentials
Production MCP authentication
Public setup tools stay open for connectivity checks. Production
SEC data tools require a buyer-controlled key sent as
x-api-key or Authorization: Bearer.
Endpointhttps://api.data-apis.com/mcpClient config/downloads/sec-event-intelligence-mcp-client-config.jsonDirectory kit/downloads/sec-event-intelligence-mcp-directory-kit.jsonServer manifest/server.json