# Federal Grant Evidence (remote · grants.utilityhouse.xyz)

Find U.S. federal grants and return cited hard-gate and award-history evidence packs.

- Trust score: 75/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `grants.utilityhouse.xyz`: 75/100 (this document), [markdown](https://verifymcp.io/servers/xyz-utilityhouse-federal-grant-evidence/mcp-registry-2.md), [page](https://verifymcp.io/servers/xyz-utilityhouse-federal-grant-evidence/mcp-registry-2)

## Channel facts

- Endpoint: `https://grants.utilityhouse.xyz/mcp/registry`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.3.2`

## Trust breakdown

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

Scored 2026-09-20.

- **Endpoint Security**: 71/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 89/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 61% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 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 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.

### Claude

```bash
claude mcp add --transport http xyz-utilityhouse-federal-grant-evidence 'https://grants.utilityhouse.xyz/mcp/registry'
```

### Cursor

```json
{
  "mcpServers": {
    "xyz-utilityhouse-federal-grant-evidence": {
      "url": "https://grants.utilityhouse.xyz/mcp/registry"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "xyz-utilityhouse-federal-grant-evidence": {
      "type": "http",
      "url": "https://grants.utilityhouse.xyz/mcp/registry"
    }
  }
}
```

### Codex

```toml
[mcp_servers.xyz-utilityhouse-federal-grant-evidence]
url = "https://grants.utilityhouse.xyz/mcp/registry"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "xyz-utilityhouse-federal-grant-evidence": {
      "type": "remote",
      "url": "https://grants.utilityhouse.xyz/mcp/registry",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add xyz-utilityhouse-federal-grant-evidence --url 'https://grants.utilityhouse.xyz/mcp/registry' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  xyz-utilityhouse-federal-grant-evidence:
    url: "https://grants.utilityhouse.xyz/mcp/registry"
```

### Netclaw

```json
{
  "McpServers": {
    "xyz-utilityhouse-federal-grant-evidence": {
      "Transport": "http",
      "Url": "https://grants.utilityhouse.xyz/mcp/registry"
    }
  }
}
```

### Vellum

```bash
assistant mcp add xyz-utilityhouse-federal-grant-evidence -t streamable-http -u 'https://grants.utilityhouse.xyz/mcp/registry'
```

### Other

```json
{
  "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.

## 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-09-20 (score 75, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-09-19 (score 75, +1)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-09-18 (score 74, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-09-17 (score 74, +1)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-09-16 (score 73, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-09-15 (score 73, +1)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-09-14 (score 72, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-09-13 (score 72, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

## MCP tools (7)

### `get_grant_document_manifest` (~105 tokens)

List a grant's official documents

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.

Input parameters:

- `opportunity_id` (string, required): Official Grants.gov opportunity ID, for example 332894

Output parameters:

- `collected_evidence` (object|null)
- `completeness` (string)
- `documents` (array)
- `latest_history_revision` (integer|null)
- `linked_documents` (array)
- `opportunity_id` (string)
- `opportunity_number` (string)
- `packages` (array)
- `reason_codes` (array)
- `revision` (integer|null)

### `analyze_nofo_requirements` (~144 tokens)

Read a grant's requirements from its official documents

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.

Input parameters:

- `claim_types` (array): Optional filter; omit for every requirement class.
- `opportunity_id` (string, required): Official Grants.gov opportunity ID, for example 332894

Output parameters:

- `claims` (array)
- `coverage` (object)
- `detail` (string)
- `manifest_completeness` (string)
- `observed_at` (string)
- `opportunity_id` (string)
- `revision` (integer|null)
- `snapshot_id` (string)
- `state` (string)
- `unread_documents` (array)

### `compare_grant_amendments` (~130 tokens)

Compare a grant's revisions

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.

Input parameters:

- `opportunity_id` (string, required): Official Grants.gov opportunity ID, for example 332894
- `since_revision` (integer): Optional; compare only revisions after this one.

Output parameters:

- `changes` (array)
- `current_revision` (integer|null)
- `detail` (string)
- `opportunity_id` (string)
- `pairs_compared` (integer)
- `pairs_observed` (integer)
- `pairs_unavailable` (integer)
- `revisions_observed` (array)
- `state` (string)
- `unavailable_pairs` (array)
- `worst_materiality` (string)

### `search_federal_grants` (~95 tokens)

Search federal grants

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.

Input parameters:

- `limit` (integer): Maximum results, from 1 to 20
- `query` (string, required): Topic or phrase such as community oral health

Output parameters:

- `count` (integer)
- `opportunities` (array)
- `query` (string)
- `sourceFreshness` (object)

### `analyze_federal_grant` (~110 tokens)

Analyze a federal grant

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.

Input parameters:

- `opportunity_id` (string, required): Numeric Grants.gov opportunity id from search_federal_grants
- `organization` (object, required)

Output parameters:

- `chargeable` (boolean)
- `funding` (object)
- `hardGates` (array)
- `limitations` (array)
- `officialRecordFreshness` (object)
- `opportunity` (object)
- `organization` (object)
- `productRelevance` (object)
- `programs` (array)
- `reasonCodes` (array)
- `recommendation` (string)
- `resultCompleteness` (string)
- `schemaVersion` (string)
- `sources` (array)
- `unresolved` (array)

### `get_federal_grant_evidence_pack` (~140 tokens)

Get a complete federal grant evidence pack

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.

Input parameters:

- `opportunity_id` (string, required): Numeric Grants.gov opportunity id
- `organization` (object, required)
- `request_id` (string, required): Caller-generated stable idempotency key; reuse it for retries

Output parameters:

- `billing` (object)
- `chargeable` (boolean)
- `funding` (object)
- `hardGates` (array)
- `limitations` (array)
- `opportunity` (object)
- `organization` (object)
- `programs` (array)
- `provenance` (object)
- `reasonCodes` (array)
- `recommendation` (string)
- `resultCompleteness` (string)
- `schemaVersion` (string)
- `scope` (object)

### `submit_federal_grant_profile_v2_beta` (~203 tokens)

Test an actual non-personal profile during the free beta

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.

Input parameters:

- `attest_current_actual_non_personal_facts` (boolean, required)
- `attest_intends_to_apply_to_opportunity_359701` (boolean, required)
- `consent_to_store_pointer_only_result` (boolean, required)
- `opportunity_id` (string, required)
- `profile` (object, required)
- `request_id` (string, required): Caller-generated UUID used only for idempotent replay

Output parameters:

- `pack` (object)
- `profileInputStored` (boolean)
- `proof` (object)
- `schemaVersion` (string)
- `storageDisposition` (string)
- `stored` (boolean)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/xyz-utilityhouse-federal-grant-evidence/mcp-registry-2#diagnostics

## Score history

- 2026-09-20: 75
- 2026-09-19: 75
- 2026-09-18: 74
- 2026-09-17: 74
- 2026-09-16: 73
- 2026-09-15: 73
- 2026-09-14: 72
- 2026-09-13: 72
- 2026-09-12: 72
- 2026-09-11: 71
- 2026-09-10: 70
- 2026-09-09: 69
- 2026-09-08: 20
- 2026-09-07: 69
- 2026-09-06: 69
- 2026-09-05: 68
- 2026-09-04: 68

## Common questions

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

## Links

- Remote endpoint: https://grants.utilityhouse.xyz/mcp/registry
- Repository: https://github.com/tytutueh13-sudo/federal-grant-evidence-mcp
- Website: https://grants.utilityhouse.xyz/from/registry
- Changelog RSS feed: https://verifymcp.io/servers/xyz-utilityhouse-federal-grant-evidence/mcp-registry-2.xml
- Changelog JSON feed: https://verifymcp.io/servers/xyz-utilityhouse-federal-grant-evidence/mcp-registry-2.json
- HTML version of this page: https://verifymcp.io/servers/xyz-utilityhouse-federal-grant-evidence/mcp-registry-2