Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Navigi: community services across Canada

REMOTE · API.NAVIGI.CA

Community services in every Canadian community, each with the date it was last checked.

Available components

+10 this week 78 Trust /100

Last scanned (18 hours ago)

Scores higher than 76% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Health and Science

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability72
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 381 tokens (~95/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage82
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 46% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 +7
    • Authorization: unverified → partial ▲ security
    • Tool “find_services” changed its title: Find services by need and place cosmetic
    • Tool “get_community” changed its title: Community overview cosmetic
    • Tool “list_needs” changed its title: List the service categories cosmetic
    • Tool “services_near” changed its title: Find services near a location cosmetic
  • 28 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Nov 2026 · Probed https://api.navigi.ca/v1/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=navigi.ca CN=YE1,O=Let's Encrypt,C=US 27 Sept 2026 26 Dec 2026 ECDSA 256 ECDSA-SHA384 63f5e9eb039adefdde46d0fdd09bfd896b7
SANs: *.navigi.ca, navigi.ca
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.navigi.ca. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ca. present 26384 13 Verified
navigi.ca. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.navigi.ca/v1/mcp Verified 200
http (plaintext) http://api.navigi.ca/v1/mcp Served over HTTP 200
MCP tools · 4 exposed · ~341 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
find_services ~189

Find community and social services (food banks, shelters, counselling, legal aid, income help and 18 more needs) in a Canadian community on navigi.ca. Every row carries the public page URL and the date the listing's own website was last checked; cite the URL and the date.

NameTypeReqDescription
freeboolean–only services listed as free
limitinteger––
needstringyeswhat the person needs, in plain words: food bank, shelter, counselling, legal aid, income assistance, or a category slug
no_referralboolean–only services that take people without a referral
placestringyescommunity name, for example Truro
provincestringyestwo-letter province or territory code (ab, bc, on, qc, ns, nb, mb, sk, pe, nl, yt, nt, nu)

No output schema declared.

No examples provided.

get_community ~42

One community's listing counts by category and its page URL on navigi.ca.

NameTypeReqDescription
communitystringyesslug or name
provincestringyes–

No output schema declared.

No examples provided.

list_needs ~37

The service categories navigi.ca uses, with the searcher terms each one answers. Call this first when unsure which need word to use.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

services_near ~73

Community and social services within a radius of a point, optionally for one need. Use when the person gives a location rather than a community name.

NameTypeReqDescription
kmnumber––
latnumberyes–
limitinteger––
lngnumberyes–
needstring––

No output schema declared.

No examples provided.

Install

How do I install the Navigi: community services across Canada MCP server?

Navigi: community services across Canada is a hosted endpoint at https://api.navigi.ca/v1/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.navigi.ca

# add to Claude Code
claude mcp add --transport http ca-navigi-navigi 'https://api.navigi.ca/v1/mcp'
Common questions

What is the Navigi: community services across Canada MCP server?

Navigi: community services across Canada is an MCP server listed in the public MCP registry as ca.navigi/navigi. Community services in every Canadian community, each with the date it was last checked. This page covers its hosted endpoint (https://api.navigi.ca/v1/mcp).

Is the Navigi: community services across Canada MCP server safe to use?

Navigi: community services across Canada scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Navigi: community services across Canada MCP server expose?

Navigi: community services across Canada exposes 4 tools: find_services, services_near, get_community, list_needs. Their descriptions and schemas cost roughly 341 tokens of context every time the server is loaded.

Does the Navigi: community services across Canada MCP server require authentication?

No. We connected to Navigi: community services across Canada without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Navigi: community services across Canada MCP server still maintained?

Navigi: community services across Canada is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.