Grants.gov Scraper: US federal grants search and alerts

io.github.bepolabsPublished by GitHub account bepolabsv1.0.0Updated Nov 12, 2026

US federal grants search and alerts, as one MCP tool through Apify

The publisher's own server: AlertsBar

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

Apify-hosted MCP server that lets an assistant search US federal grants and set up grant alerts.

What you can do
  • Search US federal grant listings through a single Apify-backed tool.
  • Set up alerts for grants so new or matching opportunities can be surfaced.
  • Runs as a remote Apify MCP endpoint rather than a local package.
When to use it
Useful when you want an assistant to look up US federal grant opportunities or keep track of new ones without leaving the chat.
Requirements
A remote connection to the Apify MCP endpoint at mcp.apify.com. Authentication is required: either an Apify API token sent as an Authorization bearer header, or signing in through OAuth.
Before you install
You must supply an Apify API token or authorize via OAuth, so the assistant's requests run against your Apify account. Tool details are not published, so confirm what the single tool does and whether alerts create or change anything before relying on it.

Installation

In SourceWeft

  1. Open Grants.gov Scraper: US federal grants search and alerts in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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.bepolabs%2Fus-grants/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "grants-gov-scraper-us-federal-grants-sea": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=bepolabs/us-grants"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 12, 2026

Score

67% 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
  • Auth declaredRequired10 pts
  • 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 Alerts integrations