_ registry / mcp streamable-http · checked 1h ago

shadow-ai-list

https://ailist.airiskmanagement.ca

Registry code: ab345ec3262f4fee

api record

Shadow AI List is a maintained, risk-ranked registry of AI tools (the 'AI Exposure Index'). Use these tools to look up an AI tool's data-exposure risk, check whether a domain is a known AI tool (i.e. shadow AI on a network), browse tools by category, or get the highest-risk AI tools. Coverage is the free top 100 of the registry.

endpoint
https://ailist.airiskmanagement.ca/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is shadow-ai-list live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is shadow-ai-list free to use?
Yes — the hub reached it with no key and no payment.
What tools does shadow-ai-list have?
4 tools: check_domain_against_registry, lookup_ai_tool_risk, list_shadow_ai, get_top_risky_ai.
Is shadow-ai-list safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.3%

90 days 98.8%· all time 98.8%

latency
155ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 509 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
security & compliance threat & vulnerability
used for
  • look up an ai tool's data exposure risk
  • check if a domain is a known ai tool
  • list riskiest ai tools
takes → gives
text → data
tools
4 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
1

through this hub

calls served
1

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
2 open 2 never probed 2 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_shadow_ai reads open 21h ago

    List AI tools from the registry, optionally filtered by category. Returns name, domain, category, and risk band. Covers the free top 100.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "description": "Max results (default 25, max 100)."
    },
    "category": {
      "type": "string",
      "description": "Optional category filter (e.g. 'coding', 'chatbot', 'meeting_transcription')."
    }
  }
}
    arguments 13 lines
  • get_top_risky_ai reads open 21h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "description": "How many (default 10, max 25)."
    }
  }
}
    arguments 9 lines
  • check_domain_against_registry reads unknown 14h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "description": "A domain or URL, e.g. 'chat.openai.com' or 'https://cursor.sh'."
    }
  }
}
    arguments 12 lines
  • lookup_ai_tool_risk reads unknown 21h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "description": "Tool name, vendor, or domain (e.g. 'Cursor', 'OpenAI', 'cursor.sh')."
    }
  }
}
    arguments 12 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id ab345ec3262f4fee.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/ab345ec3262f4fee/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/ab345ec3262f4fee/badge.svg)](https://brick.blue/agent/ab345ec3262f4fee?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
1
ok
1
failed
0
success rate
100%
median latency
361ms
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

1 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.