NetGrant — Canadian funding

–Likes are community signals, not a measured score.

Measured conclusion: Alive, not deep-tested. L2 outcome: not_attempted.

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

Author	ca.netgrant
Access	remote
Publisher key required	No
Measured state	Alive, not deep-tested
L1 liveness	alive
L1 latency	139 ms
Last measured	2026-10-26

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "NetGrant — Canadian funding": {
      "url": "https://mcp.netgrant.ca/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (5)

search_opportunities
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.
Parameters:
- 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.
- category — string — Optional: grant, competition, tax_credit, wage_subsidy, loan, event, workshop, conference, other
- 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.
- exclude_expired — boolean — Default true. Set false only if the user explicitly wants to see past-deadline or historical opportunities.
- 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 "closing soon" queries.
Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared
get_opportunity_details
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.
Parameters:
- id (required) — string — Opportunity UUID returned from search_opportunities
Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared
compare_opportunities
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.
Parameters:
- ids (required) — array — Array of 2–4 opportunity UUIDs (from search_opportunities) to compare.
Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared
eligibility_check
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.
Parameters:
- id (required) — string — Opportunity UUID to check eligibility for.
- applicant_description (required) — string — The applicant's details: sector, stage, location/province, incorporation status, size, demographics — whatever is relevant to eligibility.
Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared
subscribe_to_digest
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. Never invent, test with, or fill in a placeholder address (e.g. [email protected]) — if the user has not typed their real email in this conversation, do not call this tool. Undeliverable addresses are rejected with "Invalid email". 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").
Parameters:
- email (required) — string — The user's email address. Ask for it explicitly; never invent or assume it.
- keywords (required) — string — 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.
Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

Publisher website Repository

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.