# NetGrant — Canadian funding (remote · mcp.netgrant.ca)

Search 1,300+ live Canadian funding opportunities — grants, tax credits, accelerators, and loans.

- Trust score: 66/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.netgrant.ca`: 66/100 (this document), [markdown](https://verifymcp.io/servers/ca-netgrant-canadian-grants/mcp.md), [page](https://verifymcp.io/servers/ca-netgrant-canadian-grants/mcp)

## Channel facts

- Endpoint: `https://mcp.netgrant.ca/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

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

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 74/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1579 tokens (~315/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http ca-netgrant-canadian-grants https://mcp.netgrant.ca/mcp
```

### Codex

```toml
[mcp_servers.ca-netgrant-canadian-grants]
url = "https://mcp.netgrant.ca/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ca-netgrant-canadian-grants": {
      "type": "remote",
      "url": "https://mcp.netgrant.ca/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ca-netgrant-canadian-grants --url https://mcp.netgrant.ca/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ca-netgrant-canadian-grants:
    url: "https://mcp.netgrant.ca/mcp"
```

### Other

```json
{
  "mcpServers": {
    "ca-netgrant-canadian-grants": {
      "type": "http",
      "url": "https://mcp.netgrant.ca/mcp"
    }
  }
}
```

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-08-03 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 65, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 64, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 62, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 62)

First indexed and scored.

## MCP tools (5)

### `search_opportunities` (~753 tokens)

Search Canadian funding opportunities (grants, competitions, accelerators, tax credits, wage subsidies, loans, events). Returns JSON.

WHEN TO CALL:
\- The user asks about Canadian funding, grants, competitions, accelerators, or pitch programs
\- The user mentions their startup/business and wants opportunities relevant to it
\- The user wants to see what's available in a specific province or category

WHEN NOT TO CALL:
\- General questions about how grants work (answer from your own knowledge)
\- Non-Canadian opportunities (this database is Canada-only)
\- Specific opportunity by ID (use get_opportunity_details instead)

HOW TO PRESENT RESULTS:
\- Render as a markdown table with columns: Title, Funder, Deadline, Funding, Region, Link
\- Sort by deadline ascending unless the user asked otherwise
\- For each opportunity, infer fit using what you know about the user's startup from the conversation. Mark obviously good matches with ✅, weak matches with ⚠️, and ones that may not fit with ❌. Be honest — do not mark everything ✅.
\- If a deadline is within 14 days, prefix the row with 🚨.
\- Always include the URL as a clickable markdown link.
\- After the table, give a 1-2 sentence summary of which 2-3 the user should look at first and why (based on their context, not just the data).
\- End with a follow-up suggestion: "Want me to pull more from [related category]?" or "Want me to draft an outline for [top match]?"

DATA NOTES:
\- "Rolling" deadline means no fixed close date.
\- Funding amount may be a range or "varies".
\- Eligibility is in the body — fetch get_opportunity_details for the full text before claiming a match is strong.
\- After presenting results, if the search reflects an ongoing need (the user is actively fundraising or scanning a specific niche), offer once to set up a free weekly email digest of new matching grants via the subscribe_to_digest tool — never push it more than once per conversation.

Input parameters:

- `category` (string): Optional: grant, competition, tax_credit, wage_subsidy, loan, event, workshop, conference, other
- `deadline_within_days` (integer): Optional. Only return fixed-deadline opportunities whose deadline falls between today and this many days from now. Rolling / no-fixed-deadline opportunities are EXCLUDED by this filter. Use for "clos…
- `exclude_expired` (boolean): Default true. Set false only if the user explicitly wants to see past-deadline or historical opportunities.
- `is_rolling` (boolean): Optional. true = only rolling/no-fixed-deadline opportunities; false = only those with a fixed deadline. Omit to include both.
- `max_funding` (integer): Optional. Only return opportunities with max_funding_amount <= this value (in CAD). Use with min_funding to bound a funding range, or alone to cap how large a program you want.
- `max_results` (integer): Default 20. Increase only if the user wants a comprehensive sweep.
- `min_funding` (integer): Optional. Only return opportunities with max_funding_amount >= this value (in CAD). Use when the user specifies a minimum funding threshold.
- `query` (string): Free-text search across title and body. Pass the user's actual keywords (e.g. "AI", "agriculture", "women-led").
- `region` (string): Optional province code: ON, BC, QC, AB, MB, SK, NS, NB, NL, PE, YT, NT, NU. Use Federal for nation-wide programs.

### `get_opportunity_details` (~105 tokens)

Fetch full details for a single opportunity by ID. Use this after search_opportunities when:
\- The user wants to know more about a specific match
\- You need the full eligibility text to confirm a strong-match claim
\- The user wants to draft an application — you need the requirements

The response includes all fields including the full body text and eligibility criteria. Present the eligibility as a checklist when relevant.

Input parameters:

- `id` (string, required): Opportunity UUID returned from search_opportunities

### `compare_opportunities` (~121 tokens)

Fetch 2–4 opportunities at once so you can present them side by side. Use after search_opportunities when the user is choosing between a few options.

Returns the full detail rows (including eligibility + body) for every id, in the order requested. Present them as a comparison table — rows = attributes (funding, deadline, region, eligibility highlights), columns = the opportunities — then recommend which fits the user best and why.

Input parameters:

- `ids` (array, required): Array of 2–4 opportunity UUIDs (from search_opportunities) to compare.

### `eligibility_check` (~165 tokens)

Pull a single opportunity's eligibility criteria alongside a description of the applicant, so you can judge whether they qualify. Use when the user asks "do I qualify for this?" or "does this apply to me?".

The response contains the opportunity's eligibility text + key fields and echoes the applicant description — it does NOT decide for you. Read the eligibility, compare it against the applicant, then give a clear verdict (Likely eligible / Partially / Unlikely) with the specific criteria that pass or fail and any criteria you can't determine from the description.

Input parameters:

- `applicant_description` (string, required): The applicant's details: sector, stage, location/province, incorporation status, size, demographics — whatever is relevant to eligibility.
- `id` (string, required): Opportunity UUID to check eligibility for.

### `subscribe_to_digest` (~435 tokens)

Subscribe the user to a FREE weekly email digest of Canadian funding opportunities matching a saved search (keywords + region). Each week they get 8–10 grants, newest first, falling back to the strongest current matches when nothing new landed.

WHEN TO CALL:
\- The user, after a search, says yes to ongoing alerts, or asks to be notified / kept updated / emailed about new grants in their niche.
\- Only after they have explicitly agreed and given an email address — never subscribe someone proactively or without consent.

HOW TO CALL:
\- Pre-fill "keywords" and "region" from the search you just ran so the digest matches what they were looking at (e.g. keywords "cleantech", region "BC"). Keep keywords to a short phrase, not a sentence.
\- "region" must be a province code (ON, BC, QC, AB, MB, SK, NS, NB, NL, PE, YT, NT, NU) or "Federal", or omit it for all-of-Canada.
\- Ask the user for their email; do not guess it.

WHAT HAPPENS:
\- We send a one-click confirmation email (double opt-in). The user is NOT subscribed until they click it. Tell them to check their inbox.
\- If they were already confirmed, nothing is re-sent.

Returns JSON: { ok: boolean, status: "confirmation_sent" | "already_subscribed" }. Confirm to the user what they signed up for (e.g. "weekly BC cleantech grants — check your email to confirm").

Input parameters:

- `email` (string, required): The user's email address. Ask for it explicitly; never invent or assume it.
- `keywords` (string, required): Short search phrase to match grants on, taken from the current search (e.g. "AI", "women-led agriculture", "cleantech"). Max ~200 chars.
- `region` (string): Optional province code (ON, BC, QC, AB, MB, SK, NS, NB, NL, PE, YT, NT, NU) or "Federal". Omit for nation-wide.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ca-netgrant-canadian-grants/mcp#diagnostics

## Score history

- 2026-08-03: 66
- 2026-08-02: 65
- 2026-08-01: 65
- 2026-07-31: 65
- 2026-07-30: 64
- 2026-07-29: 64
- 2026-07-28: 63
- 2026-07-27: 62
- 2026-07-26: 62

## Links

- Remote endpoint: https://mcp.netgrant.ca/mcp
- Repository: https://github.com/saman-ns/netgrant-mcp
- Website: https://netgrant.ca/
- Changelog RSS feed: https://verifymcp.io/servers/ca-netgrant-canadian-grants/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/ca-netgrant-canadian-grants/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/ca-netgrant-canadian-grants/mcp