Shadow AI List
REMOTE · AILIST.AIRISKMANAGEMENT.CA · SCANNED SEP 20
Risk-ranked registry of AI tools: look up an AI tool's risk or check if a domain is shadow AI.
Available components
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 382 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
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
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'
{
"mcpServers": {
"ca-airiskmanagement-shadow-ai-list": {
"url": "https://ailist.airiskmanagement.ca/mcp"
}
}
} {
"servers": {
"ca-airiskmanagement-shadow-ai-list": {
"type": "http",
"url": "https://ailist.airiskmanagement.ca/mcp"
}
}
} [mcp_servers.ca-airiskmanagement-shadow-ai-list] url = "https://ailist.airiskmanagement.ca/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ca-airiskmanagement-shadow-ai-list": {
"type": "remote",
"url": "https://ailist.airiskmanagement.ca/mcp",
"enabled": true
}
}
} openclaw mcp add ca-airiskmanagement-shadow-ai-list --url 'https://ailist.airiskmanagement.ca/mcp' --transport streamable-http
mcp_servers:
ca-airiskmanagement-shadow-ai-list:
url: "https://ailist.airiskmanagement.ca/mcp" {
"McpServers": {
"ca-airiskmanagement-shadow-ai-list": {
"Transport": "http",
"Url": "https://ailist.airiskmanagement.ca/mcp"
}
}
} assistant mcp add ca-airiskmanagement-shadow-ai-list -t streamable-http -u 'https://ailist.airiskmanagement.ca/mcp'
{
"mcpServers": {
"ca-airiskmanagement-shadow-ai-list": {
"type": "http",
"url": "https://ailist.airiskmanagement.ca/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 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 +1
- Stability: 0.97 → pass security
- 23 Aug 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.
- 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
- 27 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
- 26 Jul 26 0
First indexed and scored.
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 20 Sept 2026 · Probed https://ailist.airiskmanagement.ca/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ailist.airiskmanagement.ca | CN=YR1,O=Let's Encrypt,C=US | 19 Aug 2026 | 17 Nov 2026 | RSA 2048 | SHA256-RSA | 643ee356835ffc9980869c680fd2a916f86 |
| SANs: ailist.airiskmanagement.ca | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
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 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://js.stripe.com https://snap.licdn.com; worker-src 'self' blob:; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com data:; img-src 'self' data: https: blob:; connect-src 'self' https://api.stripe.com https://px.ads.linkedin.com https://*.ads.linkedin.com https://snap.licdn.com; frame-src 'self' https://js.stripe.com https://hooks.stripe.com; frame-ancestors 'none'; base-uri 'self'; form-action 'self' https://checkout.stripe.com |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), interest-cohort=() |
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 | Verified | 200 | |
| http (plaintext) | http://ailist.airiskmanagement.ca/mcp | HTTPS enforced | 301 | https://ailist.airiskmanagement.ca/mcp |
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.
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 82 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?
No. We connected to Shadow AI List without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Shadow AI List MCP server still maintained?
Shadow AI List is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.