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.

ai.shawndurrani/mcp-registry

REMOTE · MCP-REGISTRY.SHAWNDURRANI.AI · SCANNED SEP 28

Search the public MCP Registry; discover servers and copy SSE URLs.

0 this week 70 Trust /100
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 & Reachability40
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 199 tokens (~49/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 Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
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 4 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
Install

How do I install the ai.shawndurrani/mcp-registry server?

ai.shawndurrani/mcp-registry is a hosted endpoint at https://mcp-registry.shawndurrani.ai/sse, 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 · mcp-registry.shawndurrani.ai

# add to Claude Code
claude mcp add --transport http ai-shawndurrani-mcp-registry 'https://mcp-registry.shawndurrani.ai/sse'
// .cursor/mcp.json
{
  "mcpServers": {
    "ai-shawndurrani-mcp-registry": {
      "url": "https://mcp-registry.shawndurrani.ai/sse"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "ai-shawndurrani-mcp-registry": {
      "type": "http",
      "url": "https://mcp-registry.shawndurrani.ai/sse"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.ai-shawndurrani-mcp-registry]
url = "https://mcp-registry.shawndurrani.ai/sse"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-shawndurrani-mcp-registry": {
      "type": "remote",
      "url": "https://mcp-registry.shawndurrani.ai/sse",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ai-shawndurrani-mcp-registry --url 'https://mcp-registry.shawndurrani.ai/sse' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  ai-shawndurrani-mcp-registry:
    url: "https://mcp-registry.shawndurrani.ai/sse"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "ai-shawndurrani-mcp-registry": {
      "Transport": "http",
      "Url": "https://mcp-registry.shawndurrani.ai/sse"
    }
  }
}
# add to Vellum
assistant mcp add ai-shawndurrani-mcp-registry -t streamable-http -u 'https://mcp-registry.shawndurrani.ai/sse'
// mcp.json
{
  "mcpServers": {
    "ai-shawndurrani-mcp-registry": {
      "type": "http",
      "url": "https://mcp-registry.shawndurrani.ai/sse"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 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
  • 1 Sept 26 +37
    • Injection markers: unverified → pass ▲ security
    • Stability: fail → pass ▲ security
    • Authorization: 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. security
    • Schema quality: unverified → fail ▼ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Schema quality: unverified → pass ▲ functional
    • Schema quality: unverified → good ▲ functional
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 31 Aug 26 −37
    • Tool safety: pass → unverified ▼ security
    • Stability: pass → fail ▼ security
    • Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
    • Schema quality: fail → unverified ▼ functional
    • Schema quality: good → unverified ▼ functional
    • Schema quality: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • This server's schema is too large to store in full, so we cannot compare its tools day to day 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
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 28 Sept 2026 · Probed https://mcp-registry.shawndurrani.ai/sse

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp-registry.shawndurrani.ai CN=YR2,O=Let's Encrypt,C=US 9 Sept 2026 8 Dec 2026 RSA 2048 SHA256-RSA 6ca68a37d784ef0da61991a7a2043db7217
SANs: mcp-registry.shawndurrani.ai
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
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 mcp-registry.shawndurrani.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 3799 8 Verified
shawndurrani.ai. 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=15552000; includeSubDomains
content-security-policy default-src 'self';base-uri 'self';font-src 'self' https: data:;form-action 'self';frame-ancestors 'self';img-src 'self' data:;object-src 'none';script-src 'self';script-src-attr 'none';style-src 'self' https: 'unsafe-inline'
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy no-referrer

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

Transports 2 probes
Transport URL Outcome Status Location
sse https://mcp-registry.shawndurrani.ai/sse Verified 200
http (plaintext) http://mcp-registry.shawndurrani.ai/sse HTTPS enforced 301 https://mcp-registry.shawndurrani.ai/sse
MCP tools · 4 exposed · ~199 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
health ~14

Returns server health and registry source

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

makeClientConfig ~49

Generate a minimal client config snippet for ChatGPT/Claude (SSE).

NameTypeReqDescription
clientstring––
nameOrIdstring––
sseUrlstring––

No output schema declared.

No examples provided.

probeSse ~39

Check if an SSE URL responds with text/event-stream within a short timeout.

NameTypeReqDescription
timeoutMsinteger––
urlstringyes–

No output schema declared.

No examples provided.

searchServers ~97

Search the public MCP Registry with safe pagination. Defaults to SSE-only results; set requireSse=false to include non-SSE remotes.

NameTypeReqDescription
activeOnlyboolean––
cursorstring––
limitinteger––
maxPagesinteger––
pageinteger––
pageSizeinteger––
querystring––
requireSseboolean––

No output schema declared.

No examples provided.

Common questions

What is the ai.shawndurrani/mcp-registry server?

ai.shawndurrani/mcp-registry is listed in the public MCP registry as ai.shawndurrani/mcp-registry. Search the public MCP Registry; discover servers and copy SSE URLs. This page covers its hosted endpoint (https://mcp-registry.shawndurrani.ai/sse).

Is the ai.shawndurrani/mcp-registry server safe to use?

ai.shawndurrani/mcp-registry scores 70 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 ai.shawndurrani/mcp-registry server expose?

ai.shawndurrani/mcp-registry exposes 4 tools: health, searchServers, probeSse, makeClientConfig. Their descriptions and schemas cost roughly 199 tokens of context every time the server is loaded.

Does the ai.shawndurrani/mcp-registry server require authentication?

No. We connected to ai.shawndurrani/mcp-registry without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the ai.shawndurrani/mcp-registry server still maintained?

ai.shawndurrani/mcp-registry is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.