mcp server
Arclan MCP Registry
MCP server registry — validated by live handshake, scored on reliability, monitored continuously.
Description as published by the maintainer. Source
- version 0.1.0
- active
active — Registry entry last updated 2026-05-19.
What this server can do
4 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
get_server(id, url)- 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.
query_registry(limit, status, min_score, read_only, transport, capability, 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.
recommend_server(q, auth, limit, read_only, production_safe)- 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.
report_server(errors, agentId, outcome, severity, criterion, latencyMs, serverUrl, toolsUsed, environment, evidenceRef, taskCategory, turnsRequired, componentScore, taskDescription)- 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). Required: serverUrl, outcome.
Last successful function declaration observed on . Source: https://arclan.ai/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://arclan.ai/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 0.1.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-05-19 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-05-19 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 4 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | arclan.ai | |
| mcp endpoint status | ok | The server listed 4 functions when asked. | as of probe | arclan.ai |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json