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.

Access route metadata
{
  "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.

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.

Data infrastructure only. The MCP server returns public SEC filing metadata and does not provide investment advice, ratings, recommendations, buy/sell signals, or personalized financial guidance.