# Grants Gov (npm · @pipeworx/mcp-grants-gov)

Grants.gov MCP — open federal grant opportunities (free, no auth)

- Trust score: 82/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-grants-gov/grants-gov-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-grants-gov/grants-gov-mcp)
- npm · `@pipeworx/mcp-grants-gov`: 82/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-grants-gov/pipeworx-mcp-grants-gov.md), [page](https://verifymcp.io/servers/pipeworx-io-grants-gov/pipeworx-mcp-grants-gov)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-grants-gov`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-grants-gov).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add pipeworx-io-grants-gov -- npx -y @pipeworx/mcp-grants-gov
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-grants-gov": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-grants-gov"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-grants-gov": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-grants-gov"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-grants-gov -- npx -y @pipeworx/mcp-grants-gov
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-grants-gov": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-grants-gov"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-grants-gov --command npx --arg -y --arg @pipeworx/mcp-grants-gov
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-grants-gov:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-grants-gov"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-grants-gov": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-grants-gov"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-grants-gov -t stdio -c npx -a -y @pipeworx/mcp-grants-gov
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-grants-gov": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-grants-gov"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 82, +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.

### 2026-11-03 (score 81, +27)

- [security improvement] Known CVEs: unverified → pass
- [security improvement] Malware scan: unverified → pass
- [functional improvement] Dependency health: unverified → pass

### 2026-11-02 (score 54, −26)

- [security regression] Known CVEs: pass → unverified
- [security regression] Malware scan: pass → unverified
- [functional regression] Dependency health: pass → unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-11-01 (score 80, +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.

### 2026-10-30 (score 79, +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.

### 2026-10-29 (score 78)

First indexed and scored.

## MCP tools (5)

### `search_opportunities` (~645 tokens)

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).

Input parameters:

- `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…

### `get_opportunity` (~60 tokens)

Fetch full details for a Grants.gov opportunity by ID. Returns synopsis text, eligibility, award ceiling/floor, attachments, contact info, and version history.

Input parameters:

- `opportunity_id` (number, required): Numeric opportunity ID (returned by search_opportunities as "id")

### `search_historical_opportunities` (~510 tokens)

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".

Input parameters:

- `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…

### `get_historical_opportunity` (~116 tokens)

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`.

Input parameters:

- `opportunity_id` (number, required): Numeric opportunity ID (returned by search_historical_opportunities or search_opportunities as "id").

### `agency_posting_trend` (~169 tokens)

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.

Input parameters:

- `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).

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-grants-gov/pipeworx-mcp-grants-gov#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 81
- 2026-11-03: 81
- 2026-11-02: 54
- 2026-11-01: 80
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 78

## Common questions

### 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.

### What did VerifyMCP test on the Grants Gov MCP server?

VerifyMCP ran 16 checks on Grants Gov, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-grants-gov
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-grants-gov
- Repository: https://github.com/pipeworx-io/mcp-grants-gov
- Website: https://pipeworx.io/packs/grants-gov
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-grants-gov/pipeworx-mcp-grants-gov.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-grants-gov/pipeworx-mcp-grants-gov/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-grants-gov/pipeworx-mcp-grants-gov.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-grants-gov/pipeworx-mcp-grants-gov