Home / MCP registry index / io.github.valuein/mcp-sec-edgar
Valuein — SEC EDGAR Fundamentals & Smart-Money Data
io.github.valuein/mcp-sec-edgar in the official MCP registry.
Endpoint https://mcp.valuein.biz/mcp. Source: github.com/valuein/valuein.
The registry describes it as: Point-in-time, survivorship-free SEC EDGAR fundamentals + smart-money signals for AI agents.
We read its 127 tools on 2026-10-25. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
search_companies get_company_fundamentals get_valuation_metrics get_financial_ratios get_sec_filing_links list_filing_forms list_filing_sections read_filing_section find_in_filing get_capital_allocation_profile get_peer_comparables get_pit_universe get_compute_ready_stream describe_schema list_sops get_sop verify_fact_lineage verify_facts match_derived compare_periods screen_universe get_earnings_signals list_restatements submit_feedback submit_artifact_feedback get_insider_transactions get_institutional_holdings get_manager_portfolio get_blockholders get_insider_sentiment get_top_holders get_smart_money_flow save_thesis list_theses get_thesis delete_thesis restore_deleted score_thesis_outcome score_due_theses run_workflow list_public_theses_by_user publish_thesis unpublish_thesis save_claim list_claims get_claim delete_claim link_claim_to_thesis unlink_claim_from_thesis list_claims_for_thesis score_claim score_due_claims list_public_claims_by_user publish_claim unpublish_claim save_citation_override list_citation_overrides delete_citation_override save_figure_review list_figure_reviews and 67 more
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-valuein-mcp-sec-edgar)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.