Atlas entry
mcp.netgrant.ca
7 capabilities over MCP. First atlas observation.
Surfaces
5 protocols checked
| ARD | Not found | No document retrieved |
|---|---|---|
| A2A | Not found | 0 skills |
| MCP | Valid | 2025-03-26 · 5 tools · resources not advertised · 2 prompts |
| OpenAPI | Not detected | 0 operations |
| WebMCP | Not detected | 0 declarative form tools · experimental |
Exact states and meaning
- ARDabsent
Exact state: not found · No document retrieved
The supported discovery location returned no matching document.
Not found does not prove the service exposes no such interface elsewhere.
Not observed / not fetched
- A2Aabsent
Exact state: not found · 0 skills
The supported discovery location returned no matching document.
Not found does not prove the service exposes no such interface elsewhere.
Not observed / not fetched
- MCPobserved
Exact state: valid · Revision 2025-03-26 · 5 tools · resources not advertised · 2 prompts
A usable protocol document was retrieved and validated.
Directly observed
- OpenAPIabsent
Exact state: not detected · 0 operations
No endpoint was established from the evidence and scope that InterfaceDelta inspected.
Not detected does not prove that no endpoint exists.
Not observed / not fetched
- WebMCPabsent
Exact state: not detected · 0 declarative form tools · experimental
No named declarative WebMCP form tools were observed in the origin root HTML.
Script-registered tools and other pages are not observed, so this does not mean the site has no WebMCP tools.
Not observed / not fetched
Capabilities
7 · inventory complete
Summary of the AI readings · beta
The service lists 5 capabilities, and 4 have AI readings.
4 capabilities are read as read-only, including search_opportunities, compare_opportunities and get_opportunity_details.
Rows named: search_opportunities · compare_opportunities · get_opportunity_details
Written by code from the AI readings on this page: it groups them and says nothing they do not.
The atlas shows each capability by its plain identifier, inputs and declared sign-in. Publisher descriptions, paths, links and source evidence are not published here.
MCP tools 5
compare_opportunitiesinputs
ids(required)AI Reads only 0.88
eligibility_checkinputs
applicant_description(required),id(required)AI Reads only 0.84
get_opportunity_detailsinputs
id(required)AI Reads only 0.89
search_opportunitiesinputs
category,deadline_within_days,exclude_expired,is_rollingand 5 moreAI Reads only 0.80
subscribe_to_digestinputs
email(required),keywords(required),region
MCP prompts 2
check-deadlinesfind-for-me
Not observed in this Passport: A2A skills, MCP resources, OpenAPI operations.
Declared and observed
No tools declare hints.
A disagreement is not a finding about the service: either side can be wrong. How we compare declarations and readings.
Atlas history
1 observation
- 7 capabilities · MCP 2025-03-26 · MCP endpoint validFirst observation
Fingerprint and versions
- Fingerprint
8f7a1db9b5677fa7e2a9d155eac090dec9e942e3eae7b6e18e09b5252001c63b- Passport schema
- 0.5.0, passport-semantic-v4
- Consistency
- MCP_PROMPTS_ADVERTISEMENT_LIST: match · MCP_RESOURCES_ADVERTISEMENT_LIST: not applicable · MCP_TOOLS_ADVERTISEMENT_LIST: match · OPENAPI_MCP_EXPLICIT_MAPPING: not applicable
Each class compares an observation with the previous atlas observation. Runs of unchanged observations are grouped. Struck values are what the previous observation recorded; inserted values are what this one recorded.
About this entry
ca.netgrant/canadian-grantsListedOfficial MCP Registry · first listed 15 Sep 2026 · last listed 30 Oct 2026
Passive observations of a public interface listed in the Official MCP Registry. An observation does not verify security, ownership or compliance, and InterfaceDelta assigns no scores or rankings. Methodology · Report an inaccuracy · Ask for removal
Identity and snapshot
- Target key
sha256:891c6c43d74b205d84d100c26cdb00077c1a6028b43d39a9168660bc2b883b23- Locator SHA-256
d4d0cc19b04de4f55e52fca2e7410308759c3cc4e3613b7eeb578372994e2a81- Snapshot generated
- 4 Nov 2026, 00:59 UTC
The entry is one exact observed target, not a real-world service identity, and implies no ownership. Endpoint paths are not published; the locator hash lets an operator confirm their own URL.

