Skip to main content
Glama

NetGrant — Canadian funding

Server Details

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

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-03-26
URL
Repository
saman-ns/netgrant-mcp
GitHub Stars
0
ChatGPT
–
Claude
–

TDQS

A4.5/5.0

Scored across 5 tools

Disambiguation4/5

Each tool targets a distinct step in the discovery workflow: search, single-detail, multi-comparison, eligibility check, and digest subscription. There is some overlap in that compare_opportunities and get_opportunity_details both return full opportunity rows, and eligibility_check also surfaces eligibility criteria, but the provided triggers and output differences make misselection unlikely.

Naming Consistency4/5

All names are snake_case and mostly follow verb_object: search_opportunities, get_opportunity_details, compare_opportunities, subscribe_to_digest. eligibility_check breaks the verb-first pattern slightly, and subscribe_to_digest inserts a preposition, but the pattern remains predictable and readable.

Tool Count5/5

Five tools is well-scoped for a funding-search server: search, detail, comparison, eligibility assessment, and subscription. Each tool has a clear role and none feel redundant or missing from the core workflow.

Completeness4/5

The discovery and assessment lifecycle is well covered: search → details → compare → eligibility → digest. The only notable gap is that subscribe_to_digest has no accompanying unsubscribe or subscription-management tool, leaving a mild dead end for users who want to stop the digest.

Available Tools

5 tools
compare_opportunitiesAInspect

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.

Inputs: ids (required).

eligibility_checkAInspect

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.

Inputs: id (required), applicant_description (required).

get_opportunity_detailsAInspect

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.

Inputs: id (required).

search_opportunitiesAInspect

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.

Inputs: query, region, category, is_rolling, +5 more.

subscribe_to_digestAInspect

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. user@example.com) — 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").

Inputs: email (required), keywords (required), region.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to search and inspect around 2,500 federal, state, and EU funding programs using full-text search and filters, with detailed eligibility, deadlines, contacts, and links to the original funding pages.
      3
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Provides access to FluentLab's funding database, enabling users to search for funding opportunities and retrieve document checklists required for specific funding programme applications.
      1
      2 npm
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables monitoring Italian public funding opportunities, normalizing them into a canonical model, and ranking them against a company profile with a two-stage matcher.
      6
      2
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.