Federal Grant Evidence

io.github.tytutueh13-sudoPublished by GitHub account tytutueh13-sudov1.1.0Updated Oct 24, 2026

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

The publisher's own server: AgentReady Woo

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

A remote MCP server that helps an assistant find U.S. federal grants and return cited evidence packs on eligibility gates and award history.

What you can do
Search U.S. federal grant opportunities from a connected assistant. Return evidence packs that cite hard-gate criteria for a grant. Return evidence packs that cite past award history. Present findings with citations rather than unsupported claims.
When to use it
Useful when you are researching U.S. federal funding options and want an assistant to locate relevant grants and back up eligibility and prior-award findings with citations.
Requirements
A remote MCP endpoint at the provider's host; no package installation, authentication, environment variables or headers are declared. Network access to the endpoint is required.
Before you install
The server is hosted by a third party, so grant queries and any details you include are sent to that provider. Grant and award information should be verified against official sources before you rely on it for an application.

Installation

In SourceWeft

  1. Open Federal Grant Evidence in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.tytutueh13-sudo%2Ffederal-grant-evidence/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "federal-grant-evidence": {
      "type": "http",
      "url": "https://utilityhouse.xyz/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

28% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Utilityhouse integrations