mcp-registry/ca.netgrant/canadian-grants · v1.0.0
As of 2026-10-26 16:39 UTC, the Netgrant Canadian Grants MCP server is up with a Glimind reliability score of 88/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 4 minutes.
Search 1,300+ live Canadian funding opportunities — grants, tax credits, accelerators, and loans.
Point your MCP client at this streamable-http endpoint: https://mcp.netgrant.ca/mcp
5 of 5 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Negotiates MCP 2025-03-26. Structured output, tool output schemas and elicitation arrived in 2025-06-18.
Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fca.netgrant%2Fcanadian-grants/fixes
{
"name": "compare_opportunities",
"description": "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.\n\nReturns 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.",
"inputSchema": {
"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."
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "eligibility_check",
"description": "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?\".\n\nThe 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 ",
"inputSchema": {
"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."
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_opportunity_details",
"description": "Fetch full details for a single opportunity by ID. Use this after search_opportunities when:\n- The user wants to know more about a specific match\n- You need the full eligibility text to confirm a strong-match claim\n- The user wants to draft an application — you need the requirements\n\nThe response includes all fields including the full body text and eligibility criteria. Present the eligibility as a checklist when relevant.",
"inputSchema": {
"type": "object",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"description": "Opportunity UUID returned from search_opportunities"
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/ca.netgrant/canadian-grants"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/ca.netgrant/canadian-grants"}) over MCP.
search_opportunities ~643 tokenssubscribe_to_digest ~304 tokenseligibility_check ~256 tokenscompare_opportunities ~199 tokensget_opportunity_details ~178 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fca.netgrant%2Fcanadian-grants?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fca.netgrant%2Fcanadian-grants?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fca.netgrant%2Fcanadian-grants.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fca.netgrant%2Fcanadian-grants.svg :target: https://glimind.com/server/mcp-registry%2Fca.netgrant%2Fcanadian-grants?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:547b87649ca26550…, first seen 2026-10-17, included at leaf 64 of 74,153. Version history · verify what your client received.
Compare: most reliable data servers · most reliable search servers · most reliable email servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 16:39 UTC, the Netgrant Canadian Grants MCP server is up with a Glimind reliability score of 88/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 4 minutes.
Netgrant Canadian Grants MCP server advertises 5 tools, including compare_opportunities, eligibility_check, get_opportunity_details, search_opportunities, subscribe_to_digest.
Point your MCP client at this streamable-http endpoint: https://mcp.netgrant.ca/mcp
Glimind scanned all 5 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.