Skip to content

NetGrant — Canadian funding MCP server

ca.netgrant/canadian-grantsnetgrant.castreamable-httpv1.1.0Scanned

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

5 tools: 2 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 2 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the NetGrant — Canadian funding MCP server can do

The NetGrant — Canadian funding MCP server is published by netgrant.ca, a domain the MCP Registry verified. It has 5 tools. It can create or change data (2 tools: eligibility_check and subscribe_to_digest), but cannot delete data. 3 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 10, 2026, version 1.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

5 tools

Changes things 2Claude Code: ask
  • eligibility_checkPull a single opportunity's eligibility criteria alongside a description of the applicant, so you can judge whether they qualify.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • subscribe_to_digestSubscribe the user to a FREE weekly email digest of Canadian funding opportunities matching a saved search (keywords + region).No findings

    Why it is in this group

    • The name "subscribe_to_digest" says "subscribe": a word for a change.
    Description, as the server wrote it
    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").
Only reads 3Show 3 read-only tools
  • compare_opportunitiesFetch 2–4 opportunities at once so you can present them side by side.No findings

    Why it is in this group

    • The name "compare_opportunities" says "compare": a word for reading.
    Description, as the server wrote it
    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.
  • get_opportunity_detailsFetch full details for a single opportunity by ID.No findings

    Why it is in this group

    • The name "get_opportunity_details" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • search_opportunitiesSearch Canadian funding opportunities (grants, competitions, accelerators, tax credits, wage subsidies, loans, events).No findings

    Why it is in this group

    • The name "search_opportunities" says "search": a word for reading.
    Description, as the server wrote itContains invisible characters, shown as [U+…]
    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 ⚠[U+FE0F], 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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:31 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-03-26
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.netgrant.ca/mcp: tools/list returned 5 tools to an anonymous client, including eligibility_check (write), subscribe_to_digest (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.1.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__canadian-grants__search_opportunities",
      "mcp__canadian-grants__get_opportunity_details",
      "mcp__canadian-grants__compare_opportunities"
    ],
    "ask": [
      "mcp__canadian-grants__eligibility_check",
      "mcp__canadian-grants__subscribe_to_digest"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as canadian-grants. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/ca.netgrant/canadian-grants/verify?hash=a19adb166ca476e2f82946318e4e30096369e09f35c1a9517a803a56d5211683" | jq -e '.changed == false'

Pinned hash a19adb166ca4, from Nov 10, 2026, 07:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/ca.netgrant/canadian-grants/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for ca.netgrant/canadian-grants
[![Anlyon Radar](https://radar.anlyon.com/badge/ca.netgrant/canadian-grants.svg)](https://radar.anlyon.com/servers/ca.netgrant/canadian-grants)

Source: MCP Registry · repository. Synced Oct 21, 2026, 17:46 UTC.

NetGrant — Canadian funding MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the NetGrant — Canadian funding MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the NetGrant — Canadian funding MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the NetGrant — Canadian funding MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the NetGrant — Canadian funding MCP server have?

5 tools: 2 write, 3 read. eligibility_check, subscribe_to_digest, search_opportunities, get_opportunity_details and compare_opportunities.

Does the NetGrant — Canadian funding MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the NetGrant — Canadian funding MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the NetGrant — Canadian funding MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.