NetGrant — Canadian funding

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

사용해야 할까요

품질 및 안전성

A
설명 품질
96%
스키마 완전성
98%
이름 품질
92%
오염 위험
60%
권한 일치
100%
프로토콜 준수
100%

발견 사항 (4)

  • HIGHTool poisoning patterns detected
  • MEDIUMTool 'subscribe_to_digest' description contains placeholder textsubscribe_to_digest에서
  • LOWTool description contains negative instruction about its own usesubscribe_to_digest에서
  • INFOTool description contains placeholder or incomplete textsubscribe_to_digest에서

도구 정의와 프로토콜 준수에 대한 자동 분석을 기반으로 합니다.

컨텍스트 비용

~1,896토큰 (도구 정의)
~1.7 KB일반적인 응답 크기
중간 정도의 주의 영향 (128k 컨텍스트의 1.48%)

이는 서버의 도구가 모델의 컨텍스트에 로드될 때마다 소비되는 대략적인 토큰 수입니다. 수치가 높을수록 다른 작업에 사용할 수 있는 주의가 줄어듭니다.

설치

원클릭 설치

`claude_desktop_config.json` 파일에 다음을 추가하세요:

{
  "mcpServers": {
    "canadian-grants": {
      "url": "https://mcp.netgrant.ca/mcp"
    }
  }
}

원격 엔드포인트

https://mcp.netgrant.ca/mcpstreamable-http

할 수 있는 일

도구 목록

도구 (5)

🟢 읽기 전용🟡 쓰기🔴 삭제⚪ 알 수 없음
🟡search_opportunities(query, region, category, max_results, exclude_expired, ...)

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.

입력 스키마

{
  "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"
    },
    "max_results": {
      "type": "integer",
      "minimum": 1,
      "maximum": 50,
      "default": 20,
      "description": "Default 20. Increase only if the user wants a comprehensive sweep."
    },
    "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",
      "minimum": 1,
      "maximum": 365,
      "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."
    },
    "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."
    },
    "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."
    },
    "is_rolling": {
      "type": "boolean",
      "description": "Optional. true = only rolling/no-fixed-deadline opportunities; false = only those with a fixed deadline. Omit to include both."
    }
  }
}
🟢get_opportunity_details(id)

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.

입력 스키마

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "Opportunity UUID returned from search_opportunities"
    }
  },
  "required": [
    "id"
  ]
}
🟢compare_opportunities(ids)

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.

입력 스키마

{
  "type": "object",
  "properties": {
    "ids": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "minItems": 2,
      "maxItems": 4,
      "description": "Array of 2–4 opportunity UUIDs (from search_opportunities) to compare."
    }
  },
  "required": [
    "ids"
  ]
}
🔴eligibility_check(id, applicant_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?". 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.

입력 스키마

{
  "type": "object",
  "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."
    }
  },
  "required": [
    "id",
    "applicant_description"
  ]
}
🟡subscribe_to_digest(email, keywords, region)

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

입력 스키마

{
  "type": "object",
  "properties": {
    "email": {
      "type": "string",
      "description": "The user's email address. Ask for it explicitly; never invent or assume it."
    },
    "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."
    },
    "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."
    }
  },
  "required": [
    "email",
    "keywords"
  ]
}

권장 프롬프트

fetch_info
Fetch [information type] using NetGrant — Canadian funding
예상 도구: get_opportunity_details
search_research
Search for information about [topic] using NetGrant — Canadian funding
예상 도구: search_opportunities
find_specific
Find [specific item] using NetGrant — Canadian funding
예상 도구: search_opportunities
research_workflow
Search for [topic], then get detailed information about the top results using NetGrant — Canadian funding
예상 도구: search_opportunitiesget_opportunity_details
retrieve_data
Get details about [item] from NetGrant — Canadian funding
예상 도구: get_opportunity_details

커뮤니티

이 서버 평가하기

증거

최근 관측

검증됨버전이 기록되지 않음도구 5개
검증됨버전이 기록되지 않음도구 5개