Home / MCP registry index / io.github.Kindora-PBC/foundation-discovery

io.github.Kindora-PBC/foundation-discovery

io.github.Kindora-PBC/foundation-discovery in the official MCP registry. Endpoint https://mcp.kindora.co/mcp. Source: github.com/Kindora-PBC/kindora.

The registry describes it as: Foundation discovery and grant intelligence for nonprofits. 174K+ US funders, IRS 990 data.

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

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http foundation-discovery https://mcp.kindora.co/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "foundation-discovery": {
      "url": "https://mcp.kindora.co/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"foundation-discovery","type":"http","url":"https://mcp.kindora.co/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. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

health_check list_tools search_funders get_funder_profile get_990_summary get_foundation_grants get_ntee_codes search_open_grants search_funder_jobs search_nonprofits search_organizations get_organization_profile find_funders_for_peers find_funders_of_nonprofit get_funder_stats start_kindora_profile start_connect_profile

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-kindora-pbc-foundation-discovery/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-kindora-pbc-foundation-discovery)

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.