MCP evaluation

Run the SEC MCP evaluation runner

Use one shell runner to verify the hosted SEC Filing MCP Server before sending credentials. It checks discovery, public demo data, and subscription handoff, then runs an optional production sample when a buyer-controlled API key is present.

Evaluation runner
# Public setup checks
curl -L https://api.data-apis.com/downloads/sec-event-intelligence-mcp-evaluation-curl.sh -o sec-mcp-evaluation.sh
sh sec-mcp-evaluation.sh

# Optional authenticated production sample
MCP_API_KEY=your_data_apis_key sh sec-mcp-evaluation.sh

What the runner verifies

The public checks confirm that an MCP client can reach the server and discover the buyer handoff without a credential. The optional authenticated sample should only be used after choosing a paid access route.

Evaluation metadata

Directory reviewers, MCP client builders, and API buyers can use the same runner and ordered JSON-RPC workflow. The runner is suitable for command-line checks; the workflow JSON is suitable for clients that replay requests directly.

Runner metadata
{
  "mcpUrl": "https://api.data-apis.com/mcp",
  "runner": "https://api.data-apis.com/downloads/sec-event-intelligence-mcp-evaluation-curl.sh",
  "workflow": "https://api.data-apis.com/downloads/sec-event-intelligence-mcp-evaluation-workflow.json",
  "publicChecks": [
    "initialize",
    "tools/list",
    "prompts/list",
    "sec_demo_latest_filings",
    "sec_subscription_info"
  ],
  "optionalAuthenticatedCheck": "sec_latest_filings",
  "productionAuth": "x-api-key or Authorization: Bearer"
}

After the public checks pass

Use RapidAPI for REST endpoint subscriptions and generated snippets. Use hosted MCP access when a client needs production tools/call requests against https://api.data-apis.com/mcp.

Data infrastructure only. The runner verifies public SEC filing metadata tools and setup handoff links. It does not place trades, move money, modify accounts, or provide investment advice.