reapx SEC filings - EDGAR company filings and full-text search MCP server

Checked 2026-09-07. Alive: no. Handshake: gated.

Category: legal-compliance. API and field schema.

Facts
idregistry--dev.reapx--sec-filings
namereapx SEC filings - EDGAR company filings and full-text search
registry_namedev.reapx/sec-filings
repo_urlnot available
endpoint_urlhttps://mcp.apify.com/?actors=reapx/sec-edgar-scraper
transportstreamable-http
aliveno
liveness_reasonstale
check_reachableyes
check_recent_commitno
check_installableyes
handshake_statusgated
handshake_checked_at2026-09-07T18:40:12Z
handshake_protocol_versionnot available
handshake_auth_hintBearer realm="OAuth", error="invalid_token", error_description="Missing or invalid access token. Pass an Apify API token in the Authorization: Bearer <token> header. Manage tokens at https://console.apify.com/account/integrations"
handshake_auth_discoverableurl
handshake_failure_layernone
handshake_latency_ms8732
handshake_tools_statenot available
handshake_tool_countnot available
maintenance_statusabandoned
last_commit_atnot available
categorylegal-compliance
license_spdxnot available
How to install or connect

Connect your MCP client to https://mcp.apify.com/?actors=reapx/sec-edgar-scraper.

What the checks mean

alive combines the applicable repository, package, and endpoint checks. A null result is not verifiable, not a failure. The MCP handshake is a separate structural probe and is not a security audit. Read the methodology.