accueil / serveurs / Dev & Code / io.github.cyanheads/grantsgov-mcp-server
io.github.cyanheads/grantsgov-mcp-server
serveur MCP (Model Context Protocol) · grantsgov-mcp-server 0.1.3
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que io.github.cyanheads/grantsgov-mcp-server est sûr ?
Au dernier audit MCP Hub, le serveur MCP « io.github.cyanheads/grantsgov-mcp-server » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 3 outils
- grantsgov_get_opportunity≈ 9226 tokens
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.
Paramètres, retour & exemple (8)
Paramètresopportunity_ids· ? · optionnel
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 per list and 50 unique ids and numbers combined. Reads the first 5 identifiers, ids before numbers; remaining inputs have an executable continuation.attachment_offset· integer · optionnel
Zero-based attachment offset; defaults to 0. Page size 30.description_offset· integer · optionnel
Zero-based normalized description character offset; defaults to 0. Page size 12,000.eligibility_offset· integer · optionnel
Zero-based normalized eligibility character offset; defaults to 0. Page size 6,000.opportunity_numbers· ? · optionnel
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 array, with at most 50 nonblank entries per list and 50 unique ids and numbers combined. Reads the first 5 identifiers, ids before numbers; remaining inputs have an executable continuation. A number shared by several opportunities comes back as ambiguous with candidates.application_package_offset· integer · optionnel
Zero-based open package offset; defaults to 0. Page size 10.related_opportunity_offset· integer · optionnel
Zero-based related opportunity offset; defaults to 0. Page size 10.funding_category_explanation_offset· integer · optionnel
Zero-based normalized category explanation character offset; defaults to 0. Page size 2,000.
Exemple d'appel{"name": "grantsgov_get_opportunity", "arguments": {"opportunity_ids": "texte", "attachment_offset": 1, "description_offset": 1, "eligibility_offset": 1, "opportunity_numbers": "texte", "application_package_offset": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"error": {}, "notice": "texte", "unresolved": [], "continuation": {}, "deferred_ids": [], "opportunities": [], "deferred_numbers": []}} - grantsgov_list_reference≈ 1330 tokens
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.
Paramètres, retour & exemple (3)
Paramètrestopic· string · requis · agencies | eligibilities | funding_categories | funding_instruments | statuses | sort_options | keyword_syntax
Which list to return: agencies (agency codes), eligibilities (two-digit applicant-type codes), funding_categories, funding_instruments, statuses, sort_options, or keyword_syntax.parent_code· string · optionnel
Agencies only: list every code under this agency at any depth (e.g. HHS, DOD-DARPA). Case-insensitive. Omit for the top-level list.name_contains· string · optionnel
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-agency. Works with every topic. A value with no letters or digits matches nothing.
Exemple d'appel{"name": "grantsgov_list_reference", "arguments": {"topic": "agencies"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"error": {}, "topic": "agencies", "notice": "texte", "entries": [], "totalCount": 1, "snapshot_date": "texte"}} - grantsgov_search_opportunities≈ 4461 tokens
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.
Paramètres, retour & exemple (15)
Paramètressort· string · optionnel · relevance | open_date_desc | open_date_asc | close_date_asc | close_date_desc | opportunity_number_asc | opportunity_number_desc | agency_asc
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 sorts last on asc), opportunity_number_asc/_desc, agency_asc/_desc. Default: relevance with a keyword, else open_date_desc.limit· integer · optionnel
Requested rows per page (1-1,000; default 25). Values above 100 return 100 rows with a notice.offset· integer · optionnel
Zero-based row offset for paging; use next_offset from the previous page.keyword· string · optionnel
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"), exclude with NOT or -term, and use a trailing * for prefixes (broad*). OR mixed with AND or with bare terms must be grouped in parentheses, e.g. (rural OR tribal) broadband; an ungrouped mix is rejected. A word with an internal hyphen or period (COVID-19, K-12) is matched as a phrase. Field prefixes (agency:NSF, cfda:93.866) are rejected: use the agencies, assistance_listing, or other filter instead. See grantsgov_list_reference topic keyword_syntax.agencies· ? · optionnel
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 listed agency matches.statuses· ? · optionnel
Lifecycle statuses to include: forecasted, posted, closed, archived. One whole string or an array, up to 4 nonblank entries. Default: forecasted and posted.eligibilities· ? · optionnel
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 array of strings or numbers, up to 17 nonblank entries. A single digit is zero-padded (7 = 07). Any listed type matches.include_facets· boolean · optionnel
Include facet counts per filter value. Set false when paging to save space.assistance_listing· string · optionnel
One assistance listing number (ALN, formerly CFDA), e.g. 93.866 or 93866, in any case. Only one value is supported.funding_categories· ? · optionnel
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 category matches.opportunity_number· string · optionnel
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 match. To look up a number across every status, prefer grantsgov_get_opportunity with opportunity_numbers.posted_within_days· integer · optionnel
Only opportunities posted in the last N days (1-3650). Works only with the forecasted and posted statuses.closing_within_days· integer · optionnel
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 sort only close_date_asc.funding_instruments· ? · optionnel
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_unrestricted· boolean · optionnel
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.
Exemple d'appel{"name": "grantsgov_search_opportunities", "arguments": {"sort": "relevance", "limit": 1, "offset": 1, "keyword": "texte", "agencies": "texte", "statuses": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"cap": 1, "error": {}, "shown": 1, "facets": {}, "notice": "texte", "truncated": true, "totalCount": 1, "next_offset": 1, "opportunities": [], "applied_filters": {}, "effective_keyword": "texte"}}
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».