Arclan MCP Registry

MCP registry: 138k servers crawled, handshake-validated, reliability-scored. 744 production-safe.

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
93%
Naming quality
90%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~1,109Tokens (tool definitions)
~2.6 KBTypical response size
Moderate attention impact (0.87% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "registry": {
      "url": "https://arclan.ai/mcp"
    }
  }
}

Remote endpoints

https://arclan.ai/mcpstreamable-http

What it can do

Tool inventory

Tools (4)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟡query_registry(capability, min_score, transport, status, production_safe, ...)

Search the Arclan registry for MCP servers. By default returns only connectable servers (active, mcp_partial, auth_gated). Use status=stdio to browse local-only servers available for installation. Use status=all to query the full index. Use production_safe=true to restrict to servers with uptime > 97% and handshake success > 95%. Use read_only=true to restrict to servers with no write or exec tools. Use this before connecting to an MCP server to check its validation status and score. After using a server, call report_server to contribute reliability data.

Input Schema

{
  "type": "object",
  "properties": {
    "capability": {
      "type": "string",
      "description": "Filter by tool name or keyword (searches name, description, tools)"
    },
    "min_score": {
      "type": "number",
      "description": "Minimum validation score 0–100 (default 0)"
    },
    "transport": {
      "type": "string",
      "enum": [
        "http",
        "sse",
        "stdio",
        "unknown"
      ],
      "description": "Filter by transport type"
    },
    "status": {
      "type": "string",
      "enum": [
        "active",
        "mcp_partial",
        "auth_gated",
        "stdio",
        "unreachable",
        "invalid",
        "zombie",
        "all"
      ],
      "description": "Filter by state. Default (omit): connectable states only (active + mcp_partial + auth_gated). Use \"stdio\" for local-install catalog. Use \"all\" for the full index."
    },
    "production_safe": {
      "type": "boolean",
      "description": "Only return servers with uptime_7d > 97% and handshake_success_rate > 95%. Use when reliability matters."
    },
    "read_only": {
      "type": "boolean",
      "description": "Only return servers with no write or exec tools — safe for read-only agent workflows."
    },
    "limit": {
      "type": "number",
      "description": "Max results to return 1–20 (default 10)"
    }
  }
}
🟢get_server(url, id)

Get full details for a specific MCP server. Pass the server name (e.g. "GitHub", "Brave Search"), registry ID slug, or endpoint URL. Returns score, state, tools list, latency, and recent test history.

Input Schema

{
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "description": "The MCP server endpoint URL (e.g. \"https://mcp.example.com/mcp\")"
    },
    "id": {
      "type": "string",
      "description": "Server name, registry ID slug, or any identifier (e.g. \"github\", \"brave-search\", \"gateway-pipeworx-io-rpc-mcp\")"
    }
  }
}
🟢recommend_server(q, auth, production_safe, read_only, limit)

Get ranked MCP server recommendations for a task. Returns servers scored by production safety, keyword relevance, registry score, latency, and freshness. Each result includes a reason code array explaining why it was ranked. Use this instead of query_registry when you want an opinionated ranked list rather than a filtered search.

Input Schema

{
  "type": "object",
  "properties": {
    "q": {
      "type": "string",
      "description": "Task or capability query — e.g. \"search the web\" or \"read files\""
    },
    "auth": {
      "type": "boolean",
      "description": "Include servers that require authentication (default: true)"
    },
    "production_safe": {
      "type": "boolean",
      "description": "Only return production-safe servers (uptime > 97%, handshake > 95%)"
    },
    "read_only": {
      "type": "boolean",
      "description": "Only return servers with no write-classified tools"
    },
    "limit": {
      "type": "number",
      "description": "Max results 1–20 (default: 5)"
    }
  }
}
🟡report_server(serverUrl, outcome, agentId, toolsUsed, turnsRequired, ...)

Submit an agent usage report for an MCP server. Reports are aggregated and influence registry trust scores. Call this after using an MCP server so the registry can track real-world reliability. Supports both a simple outcome report and a structured scoring report (criterion + component_score).

Input Schema

{
  "type": "object",
  "properties": {
    "serverUrl": {
      "type": "string",
      "description": "The MCP server endpoint URL that was used"
    },
    "outcome": {
      "type": "string",
      "enum": [
        "success",
        "failure",
        "partial"
      ],
      "description": "Result of using the server"
    },
    "agentId": {
      "type": "string",
      "description": "Identifier for the reporting agent (optional)"
    },
    "toolsUsed": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "List of tool names that were called"
    },
    "turnsRequired": {
      "type": "number",
      "description": "Number of turns to complete the task"
    },
    "latencyMs": {
      "type": "number",
      "description": "Total wall-clock latency in milliseconds"
    },
    "taskCategory": {
      "type": "string",
      "description": "Category of task attempted (e.g. \"search\", \"write\", \"read\")"
    },
    "taskDescription": {
      "type": "string",
      "description": "Brief description of what the task was"
    },
    "errors": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Array of error strings encountered during tool use"
    },
    "criterion": {
      "type": "string",
      "enum": [
        "output_reliability",
        "side_effect_transparency",
        "failure_handling",
        "rate_limits",
        "agent_feedback"
      ],
      "description": "Specific reliability criterion being scored (enables structured component scoring)"
    },
    "componentScore": {
      "type": "number",
      "description": "Score 0–100 for the specified criterion"
    },
    "severity": {
      "type": "string",
      "enum": [
        "info",
        "warning",
        "error",
        "critical"
      ],
      "description": "Severity of the worst issue encountered"
    },
    "environment": {
      "type": "string",
      "enum": [
        "prod",
        "staging",
        "dev",
        "unknown"
      ],
      "description": "Environment the server was used in"
    },
    "evidenceRef": {
      "type": "string",
      "description": "Trace ID, log URL, or other reference supporting this report"
    }
  },
  "required": [
    "serverUrl",
    "outcome"
  ]
}

Compare

Peer Comparison

Compare this server with others in the same category.

Tools:0
Tools:0
Uptime:100.0%
Latency:303ms
Tools:2

Version History

unknown → unknown
11/4/2026
Initial manifest with 4 tools
Details
Added:
  • + query_registry
  • + get_server
  • + recommend_server
  • + report_server
unknown → unknown
11/4/2026
Initial manifest with 4 tools
Details
Added:
  • + query_registry
  • + get_server
  • + recommend_server
  • + report_server
unknown → unknown
11/4/2026
Initial manifest with 4 tools
Details
Added:
  • + query_registry
  • + get_server
  • + recommend_server
  • + report_server
unknown → unknown
11/4/2026
Initial manifest with 4 tools
Details
Added:
  • + query_registry
  • + get_server
  • + recommend_server
  • + report_server
unknown → unknown
11/4/2026
Initial manifest with 4 tools
Details
Added:
  • + query_registry
  • + get_server
  • + recommend_server
  • + report_server
unknown → unknown
11/3/2026
Initial manifest with 4 tools
Details
Added:
  • + query_registry
  • + get_server
  • + recommend_server
  • + report_server
unknown → unknown
11/3/2026
Initial manifest with 4 tools
Details
Added:
  • + query_registry
  • + get_server
  • + recommend_server
  • + report_server
unknown → unknown
11/3/2026
Initial manifest with 4 tools
Details
Added:
  • + query_registry
  • + get_server
  • + recommend_server
  • + report_server
unknown → unknown
11/3/2026
Initial manifest with 4 tools
Details
Added:
  • + query_registry
  • + get_server
  • + recommend_server
  • + report_server
unknown → unknown
11/3/2026
Initial manifest with 4 tools
Details
Added:
  • + query_registry
  • + get_server
  • + recommend_server
  • + report_server

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded4 tools
verifiedversion not recorded4 tools
verifiedversion not recorded4 tools
verifiedversion not recorded4 tools
verifiedversion not recorded4 tools
verifiedversion not recorded4 tools