Grants Gov
NPM · @PIPEWORX/MCP-GRANTS-GOV · 2 COMPONENTS
Grants.gov MCP — open federal grant opportunities (free, no auth)
Available components
Last scanned (10 hours ago)
Scores higher than 72% of npm servers
Category Education and Research
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-grants-gov). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability61
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1555 tokens (~311/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +27
- Known CVEs: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Dependency health: unverified → pass ▲ functional
- 2 Nov 26 −26
- Known CVEs: pass → unverified ▼ security
- Malware scan: pass → unverified ▼ security
- Dependency health: pass → unverified ▼ functional
- Package version: 0.2.0 → 0.2.1 functional
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 78
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-grants-gov@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-grants-gov |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-grants-gov/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3637337768 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:c60b3aecc4f2d4c90a32af0cf0ae12a80557be61417aba23a9fe76d0975290813835b9ae1149ec526861d98ff758710d4a4dc8d5829faa46827b1d7e8 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
agency_posting_trend ~169
An agency's opportunity-posting trend by federal fiscal year (Oct-Sep): how many opportunities it posted, total estimated program funding, and average award ceiling, per year. Answers "is this agency posting more or fewer opportunities than last year" and "how has this agency's funding trended". Fiscal year is derived from each opportunity's post_date.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Alias for agency_code. |
| agency_code | string | – | Agency or sub-agency code, e.g. "EPA", "NIH", "HHS-CDC1". Matches as a prefix/segment, same forgiveness as search_historical_opportunities. Alias: agency. |
| years | number | – | Number of most-recent fiscal years to return, 1-40 (default 10). |
No output schema declared.
No examples provided.
get_historical_opportunity ~116
Fetch one Grants.gov opportunity by its numeric opportunity ID, in ANY status (open, closed, archived, or forecasted) — unlike get_opportunity, which calls the live API and only reliably resolves currently-open opportunities. Returns the full record plus a computed `status` (derived from close/archive dates against today, the same vocabulary search_historical_opportunities uses) and `data_as_of`.
| Name | Type | Req | Description |
|---|---|---|---|
| opportunity_id | number | yes | Numeric opportunity ID (returned by search_historical_opportunities or search_opportunities as "id"). |
No output schema declared.
No examples provided.
get_opportunity ~60
Fetch full details for a Grants.gov opportunity by ID. Returns synopsis text, eligibility, award ceiling/floor, attachments, contact info, and version history.
| Name | Type | Req | Description |
|---|---|---|---|
| opportunity_id | number | yes | Numeric opportunity ID (returned by search_opportunities as "id") |
No output schema declared.
No examples provided.
search_historical_opportunities ~510
Search Grants.gov's FULL opportunity history (closed and archived opportunities back to 2004, plus forecasted opportunities not yet posted) — coverage search_opportunities' live API cannot serve, since search2 only usefully answers "what is open right now". Covers Grants.gov's full catalog, refreshed once a day (see `data_as_of`). Filter by agency code, CFDA/Assistance Listing number, keyword (full-text over title + description), status, opportunity category, or post-date range. Unlike search_opportunities, status here defaults to EVERY status, not just "posted" — pass status explicitly to narrow. Answers "what did this agency fund last fiscal year", "what opportunities under CFDA 93.351 have ever closed", "what is forecasted for next year that hasn't posted yet".
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Alias for agency_code. |
| agency_code | string | – | Agency or sub-agency code, e.g. "NIH" or "HHS-NIH11" or "DOS". Matches as a prefix/segment against the fully-qualified codes on file (same bare-vs-qualified forgiveness as search_opportunities' `agen… |
| aln | string | – | Alias for cfda. |
| cfda | string | – | Assistance Listing Number / CFDA number, exact match, e.g. "93.351". Alias: aln. |
| keyword | string | – | Full-text search over the opportunity title and description (PostgreSQL websearch syntax — quote a phrase, "-word" to exclude). More forgiving than the live tool's exact-phrase keyword match. |
| limit | number | – | Rows to return, 1-500 (default 25). |
| offset | number | – | 0-based start record, for paging. |
| opportunity_category | string | – | Single-letter Grants.gov category code: D discretionary, M mandatory, C continuation, E earmark, O other. |
| post_date_from | string | – | Only opportunities posted on/after this date, YYYY-MM-DD. |
| post_date_to | string | – | Only opportunities posted on/before this date, YYYY-MM-DD. |
| status | string | – | posted (open now) | closed | archived | forecasted (not yet posted). One value. There is no "open" or "active" status: use "posted" for opportunities open for applications. Omit to search every statu… |
No output schema declared.
No examples provided.
search_opportunities ~645
Search Grants.gov for currently-open or recently-closed federal funding opportunities. Filter by keyword, opportunity status, agency code, funding category, or date range. Returns opportunity number, title, agency, open/close dates, and assistance listing numbers (formerly CFDA).
| Name | Type | Req | Description |
|---|---|---|---|
| agencies | string | – | Comma-separated agency codes (e.g., "EPA,USDA" or a bare department like "HHS" or "NIH"). Grants.gov itself indexes opportunities under a FULLY-QUALIFIED sub-agency code ("HHS-NIH11", "HHS-CDC1", ...… |
| agency | string | – | Alias for `agencies` — a single agency or department code (e.g. "NIH" or "HHS"; see `agencies` for how a bare code is matched). |
| aln | string | – | Assistance Listing Number / CFDA number (e.g., "10.001") |
| funding_categories | string | – | Comma-separated category codes (e.g., "ED" education, "ENV" environment, "ST" science) |
| keyword | string | – | Grants.gov's own keyword match behaves like an exact/AND phrase across title and synopsis text, not a relevance-ranked full-text search — a compound multi-concept phrase (e.g. joining three unrelated… |
| limit | number | – | Rows per page (1-1000, default 25) |
| offset | number | – | 0-based start record (default 0) |
| open_only | boolean | – | true restricts to currently-open or forthcoming opportunities (same as status "posted|forecasted"); omit or false leaves status at its default. Alias for status when a caller only knows open/not-open… |
| status | string | – | posted (open for applications now) | forecasted (announced, not yet posted) | closed | archived. Default posted. There is no "open" or "active" status: use "posted". For posted plus forecasted togeth… |
No output schema declared.
No examples provided.
How do I install the Grants Gov MCP server?
Grants Gov runs locally as an npm package, launched with npx -y @pipeworx/mcp-grants-gov. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-grants-gov
claude mcp add pipeworx-io-grants-gov -- npx -y @pipeworx/mcp-grants-gov
What is the Grants Gov MCP server?
Grants Gov is an MCP server listed in the public MCP registry as io.github.pipeworx-io/grants-gov. Grants.gov MCP, open federal grant opportunities (free, no auth). This page covers its npm package (@pipeworx/mcp-grants-gov).
Is the Grants Gov MCP server safe to use?
Grants Gov scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Grants Gov MCP server expose?
Grants Gov exposes 5 tools: search_opportunities, get_opportunity, search_historical_opportunities, get_historical_opportunity, agency_posting_trend. Their descriptions and schemas cost roughly 1,500 tokens of context every time the server is loaded.
Is the Grants Gov MCP server still maintained?
Grants Gov is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Grants Gov MCP server under?
Grants Gov declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.