io.github.cyanheads/grantsgov-mcp-server
REMOTE · GRANTSGOV.CASEYJHAND.COM · 2 COMPONENTS
Search Grants.gov funding opportunities and read full records: eligibility, awards, deadlines.
Available components
Last scanned (13 hours ago)
Scores higher than 94% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Education and Research
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1847 tokens (~461/item across 4 items; 3 tools + 1 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 Management90
- Stability observed for 27 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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 (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 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 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +3
- Schema quality: 581 → 461 ▲ functional
- First check of Schema quality: 100 functional
- Schema quality: excellent → good functional
- New resource “grantsgov-guide” functional
- Server version: 0.1.3 → 0.2.0 functional
- “grantsgov_list_reference” added an optional parameter “limit” cosmetic
- “grantsgov_list_reference” added an optional parameter “offset” cosmetic
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
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 · Probed https://grantsgov.caseyjhand.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=caseyjhand.com | CN=WE1,O=Google Trust Services,C=US | 2 Nov 2026 | 31 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 995a30681ab772540e934241ca1d576c |
| SANs: caseyjhand.com, *.caseyjhand.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of grantsgov.caseyjhand.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| caseyjhand.com. | DS published | 2371 | 13 | Verified |
| grantsgov.caseyjhand.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://grantsgov.caseyjhand.com/mcp | Verified | 200 | |
| http (plaintext) | http://grantsgov.caseyjhand.com/mcp | HTTPS enforced | 301 | https://grantsgov.caseyjhand.com/mcp |
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 →
grantsgov_get_opportunity Get Grants.gov Opportunity ~437
Read the Grants.gov record for up to 5 opportunities, given numeric opportunity ids or opportunity numbers: deadline, funding, eligibility, description, assistance listings, contact, attachments, packages, and latest revision metadata. Lists and narratives are bounded independent pages; follow each record pages continuation to retrieve the remaining section. An opportunity number is resolved across all statuses. A miss or an ambiguous number comes back as an unresolved entry with guidance, not an error.
| Name | Type | Req | Description |
|---|---|---|---|
| application_package_offset | integer | – | Zero-based open package offset; defaults to 0. Page size 10. |
| attachment_offset | integer | – | Zero-based attachment offset; defaults to 0. Page size 30. |
| description_offset | integer | – | Zero-based normalized description character offset; defaults to 0. Page size 12,000. |
| eligibility_offset | integer | – | Zero-based normalized eligibility character offset; defaults to 0. Page size 6,000. |
| funding_category_explanation_offset | integer | – | Zero-based normalized category explanation character offset; defaults to 0. Page size 2,000. |
| opportunity_ids | – | – | Numeric Grants.gov ids (e.g. 363423, or "363423" as search rows emit them), from grantsgov_search_opportunities opportunity_id. Accepts one whole string or an array, with at most 50 nonblank entries… |
| opportunity_numbers | – | – | Agency-assigned opportunity numbers (e.g. HRSA-27-005), matched exactly and case-insensitively across all statuses; one pair of surrounding double quotes is removed. Accepts one whole string or an ar… |
| related_opportunity_offset | integer | – | Zero-based related opportunity offset; defaults to 0. Page size 10. |
| Name | Type | Req | Description |
|---|---|---|---|
| continuation | object | – | Next identifier batch, omitted when the queue is exhausted. |
| deferred_ids | array | – | Unprocessed ids, omitted when none remain. |
| deferred_numbers | array | – | Unprocessed numbers, omitted when none remain. |
| error | object | – | Present when the call failed. Absent on success. |
| notice | string | – | Summary of unresolved inputs and what to call next. |
| opportunities | array | – | Records found, in input order. |
| unresolved | array | – | Inputs that did not resolve to exactly one record. Empty when all resolved. |
No examples provided.
grantsgov_list_reference List Grants.gov Reference Codes ~284
List the codes Grants.gov search filters accept, with labels and live opportunity counts: agencies (top level, or one agency's sub-agencies via parent_code, or matched by name via name_contains), applicant eligibility types, funding categories, funding instruments, statuses, sort options, and keyword syntax. Use the codes as grantsgov_search_opportunities inputs.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Entries per page; defaults to 50. Requests above the processing cap of 100 are clamped with a notice. |
| name_contains | string | – | Keep only entries whose label or code contains every word given, ignoring case, accents, and punctuation (e.g. "national science", "nih"). For agencies this searches every code, top-level and sub-age… |
| offset | integer | – | Zero-based offset into the complete filtered list; use continuation for the next page. |
| parent_code | string | – | Agencies only: list every code under this agency at any depth (e.g. HHS, DOD-DARPA). Case-insensitive. Omit for the top-level list. |
| topic | string | yes | Which list to return: agencies (agency codes), eligibilities (two-digit applicant-type codes), funding_categories, funding_instruments, statuses, sort_options, or keyword_syntax. |
| Name | Type | Req | Description |
|---|---|---|---|
| cap | number | – | Effective page size, at most 100. |
| continuation | object | – | Complete arguments for the next grantsgov_list_reference call; absent when no entries remain. |
| entries | array | – | Reference entries. |
| error | object | – | Present when the call failed. Absent on success. |
| notice | string | – | Guidance when name_contains matched nothing, or when parent_code has no sub-agencies. |
| reference_cache | object | – | Degraded reference-cache provenance; absent after a healthy refresh. |
| shown | number | – | Entries returned on this page. |
| snapshot_date | string | – | When the live vocabulary was fetched (ISO timestamp); absent for fully static topics. |
| topic | string | – | The topic listed. |
| totalCount | number | – | Total entries matching the filters before paging. |
| truncated | boolean | – | True when matching entries remain after this page. |
No examples provided.
grantsgov_search_opportunities Search Grants.gov Opportunities ~977
Search federal funding opportunities on Grants.gov by keyword, agency, applicant eligibility, funding category, funding instrument, assistance listing, opportunity number, posting window (posted_within_days), or closing window (closing_within_days). Returns forecasted and posted opportunities unless statuses says otherwise, each row led by its close date and days remaining, plus facet counts for narrowing. Bare keyword terms are all required; join alternatives with OR, in parentheses when other terms stay required. Rows carry no award amounts or eligibility detail; read those with grantsgov_get_opportunity. Filter codes come from grantsgov_list_reference.
| Name | Type | Req | Description |
|---|---|---|---|
| agencies | – | – | Agency codes from grantsgov_list_reference topic agencies (e.g. HHS, HHS-NIH11, NSF). One whole string or an array, up to 10 nonblank entries. A code includes its sub-agencies. Case-insensitive. Any… |
| assistance_listing | string | – | One assistance listing number (ALN, formerly CFDA), e.g. 93.866 or 93866, in any case. Only one value is supported. |
| closing_within_days | integer | – | Only posted opportunities closing between today and N days from today, US Eastern (0-365; 0 = closing today). Searches posted opportunities in close-date order, so statuses may only be posted and sor… |
| eligibilities | – | – | Two-digit applicant-type codes from grantsgov_list_reference topic eligibilities (e.g. 12 = nonprofits with 501(c)(3) status, 07 = federally recognized tribal governments). One whole string or an arr… |
| funding_categories | – | – | Funding category codes from grantsgov_list_reference topic funding_categories (e.g. HL = Health, ED = Education). One whole string or an array, up to 28 nonblank entries. Case-insensitive. Any listed… |
| funding_instruments | – | – | Funding instruments: G (grant), CA (cooperative agreement), PC (procurement contract), O (other). One whole string or an array, up to 4 nonblank entries. Any listed instrument matches. |
| include_facets | boolean | – | Include facet counts per filter value. Set false when paging to save space. |
| include_unrestricted | boolean | – | When eligibilities is set, also match opportunities open to any applicant type (code 99), which the specific codes do not cover. Set false to see only opportunities targeted at the listed types. |
| keyword | string | – | Full-text search over title, description, opportunity number, and agency. Bare terms are all required (rural broadband = rural AND broadband); join alternatives with OR, quote phrases ("mental health… |
| limit | integer | – | Requested rows per page (1-1,000; default 25). Values above 100 return 100 rows with a notice. |
| offset | integer | – | Zero-based row offset for paging; use next_offset from the previous page. |
| opportunity_number | string | – | Exact agency-assigned opportunity number (e.g. HRSA-27-005), matched case-insensitively; one pair of surrounding double quotes is removed. Numbers are not unique across agencies, so several rows can… |
| posted_within_days | integer | – | Only opportunities posted in the last N days (1-3650). Works only with the forecasted and posted statuses. |
| sort | string | – | Result order: relevance (best keyword match; needs keyword, otherwise the order is arbitrary), open_date_desc/open_date_asc (posting date), close_date_asc/close_date_desc (close date; no close date s… |
| statuses | – | – | Lifecycle statuses to include: forecasted, posted, closed, archived. One whole string or an array, up to 4 nonblank entries. Default: forecasted and posted. |
| Name | Type | Req | Description |
|---|---|---|---|
| applied_filters | object | – | Filters as the server applied them, including defaults and expansions. |
| cap | number | – | The limit applied. |
| effective_keyword | string | – | The keyword as compiled and sent upstream. |
| error | object | – | Present when the call failed. Absent on success. |
| facets | object | – | Counts per filter value for the current filters. Omitted when include_facets is false. |
| next_offset | number | – | Offset for the next reachable page of scanned matches; absent when none remain, even if the closing-window scan is incomplete. |
| notice | string | – | Zero-hit or window guidance naming the next call. |
| opportunities | array | – | Matching opportunities, deadline first. |
| reference_cache | object | – | Degraded reference-cache provenance when a filter uses stale vocabulary. |
| shown | number | – | Rows returned on this page. |
| totalCount | number | – | Matching opportunities counted. In closing_within_days mode, total_count_kind says whether this is exact or a lower bound. |
| total_count_kind | string | – | Closing-window count precision: exact after exhaustion or an observed boundary; lower_bound when unscanned rows may still qualify. Omitted in other modes. |
| truncated | boolean | – | True when more scanned matches remain after this page or a closing-window scan is incomplete, including on an empty page. |
No examples provided.
How do I install the io.github.cyanheads/grantsgov-mcp-server server?
io.github.cyanheads/grantsgov-mcp-server is a hosted endpoint at https://grantsgov.caseyjhand.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · grantsgov.caseyjhand.com
claude mcp add --transport http cyanheads-grantsgov-mcp-server 'https://grantsgov.caseyjhand.com/mcp'
What is the io.github.cyanheads/grantsgov-mcp-server server?
io.github.cyanheads/grantsgov-mcp-server is listed in the public MCP registry as io.github.cyanheads/grantsgov-mcp-server. Search Grants.gov funding opportunities and read full records: eligibility, awards, deadlines. This page covers its hosted endpoint (https://grantsgov.caseyjhand.com/mcp).
Is the io.github.cyanheads/grantsgov-mcp-server server safe to use?
io.github.cyanheads/grantsgov-mcp-server scores 87 out of 100 on VerifyMCP. 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.cyanheads/grantsgov-mcp-server server expose?
io.github.cyanheads/grantsgov-mcp-server exposes 3 tools: grantsgov_search_opportunities, grantsgov_get_opportunity, grantsgov_list_reference. Their descriptions and schemas cost roughly 1,698 tokens of context every time the server is loaded.
Does the io.github.cyanheads/grantsgov-mcp-server server require authentication?
No. We connected to io.github.cyanheads/grantsgov-mcp-server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.cyanheads/grantsgov-mcp-server server still maintained?
io.github.cyanheads/grantsgov-mcp-server 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 did VerifyMCP test on the io.github.cyanheads/grantsgov-mcp-server server?
VerifyMCP ran 13 checks on io.github.cyanheads/grantsgov-mcp-server, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.