Koskamo

NetGrant MCP

An MCP server providing read-only access to a database of over 1,300 Canadian funding opportunities, including grants, tax credits, accelerators, and loans. It allows agents to search for opportunities and retrieve detailed information about specific funding programs.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

NetGrant MCP logo, by NetGrantVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-07Operated by NetGrant
MCP endpoint (Streamable HTTP)
https://mcp.netgrant.ca/mcp
Vendor documentation

What its tools do

5 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

5 of 5 have a description · 0 of 5 declare behavior hints · 5 of 5 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to netgrant.ca ·
  • Passed Endpoint is on the registry namespace domain ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Search for Canadian grants and tax credits
  • Retrieve details for specific funding opportunities
  • Identify accelerators and loans for businesses

Source and maintenance

Vendor evidenceRegistry 1.1.0
Maintenance checked

Protocol and capabilities

Server
netgrant 1.0.0
MCP protocol negotiated in check
2025-03-26
Tools
5 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
2 advertised
Server-advertised capabilities
{
  "tools": {},
  "prompts": {}
}

Tools

5 advertised

search_opportunities
Advertised by the server during the last successful anonymous check.

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.

search_opportunities input schema
{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Free-text search across title and body. Pass the user's actual keywords (e.g. \"AI\", \"agriculture\", \"women-led\")."
    },
    "region": {
      "type": "string",
      "description": "Optional province code: ON, BC, QC, AB, MB, SK, NS, NB, NL, PE, YT, NT, NU. Use Federal for nation-wide programs."
    },
    "category": {
      "type": "string",
      "description": "Optional: grant, competition, tax_credit, wage_subsidy, loan, event, workshop, conference, other"
    },
    "is_rolling": {
      "type": "boolean",
      "description": "Optional. true = only rolling/no-fixed-deadline opportunities; false = only those with a fixed deadline. Omit to include both."
    },
    "max_funding": {
      "type": "integer",
      "minimum": 0,
      "description": "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": {
      "type": "integer",
      "default": 20,
      "maximum": 50,
      "minimum": 1,
      "description": "Default 20. Increase only if the user wants a comprehensive sweep."
    },
    "min_funding": {
      "type": "integer",
      "minimum": 0,
      "description": "Optional. Only return opportunities with max_funding_amount >= this value (in CAD). Use when the user specifies a minimum funding threshold."
    },
    "exclude_expired": {
      "type": "boolean",
      "default": true,
      "description": "Default true. Set false only if the user explicitly wants to see past-deadline or historical opportunities."
    },
    "deadline_within_days": {
      "type": "integer",
      "maximum": 365,
      "minimum": 1,
      "description": "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."
    }
  }
}
get_opportunity_details
Advertised by the server during the last successful anonymous check.

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.

get_opportunity_details input schema
{
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Opportunity UUID returned from search_opportunities"
    }
  }
}
compare_opportunities
Advertised by the server during the last successful anonymous check.

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.

compare_opportunities input schema
{
  "type": "object",
  "required": [
    "ids"
  ],
  "properties": {
    "ids": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 4,
      "minItems": 2,
      "description": "Array of 2–4 opportunity UUIDs (from search_opportunities) to compare."
    }
  }
}
eligibility_check
Advertised by the server during the last successful anonymous 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.

eligibility_check input schema
{
  "type": "object",
  "required": [
    "id",
    "applicant_description"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Opportunity UUID to check eligibility for."
    },
    "applicant_description": {
      "type": "string",
      "description": "The applicant's details: sector, stage, location/province, incorporation status, size, demographics — whatever is relevant to eligibility."
    }
  }
}
subscribe_to_digest
Advertised by the server during the last successful anonymous check.

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").

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

Prompts

2 advertised

find-for-me

Advertised by the server during the last successful anonymous check.

Find Canadian funding opportunities matched to your business

business_description
One sentence about your business (sector, stage, location) (required)
check-deadlines

Advertised by the server during the last successful anonymous check.

Show Canadian funding opportunities closing in the next 30 days

category
Optional category filter (grant, competition, etc.)

Resources

Not advertised

No resource definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
868 ms
95th percentile latency
868 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 868 ms · metadata changed · 5 tool(s), 2 prompt(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http netgrant-mcp https://mcp.netgrant.ca/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add netgrant-mcp --url https://mcp.netgrant.ca/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable netgrant-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "netgrant-mcp": {
      "url": "https://mcp.netgrant.ca/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "netgrant-mcp": {
      "type": "streamableHttp",
      "url": "https://mcp.netgrant.ca/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start netgrant-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "netgrant-mcp": {
      "type": "http",
      "url": "https://mcp.netgrant.ca/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http netgrant-mcp https://mcp.netgrant.ca/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://mcp.netgrant.ca/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "netgrant-mcp": {
      "serverUrl": "https://mcp.netgrant.ca/mcp"
    }
  }
}

Let your agent find its tools

Find servers like NetGrant MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Do you run NetGrant MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing