Home / MCP registry index / com.modevc/radar

Mode VC: AI Venture Research Charts & Investor Atlas

com.modevc/radar in the official MCP registry. Endpoint https://modevc.com/api/mcp. Source: github.com/harrybuild/modevc-mcp.

The registry describes it as: Query 38 empirical AI market charts, evaluate distribution defensibility, and search 3,650+ VCs.

We read its 18 tools on 2026-10-27. 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

get_distribution_moat_score get_venture_chart_of_the_day search_charts get_chart_data search_investors get_investor_details get_mode_vc_thesis_and_criteria calc_safe_dilution calc_83b_qsbs_delaware calc_term_sheet_waterfall calc_burn_multiple_runway calc_saas_metrics calc_llm_inference_cost calc_fundraising_readiness calc_cofounder_equity get_new_raises get_firm_filings get_daily_ai_raises

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/com-modevc-radar/badge.svg)](https://lazaretto.dev/mcp-registry/com-modevc-radar)

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.