io.github.VaibhavBansal26/grants-discovery-mcp-server
NPM · GRANTS-DISCOVERY-MCP-SERVER
Search US federal grants, read NOFO details, and research past awards. No API key.
Available components
Last scanned (40 minutes ago)
Scores higher than 44% of npm servers
Category Finance and Payments
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
- 0 of 3 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 779 tokens (~194/item across 4 items; 4 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 Management20
- Stability observed for 6 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 70
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 22 Nov 2026 · Analysed npm/grants-discovery-mcp-server@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 3 packages
| Packages resolved | 3 |
|---|---|
| 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 →
grants_get_opportunity Get Grant Opportunity Details ~102
Get the full announcement for one Grants.gov opportunity: summary, eligibility, award ceiling/floor, total funding, expected number of awards, cost sharing, key dates, and agency contact. Use grants_search_opportunities first to find the numeric opportunity ID.
| Name | Type | Req | Description |
|---|---|---|---|
| opportunity_id | integer | yes | Numeric opportunity ID from search results, e.g. 359145 |
| response_format | string | – | 'markdown' for readable text, 'json' for structured data |
No output schema declared.
No examples provided.
grants_list_filter_options List Grant Filter Options ~92
List valid filter codes for grants_search_opportunities: applicant eligibility codes, funding categories, and funding instruments, with how many current opportunities each matches. Call this when a user describes an applicant type (e.g. 'nonprofit', 'tribal government') or topic area and you need the matching code.
| Name | Type | Req | Description |
|---|---|---|---|
| response_format | string | – | 'markdown' for readable text, 'json' for structured data |
No output schema declared.
No examples provided.
grants_search_opportunities Search Grant Opportunities ~353
Search US federal funding opportunities on Grants.gov. Returns one page of matches with ID, number, agency, open/close dates, and status. If more results exist, the result gives next_offset; call again with that offset. Use grants_get_opportunity with an ID for the full announcement (award sizes, eligibility, contacts). Filter values are codes: agencies like 'HHS-NIH11' (prefix match, e.g. 'HHS'), eligibilities like '25' (use grants_list_filter_options for codes). Examples: - "Open diabetes research grants" -> keyword="diabetes", statuses=["posted"] - "Forecasted NIH opportunities" -> agencies=["HHS-NIH11"], statuses=["forecasted"] - "Grants for nonprofits on rural health" -> keyword="rural health", eligibilities=["25"]
| Name | Type | Req | Description |
|---|---|---|---|
| agencies | array | – | Agency codes, e.g. ['HHS-NIH11','USDA'] |
| aln | string | – | Assistance Listing Number (formerly CFDA), e.g. '93.847' |
| eligibilities | array | – | Applicant-type codes from grants_list_filter_options, e.g. ['25'] |
| funding_categories | array | – | Category codes, e.g. ['HL'] for Health |
| keyword | string | – | Free-text search over title and description, e.g. 'rural health' |
| limit | integer | – | Results per page |
| offset | integer | – | Records to skip, for pagination |
| response_format | string | – | 'markdown' for readable text, 'json' for structured data |
| statuses | array | – | Opportunity statuses to include. Default: posted and forecasted (still actionable) |
No output schema declared.
No examples provided.
grants_search_past_awards Search Past Federal Awards ~232
Search historical federal grant awards on USAspending.gov to see who has been funded, by whom, and how much. Useful for competitive research: find peer organizations funded for a topic, typical award sizes, and which agencies fund an area. Examples: - "Who got funded for rural diabetes programs in FY2024?" -> keyword="rural diabetes", fiscal_year_start=2024, fiscal_year_end=2024 - "What has Navajo Nation received?" -> recipient="Navajo Nation" Results are sorted by award amount, largest first.
| Name | Type | Req | Description |
|---|---|---|---|
| fiscal_year_end | integer | – | Last federal fiscal year |
| fiscal_year_start | integer | – | First federal fiscal year (Oct-Sep) |
| keyword | string | – | Topic text matched against award descriptions |
| limit | integer | – | Results per page |
| page | integer | – | Page number, starting at 1 |
| recipient | string | – | Recipient name search, e.g. 'University of Michigan' |
| response_format | string | – | 'markdown' for readable text, 'json' for structured data |
No output schema declared.
No examples provided.
How do I install the io.github.VaibhavBansal26/grants-discovery-mcp-server server?
io.github.VaibhavBansal26/grants-discovery-mcp-server runs locally as an npm package, launched with npx -y grants-discovery-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · grants-discovery-mcp-server
claude mcp add vaibhavbansal26-grants-discovery-mcp-server -- npx -y grants-discovery-mcp-server
What is the io.github.VaibhavBansal26/grants-discovery-mcp-server server?
io.github.VaibhavBansal26/grants-discovery-mcp-server is listed in the public MCP registry as io.github.VaibhavBansal26/grants-discovery-mcp-server. Search US federal grants, read NOFO details, and research past awards. No API key. This page covers its npm package (grants-discovery-mcp-server).
Is the io.github.VaibhavBansal26/grants-discovery-mcp-server server safe to use?
io.github.VaibhavBansal26/grants-discovery-mcp-server scores 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 November 2026. It declares no install or post-install scripts. 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 io.github.VaibhavBansal26/grants-discovery-mcp-server server expose?
io.github.VaibhavBansal26/grants-discovery-mcp-server exposes 4 tools: grants_search_opportunities, grants_get_opportunity, grants_list_filter_options, grants_search_past_awards. Their descriptions and schemas cost roughly 779 tokens of context every time the server is loaded.
Is the io.github.VaibhavBansal26/grants-discovery-mcp-server server still maintained?
io.github.VaibhavBansal26/grants-discovery-mcp-server is still listed as active in the MCP registry. We last reached this channel on 22 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 io.github.VaibhavBansal26/grants-discovery-mcp-server server under?
io.github.VaibhavBansal26/grants-discovery-mcp-server 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 io.github.VaibhavBansal26/grants-discovery-mcp-server server?
VerifyMCP ran 16 checks on io.github.VaibhavBansal26/grants-discovery-mcp-server, 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.