Federal Grant Evidence
REMOTE · GRANTS.UTILITYHOUSE.XYZ · SCANNED SEP 20
Find U.S. federal grants and return cited hard-gate and award-history evidence packs.
Available components
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 Security71
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability68
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1144 tokens (~163/item across 7 items; 7 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 Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 61% of tool parameters carry a description.Partial
- 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
How do I install the Federal Grant Evidence MCP server?
Federal Grant Evidence is a hosted endpoint at https://grants.utilityhouse.xyz/mcp/registry, 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 · grants.utilityhouse.xyz
claude mcp add --transport http xyz-utilityhouse-federal-grant-evidence 'https://grants.utilityhouse.xyz/mcp/registry'
{
"mcpServers": {
"xyz-utilityhouse-federal-grant-evidence": {
"url": "https://grants.utilityhouse.xyz/mcp/registry"
}
}
} {
"servers": {
"xyz-utilityhouse-federal-grant-evidence": {
"type": "http",
"url": "https://grants.utilityhouse.xyz/mcp/registry"
}
}
} [mcp_servers.xyz-utilityhouse-federal-grant-evidence] url = "https://grants.utilityhouse.xyz/mcp/registry"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"xyz-utilityhouse-federal-grant-evidence": {
"type": "remote",
"url": "https://grants.utilityhouse.xyz/mcp/registry",
"enabled": true
}
}
} openclaw mcp add xyz-utilityhouse-federal-grant-evidence --url 'https://grants.utilityhouse.xyz/mcp/registry' --transport streamable-http
mcp_servers:
xyz-utilityhouse-federal-grant-evidence:
url: "https://grants.utilityhouse.xyz/mcp/registry" {
"McpServers": {
"xyz-utilityhouse-federal-grant-evidence": {
"Transport": "http",
"Url": "https://grants.utilityhouse.xyz/mcp/registry"
}
}
} assistant mcp add xyz-utilityhouse-federal-grant-evidence -t streamable-http -u 'https://grants.utilityhouse.xyz/mcp/registry'
{
"mcpServers": {
"xyz-utilityhouse-federal-grant-evidence": {
"type": "http",
"url": "https://grants.utilityhouse.xyz/mcp/registry"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 20 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 19 Sept 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 18 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 17 Sept 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 16 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 15 Sept 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 14 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 13 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
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 20 Sept 2026 · Probed https://grants.utilityhouse.xyz/mcp/registry
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=utilityhouse.xyz | CN=WE1,O=Google Trust Services,C=US | 5 Sept 2026 | 4 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 236e6417e29787c313f5fc5b7c724a49 |
| SANs: utilityhouse.xyz, grants.utilityhouse.xyz, *.grants.utilityhouse.xyz | ||||||
| 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 grants.utilityhouse.xyz. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | present | 3599, 18130 | 8, 8 | Verified |
| utilityhouse.xyz. | present | 2371 | 13 | Verified |
| grants.utilityhouse.xyz. | 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=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' https://static.cloudflareinsights.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https:; font-src 'self' data:; connect-src 'self' https://api.usaspending.gov https://cloudflareinsights.com https://static.cloudflareinsights.com; frame-src 'none'; form-action 'self' https://accounts.google.com; frame-ancestors 'none'; base-uri 'self'; object-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://grants.utilityhouse.xyz/mcp/registry | Verified | 200 | |
| http (plaintext) | http://grants.utilityhouse.xyz/mcp/registry | Inconclusive | 405 |
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 →
analyze_federal_grant Analyze a federal grant ~110
Use this when the user needs a sourced go/no-go pursuit screen for one U.S. federal grant using a non-personal organization profile and the official opportunity record. The current preview is always free and explicitly marks unresolved project relevance, document, or award-history evidence. Do not use it for discovery only, legal eligibility advice, award prediction, drafting, or submission.
| Name | Type | Req | Description |
|---|---|---|---|
| opportunity_id | string | yes | Numeric Grants.gov opportunity id from search_federal_grants |
| organization | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| chargeable | boolean | yes | – |
| funding | object | yes | – |
| hardGates | array | yes | – |
| limitations | array | yes | – |
| officialRecordFreshness | object | yes | – |
| opportunity | object | yes | – |
| organization | object | yes | – |
| productRelevance | object | yes | – |
| programs | array | yes | – |
| reasonCodes | array | yes | – |
| recommendation | string | yes | – |
| resultCompleteness | string | yes | – |
| schemaVersion | string | yes | – |
| sources | array | yes | – |
| unresolved | array | yes | – |
No examples provided.
analyze_nofo_requirements Read a grant's requirements from its official documents ~144
Use this after the document manifest, when the user needs the requirements stated inside a U.S. federal grant's official announcement — eligibility, cost share, deadlines, page limits, required submissions and evaluation criteria — each with the document, page and exact source text it came from. It returns CONFIRMED, CONFLICT, UNKNOWN or EXTRACTION_INCOMPLETE per requirement and never fills a gap with an inference. It does not determine legal eligibility, predict an award, draft, or submit.
| Name | Type | Req | Description |
|---|---|---|---|
| claim_types | array | – | Optional filter; omit for every requirement class. |
| opportunity_id | string | yes | Official Grants.gov opportunity ID, for example 332894 |
| Name | Type | Req | Description |
|---|---|---|---|
| claims | array | – | – |
| coverage | object | – | – |
| detail | string | – | – |
| manifest_completeness | string | – | – |
| observed_at | string | – | – |
| opportunity_id | string | yes | – |
| revision | integer|null | – | – |
| snapshot_id | string | – | – |
| state | string | yes | – |
| unread_documents | array | – | – |
No examples provided.
compare_grant_amendments Compare a grant's revisions ~130
Use this when the user needs to know what changed between revisions of a U.S. federal grant opportunity — deadlines, cost share, eligibility, funding — with the before and after value for each change and how much it matters. It reads the official revision history and reports what Grants.gov itself declared changed alongside the computed difference. It does not read announcement documents, assess eligibility, predict an award, draft, or submit.
| Name | Type | Req | Description |
|---|---|---|---|
| opportunity_id | string | yes | Official Grants.gov opportunity ID, for example 332894 |
| since_revision | integer | – | Optional; compare only revisions after this one. |
| Name | Type | Req | Description |
|---|---|---|---|
| changes | array | – | – |
| current_revision | integer|null | yes | – |
| detail | string | – | – |
| opportunity_id | string | yes | – |
| pairs_compared | integer | – | – |
| pairs_observed | integer | – | – |
| pairs_unavailable | integer | – | – |
| revisions_observed | array | yes | – |
| state | string | yes | – |
| unavailable_pairs | array | – | – |
| worst_materiality | string | – | – |
No examples provided.
get_federal_grant_evidence_pack Get a complete federal grant evidence pack ~140
Use this limited free-beta tool after search or preview when the user wants a complete, versioned hard-gate and award-history evidence pack for one U.S. federal grant. It never requests payment during the beta. The service has a global daily beta capacity and counts only newly released complete results; reuse request_id for retries. It does not evaluate semantic project relevance, determine legal eligibility, predict an award, draft, or submit.
| Name | Type | Req | Description |
|---|---|---|---|
| opportunity_id | string | yes | Numeric Grants.gov opportunity id |
| organization | object | yes | – |
| request_id | string | yes | Caller-generated stable idempotency key; reuse it for retries |
| Name | Type | Req | Description |
|---|---|---|---|
| billing | object | yes | – |
| chargeable | boolean | yes | – |
| funding | object | yes | – |
| hardGates | array | yes | – |
| limitations | array | yes | – |
| opportunity | object | yes | – |
| organization | object | yes | – |
| programs | array | yes | – |
| provenance | object | yes | – |
| reasonCodes | array | yes | – |
| recommendation | string | yes | – |
| resultCompleteness | string | yes | – |
| schemaVersion | string | yes | – |
| scope | object | yes | – |
No examples provided.
get_grant_document_manifest List a grant's official documents ~105
Use this when the user needs to know which official documents a U.S. federal grant opportunity has, which revision is current, and whether the official record is complete. It returns every Full Announcement, revised announcement, supporting document and application package Grants.gov holds, with official download URLs. It does not read the documents, assess eligibility, predict an award, draft, or submit.
| Name | Type | Req | Description |
|---|---|---|---|
| opportunity_id | string | yes | Official Grants.gov opportunity ID, for example 332894 |
| Name | Type | Req | Description |
|---|---|---|---|
| collected_evidence | object|null | – | – |
| completeness | string | yes | – |
| documents | array | yes | – |
| latest_history_revision | integer|null | – | – |
| linked_documents | array | – | – |
| opportunity_id | string | yes | – |
| opportunity_number | string | – | – |
| packages | array | – | – |
| reason_codes | array | – | – |
| revision | integer|null | yes | – |
No examples provided.
search_federal_grants Search federal grants ~95
Use this when the user needs to find current or forecasted U.S. federal grant opportunities by topic. It returns official identifiers and source URLs for follow-up analysis. Do not use it to decide eligibility, predict an award, write an application, or submit anything.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum results, from 1 to 20 |
| query | string | yes | Topic or phrase such as community oral health |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| opportunities | array | yes | – |
| query | string | yes | – |
| sourceFreshness | object | yes | – |
No examples provided.
submit_federal_grant_profile_v2_beta Test an actual non-personal profile during the free beta ~203
Use this opt-in free-beta tool only when the user wants to test opportunity 359701 against current actual non-personal organization, project, and readiness facts. The user must explicitly attest that the facts are current, explicitly confirm intent to apply to this opportunity, and consent to storing the resulting pointer-only pack for 30 days. The raw profile, names, contact details, identifiers, narratives, documents, and credentials are not stored. Missing facts remain NEEDS_INPUT. It does not determine legal eligibility, predict an award, draft, or submit an application.
| Name | Type | Req | Description |
|---|---|---|---|
| attest_current_actual_non_personal_facts | boolean | yes | – |
| attest_intends_to_apply_to_opportunity_359701 | boolean | yes | – |
| consent_to_store_pointer_only_result | boolean | yes | – |
| opportunity_id | string | yes | – |
| profile | object | yes | – |
| request_id | string | yes | Caller-generated UUID used only for idempotent replay |
| Name | Type | Req | Description |
|---|---|---|---|
| pack | object | yes | – |
| profileInputStored | boolean | yes | – |
| proof | object | – | – |
| schemaVersion | string | yes | – |
| storageDisposition | string | yes | – |
| stored | boolean | yes | – |
No examples provided.
What is the Federal Grant Evidence MCP server?
Federal Grant Evidence is an MCP server listed in the public MCP registry as xyz.utilityhouse/federal-grant-evidence. Find U.S. federal grants and return cited hard-gate and award-history evidence packs. This page covers its hosted endpoint (https://grants.utilityhouse.xyz/mcp/registry).
Is the Federal Grant Evidence MCP server safe to use?
Federal Grant Evidence scores 75 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 Federal Grant Evidence MCP server expose?
Federal Grant Evidence exposes 7 tools: get_grant_document_manifest, analyze_nofo_requirements, compare_grant_amendments, search_federal_grants, analyze_federal_grant, and 2 more. Their descriptions and schemas cost roughly 927 tokens of context every time the server is loaded.
Does the Federal Grant Evidence MCP server require authentication?
No. We connected to Federal Grant Evidence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Federal Grant Evidence MCP server still maintained?
Federal Grant Evidence is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.