Home / MCP registry index / biz.valuein/mcp
Valuein — SEC EDGAR Fundamentals & Smart-Money Data
biz.valuein/mcp 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 111 tools on 2026-11-10. 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 about every two weeks.
Connect it
The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:
claude mcp add --transport http valuein https://mcp.valuein.biz/mcp{
"mcpServers": {
"valuein": {
"url": "https://mcp.valuein.biz/mcp"
}
}
}code --add-mcp '{"name":"valuein","type":"http","url":"https://mcp.valuein.biz/mcp"}'Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.
Let Claude Code check servers as it adds them
With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.
claude plugin marketplace add lazaretto-ai/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-pluginsTools it advertises
search_companies get_company_fundamentals get_valuation_metrics get_financial_ratios get_sec_filing_links list_filing_forms latest_filings 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 verify_filing_figures compare_periods screen_universe get_earnings_signals list_restatements explain_restatement 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 restore_deleted undo_change run_workflow save_citation_override list_citation_overrides delete_citation_override save_figure_review list_figure_reviews delete_figure_review get_research_file sign_off_report verify_report_figures save_watchlist list_watchlists get_watchlist delete_watchlist set_agent_memory get_agent_memory delete_agent_memory watchlist_diff create_signal update_signal list_signals delete_signal test_signal and 51 more
Tool changes
We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.
Fingerprint of its tools at our last full read (2026-11-10):
078f124ee708fe23. A client can hash the tools it is served the same way and compare;
the full value and a hash per tool are in this page as JSON.
Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.
Run this server? Show the check in your README
The badge reflects the latest read:
[](https://lazaretto.dev/mcp-registry/biz-valuein-mcp)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. How tool poisoning works. What we found across the registry. Check another server.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.