MCP server for SEC EDGAR filings (10-K / 10-Q / 8-K), pay-per-call in USDC on Base via x402.
Three tools with identical empty input schemas ({}), minimal parameter descriptions, and no output schema documentation. Tool names lack action verbs (sec_filings_today, sec_filings_8k, sec_filings_service_info are noun-heavy). Descriptions are adequate in length (194-250 chars, within baseline 34-392 range) but lack actionable guidance on when to call each tool vs. alternatives. No parameter validation, no error recovery guidance, no pagination support despite 'max 40 per call' limit. Error handling returns raw upstream errors without LLM-actionable recovery steps.
Real-time stream of SEC EDGAR 8-K current reports — material corporate events such as M&A, officer changes, earnings releases, delisting and bankruptcy. Sorted by filing time descending, max 40 per call. Paid per call: $0.005 USDC on Base, settled automatically over x402.
Free discovery endpoint: describes the available SEC EDGAR data endpoints, their prices, payment network and wallet address. Use this first to check pricing before calling a paid tool.
Latest SEC EDGAR filings across 10-K, 10-Q and 8-K form types, sorted by filing time descending (max 40 per call, refreshed every 10 minutes). Each item: form type, company name + CIK, filing time (UTC), EDGAR archive URL. Paid per call: $0.01 USDC on Base, settled automatically over x402.
All three tools have empty input schemas ({}). No parameters are defined, validated, or described.
Tool names lack action verbs. 'sec_filings_today' and 'sec_filings_8k' are noun-heavy and do not clearly signal what action occurs when called. Should be 'get_sec_filings_today', 'list_sec_8k_events', 'describe_sec_filings_service'.
No output schema documented. LLMs cannot plan downstream calls or extract fields without knowing response structure. Descriptions mention 'form type, company name + CIK, filing time (UTC), EDGAR archive URL' but no formal schema is provided.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 40 | 2026-07-28+ | v2 |
Error handling returns raw upstream errors ('Upstream returned HTTP 402: ...') without LLM-actionable recovery guidance. Per pattern:recovery-guide, errors must tell the agent what to do next.
No pagination parameters (limit, offset, page) despite 'max 40 per call' limit. Large result sets risk context window exhaustion. No next_cursor or total_count in documented output.