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.

Subscribe on RapidAPI Request hosted MCP access Run MCP browser demo MCP first tool-call JSON Run watchlist in RapidAPI Playground Download curl runner Download MCP config Download Postman collection Security profile Access JSON

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.",
  "firstCallSuccessCriteria": {
    "expectedHttpStatus": 200,
    "rapidapiHost": "sec-event-intelligence.p.rapidapi.com",
    "recommendedEndpoint": "/v1/sec/watchlist/changes",
    "recommendedQuery": "tickers=AAPL,MSFT,NVDA&since=2026-07-01&limit=10",
    "requiredResponseFields": [
      "data",
      "meta"
    ],
    "successChecks": [
      "RapidAPI Playground returns HTTP 200 for the subscribed app.",
      "The request uses x-rapidapi-host and x-rapidapi-key headers.",
      "The JSON response contains data and meta fields.",
      "The same request runs from a backend, worker, or serverless function."
    ],
    "zeroUsageRecovery": [
      "A RapidAPI subscription alone does not create traffic.",
      "Run the endpoint in RapidAPI Playground before copying snippets.",
      "Use the subscribed RapidAPI app and the RapidAPI host, not the Data APIs base URL.",
      "Move the key to server-side code before scheduling production polling."
    ],
    "selfServeUrls": {
      "firstCallChecklist": "https://api.data-apis.com/first-call",
      "rapidapiSetup": "https://api.data-apis.com/rapidapi",
      "watchlistPlayground": "https://api.data-apis.com/events/sec-event-intelligence/rapidapi?target=first-call-watchlist-playground",
      "postmanCollection": "https://api.data-apis.com/events/sec-event-intelligence/download?target=postman-collection",
      "pythonRunner": "https://api.data-apis.com/events/sec-event-intelligence/download?target=sdk-first-call-python"
    }
  }
}

After sec_demo_latest_filings succeeds

A successful public tool call proves that the remote MCP server is reachable and the client can parse tool results. The next action is to call sec_subscription_info, then choose the self-serve REST route unless the client specifically needs production tools/call requests through MCP.

Call sec_subscription_info nextReturn RapidAPI checkout, first-call, hosted MCP access, pricing, and config URLs without credentials
REST defaultRun the watchlist endpoint in RapidAPI Playground when the client can call HTTP endpoints
First-call successConfirm HTTP 200 JSON with data and meta fields before scheduling jobs
Zero usage recoveryIf RapidAPI usage still shows zero, execute the endpoint from the subscribed RapidAPI app before moving snippets to code
MCP production onlyRequest hosted MCP access only when production tools/call requires a Data APIs key

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/changes
Hosted MCP directRequest hosted MCP access when your MCP client needs production tools/call data through https://api.data-apis.com/mcp
Machine-readable handoffRead access JSON for REST checkout, hosted MCP access, pricing, manifests, and evaluation links
No-key verificationRun initialize, tools/list, sec_demo_latest_filings, and sec_subscription_info before sending credentials
Runner to productionUse the curl runner without a key first; after adding MCP_API_KEY, SEC_API_KEY, or DATA_APIS_API_KEY, it also runs an authenticated sec_latest_filings sample

Continue without waiting

Hosted MCP access can be reviewed separately. A buyer can still verify the public MCP tools, run the REST watchlist endpoint, and import the request collection before a production MCP key is issued.

MCP no-key demoRun the browser demo for sec_demo_latest_filings and sec_subscription_info without credentials
Copyable tool callOpen first public tool-call JSON for JSON-RPC clients, terminals, and MCP client import checks
REST first requestRun the watchlist endpoint in RapidAPI Playground when the client can use REST immediately
Postman importDownload collection JSON and pair it with the public environment file for endpoint review
Client configDownload Streamable HTTP config for remote MCP client setup
Evaluation runnerDownload the curl runner to replay public checks before adding a buyer-controlled key

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/mcp
Curl runnerDownload the runner for no-key setup checks plus an optional authenticated sec_latest_filings sample
Client config/downloads/sec-event-intelligence-mcp-client-config.json
Directory kit/downloads/sec-event-intelligence-mcp-directory-kit.json
Server manifest/server.json
Security profile/.well-known/mcp-security.json

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.