# Grants Qualification MCP Server (`nexgenwatch/grants-qualification-mcp`) Actor

Report what a US federal grant agency actually states about who may apply, and screen an applicant type against it. Three outcomes, and 'qualified' is not one of them.

- **URL**: https://apify.com/nexgenwatch/grants-qualification-mcp.md
- **Developed by:** [NexGen Watch](https://apify.com/nexgenwatch) (community)
- **Categories:** Agents, Business
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $50.00 / 1,000 tool calls

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Grants Qualification MCP Server

Report what a US federal grant agency **actually states** about who may apply — the coded
applicant types, the free-text eligibility narrative, cost-sharing, award range and close date —
and screen an applicant type against it.

### This server will not tell you that you qualify

It has three screening outcomes and **"qualified" is not one of them**:

| outcome | meaning |
|---|---|
| `CLEAR_MISMATCH` | the applicant type is **not** in the agency's coded list — the one negative the coded list supports |
| `NOT_EXCLUDED_BY_THE_CODED_LIST` | the type appears in the list. **Not** a determination — the narrative may add conditions |
| `CANNOT_DETERMINE` | the coded list defers to the prose, states no types, or none was supplied |

**Why.** Grants.gov states eligibility in two places and they are not equivalent: a coded
`applicantTypes` list, and a free-text narrative. The narrative routinely carries geography,
sector, prior-award and partnership conditions no coded list can express — and agencies edit it
roughly **12× more often** than the coded list.

The first posted opportunity read during this server's own source check makes the point:

```
coded applicant types : [{"id": "25", "description": "Others (see text field
                          entitled \"Additional Information on Eligibility\")"}]
eligibility narrative : "The following organizations are eligible to apply:
                         - Indonesia-based ..."
```

The coded field says, in effect, *the rule is not in this field*. A server screening on it alone
would answer "eligible applicant type: Others" to an agent asking on behalf of a US nonprofit.
So **deferral is detected and reported**, and screening returns `CANNOT_DETERMINE` with the
narrative handed back to read.

### Tools

| tool | what it answers |
|---|---|
| `find_opportunities` | Currently posted opportunities, each with its number, close date and Grants.gov URL |
| `get_eligibility` | Everything stated about who may apply, including whether the coded list defers to prose |
| `screen_applicant` | Screen one applicant type — three outcomes, never "qualified" |
| `explain_outcomes` | What each outcome means and why there is no "qualified". Read before acting. |

### Scope

**US federal discretionary grants on Grants.gov. One jurisdiction.** UK Find a Grant was probed
and both documented API paths returned 404, so it is not covered and this server does not imply
otherwise.

Sources, public and logged-out, no key: `api.grants.gov/v1/api/search2` and
`api.grants.gov/v1/api/fetchOpportunity`. Every outbound call is paced through one shared
strict-pacing bucket at 5 requests/second.

### Pricing

| Event | Price |
|---|---|
| Server start (`apify-actor-start`) | $0.05, charged once per server run by the platform |
| Tool call (`mcp-tool-call`) | **$0.05 flat per completed tool call** |

No other events. **Errors and notices are not charged** — a bad opportunity id, an empty
applicant type, or a Grants.gov read failure returns without billing. A sourced answer,
including a `CANNOT_DETERMINE`, **is** charged: it is the honest answer to the question asked.

If a tool call cannot be billed correctly, **the call fails** rather than serving free.

# Actor input Schema

## `note` (type: `string`):

This Actor runs as an MCP server in Standby mode. Connect an MCP client to the server URL with path /mcp; there is no batch input to fill in.

## Actor input object example

```json
{
  "note": "standby"
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "note": "standby"
};

// Run the Actor and wait for it to finish
const run = await client.actor("nexgenwatch/grants-qualification-mcp").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "note": "standby" }

# Run the Actor and wait for it to finish
run = client.actor("nexgenwatch/grants-qualification-mcp").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "note": "standby"
}' |
apify call nexgenwatch/grants-qualification-mcp --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgenwatch/grants-qualification-mcp"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/EeECsd8tL5BZrfiA3/builds/eFY5XE9EDcgvmPLQO/openapi.json