Shadow AI List
REMOTE · AILIST.AIRISKMANAGEMENT.CA
Risk-ranked registry of AI tools: look up an AI tool's risk or check if a domain is shadow AI.
Available components
Last scanned (23 hours ago)
Scores higher than 97% of remote servers
Unreachable for 1 day in a row. Last reached 3 Nov 2026.
Category Security
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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://ailist.airiskmanagement.ca/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ailist.airiskmanagement.ca. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ca. | present | 26384 | 13 | Verified |
| airiskmanagement.ca. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ailist.airiskmanagement.ca/mcp | Unreachable | ||
| http (plaintext) | http://ailist.airiskmanagement.ca/mcp | HTTPS enforced |
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 →
check_domain_against_registry Check if a domain is shadow AI ~79
Check whether a domain or subdomain belongs to a known AI tool - i.e. whether traffic to it is shadow AI. Returns the tool and its risk if matched. Covers the free top 100.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | A domain or URL, e.g. 'chat.openai.com' or 'https://cursor.sh'. |
No output schema declared.
No examples provided.
get_top_risky_ai Get the highest-risk AI tools ~61
Get the highest-risk AI tools by AI Exposure Index risk score. Returns name, domain, category, and risk score + band. Covers the free top 100.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many (default 10, max 25). |
No output schema declared.
No examples provided.
list_shadow_ai List AI tools ~81
List AI tools from the registry, optionally filtered by category. Returns name, domain, category, and risk band. Covers the free top 100.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional category filter (e.g. 'coding', 'chatbot', 'meeting_transcription'). |
| limit | integer | – | Max results (default 25, max 100). |
No output schema declared.
No examples provided.
lookup_ai_tool_risk Look up an AI tool's risk ~80
Look up an AI tool by name, vendor, or domain and return its AI Exposure Index risk score, risk band, category, and whether it trains on user data. Covers the free top 100.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Tool name, vendor, or domain (e.g. 'Cursor', 'OpenAI', 'cursor.sh'). |
No output schema declared.
No examples provided.
How do I install the Shadow AI List MCP server?
Shadow AI List is a hosted endpoint at https://ailist.airiskmanagement.ca/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 · ailist.airiskmanagement.ca
claude mcp add --transport http ca-airiskmanagement-shadow-ai-list 'https://ailist.airiskmanagement.ca/mcp'
What is the Shadow AI List MCP server?
Shadow AI List is an MCP server listed in the public MCP registry as ca.airiskmanagement/shadow-ai-list. Risk-ranked registry of AI tools: look up an AI tool's risk or check if a domain is shadow AI. This page covers its hosted endpoint (https://ailist.airiskmanagement.ca/mcp).
Is the Shadow AI List MCP server safe to use?
Shadow AI List scores 89 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 Shadow AI List MCP server expose?
Shadow AI List exposes 4 tools: lookup_ai_tool_risk, check_domain_against_registry, list_shadow_ai, get_top_risky_ai. Their descriptions and schemas cost roughly 301 tokens of context every time the server is loaded.
Does the Shadow AI List MCP server require authentication?
Its publisher declares no required credentials for Shadow AI List. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Shadow AI List MCP server still maintained?
Shadow AI List is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 3 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.