Home / MCP registry index / io.github.tettertotter/fundinglandscape
FundingLandscape
io.github.tettertotter/fundinglandscape in the official MCP registry.
Endpoint https://fundinglandscape.com/api/mcp. Source: github.com/tettertotter/fundinglandscape.
The registry describes it as: Search 31,000+ open US grants, federal contracts, and foundations. Checked daily, free tier.
We read its 28 tools on 2026-10-22. 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_grants_and_procurement search_grantsplus search_procurement whats_new get_opportunity get_categories get_upgrade_link get_account_status sign_in get_setup_instructions get_tool_guide get_dataset_summary get_pricing get_pack_link report_feedback find_similar deadline_calendar search_foundations get_foundation find_funders_of funders_for_cause check_connection batch_search_procurement batch_search_grantsplus list_saved_searches save_search delete_saved_search update_saved_search
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-tettertotter-fundinglandscape)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.