{
  "markdown": "# ProPublica Nonprofit Explorer — IRS Form 990 Data\n\nProPublica's Nonprofit Explorer aggregates IRS Form 990 filings: every nonprofit's tax return data with revenue, expenses, executive compensation, grants given/received, and program services. ~1.8M nonprofits indexed since 2001. Free, no auth.\n\nPart of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1476+ live data sources.\n\n## Why this matters for AI agents\n\nFor nonprofit research, \"where does this charity's money actually go?\" questions, executive compensation analysis, or tracing grant flows between foundations and recipients — Form 990 is the canonical data, and ProPublica makes it queryable. Pair with [USAspending](/docs/reference/usaspending) (federal grants), [OpenFEC](/docs/reference/open-fec) (political activity), and [SEC EDGAR](/docs/reference/edgar) (corporate philanthropy).\n\nCommon flows:\n\n- **Org lookup.** \"Find Form 990 filings for X\" → search by name or EIN.\n- **Org detail.** Latest filing year financials: revenue, expenses, top compensation, program ratios.\n- **Grant tracing.** \"Who has the X Foundation funded?\" → grants-given detail from Schedule I.\n- **Officer compensation.** Top employees with salary, benefits, and other compensation.\n\n## Auth\n\nNone. ProPublica's Nonprofit Explorer API is fully public, free.\n\n## What Form 990 reveals\n\n| Schedule | What it covers |\n|---|---|\n| Form 990 (full) | Required for orgs with ≥$200k revenue; full financial detail |\n| Form 990-EZ | Smaller orgs ($50k-$200k revenue); abbreviated |\n| Form 990-PF | Private foundations; grant-making detail |\n| Form 990-N | Tiny orgs (<$50k); postcard filing only |\n| Schedule I | Grants given to other orgs |\n| Schedule J | Compensation detail for top-paid employees |\n| Schedule O | Free-form supplementary disclosures (governance, mission detail) |\n\n## Common pitfalls\n\n- **990 lag.** Nonprofits file ~6-9 months after fiscal year-end. So 2024 fiscal-year data appears late 2025. Most-recent year is rarely current-year.\n- **Calendar vs fiscal year.** Different orgs use different fiscal years. \"FY 2023\" may end in any month. Check the period-end date.\n- **501(c)(3) vs (c)(4) vs (c)(6).** All file 990s but with different rules and political-activity restrictions. The classification matters more than total revenue for understanding what an org does.\n- **Compensation reporting nuances.** Top compensation includes salary + bonuses + retirement contributions + nontaxable benefits. The headline \"compensation\" number can vary depending on schedule used.\n- **Donor-advised funds (DAFs).** Money flowing through DAFs (Fidelity Charitable, Schwab Charitable) appears as the DAF receiving and granting — the actual donor and ultimate beneficiary may be opaque.\n- **501(c)(4) \"social welfare.\"** These can engage in some political activity but don't disclose donors. They show up here, but their political spending traces require [OpenFEC](/docs/reference/open-fec) cross-reference.\n- **Address normalization.** Org addresses often have suite numbers, PO boxes, and registered-agent addresses that aren't where the org actually operates. Cross-reference geographic claims with state corporate registries.\n\n## Quick Start\n\nAdd to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):\n\n```json\n{\n  \"mcpServers\": {\n    \"propublica-nonprofit\": {\n      \"url\": \"https://gateway.pipeworx.io/propublica-nonprofit/mcp\"\n    }\n  }\n}\n```\n\n### What this endpoint actually serves\n\n`tools/list` at `https://gateway.pipeworx.io/propublica-nonprofit/mcp` returns the tools in the table\nabove **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,\n`discover_tools`, `search_within`, `remember`/`recall` and the rest of the\ngateway-wide set. So the tool count you see is larger than this table: a\nsingle-pack endpoint currently lists roughly 30 shared tools alongside the\npack's own. The connection's `initialize` response states its exact scope, and\nis the authoritative answer for a given day.\n\nThis is deliberate, not multiplexing by accident. The meta-tools are what let a\nscoped connection answer a question this pack does not cover — via\n`ask_pipeworx`, which routes across the whole catalog — without you adding a\nsecond MCP server. There is currently no way to mount a pack endpoint without\nthem; if the extra schemas cost you more context than the routing is worth,\nconnect to the full gateway once rather than to several pack endpoints.\n\nOr connect to the full Pipeworx gateway to get every pack's tools listed\ndirectly, instead of just this one's:\n\n```json\n{\n  \"mcpServers\": {\n    \"pipeworx\": {\n      \"url\": \"https://gateway.pipeworx.io/mcp\"\n    }\n  }\n}\n```\n\nBoth URLs reach the same gateway and the same 1476+ data sources. The\nonly difference is which pack's tools are listed **directly**; `ask_pipeworx`\nreaches all of them from either one.\n\n## Using with ask_pipeworx\n\nInstead of calling tools directly, you can ask questions in plain English —\nthis works on the pack endpoint above as well as on the full gateway:\n\n```\nask_pipeworx({ question: \"your question about Propublica Nonprofit data\" })\n```\n\nThe gateway picks the right tool and fills the arguments automatically.\n\n## More\n\n- [Docs and guides](https://pipeworx.io/docs)\n- [pipeworx.io](https://pipeworx.io)\n\n## License\n\nMIT\n",
  "bytes": 5278,
  "sha": "38b7afd9219ac6c0c2c1c505d4c5e7d0dbd7e1515e6eaa631f13c52897b3cf48",
  "repo_slug": "pipeworx-io/mcp-propublica-nonprofit",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_pipeworx_io_propublica_nonprof_603c44a3/readme"
}