# Arclan MCP Registry (remote · arclan.ai)

MCP server registry — validated by live handshake, scored on reliability, monitored continuously.

- Trust score: 59/100 (low)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-04

## Components

- remote · `arclan.ai`: 59/100 (this document), [markdown](https://verifymcp.io/servers/ai-arclan-registry/arclan.md), [page](https://verifymcp.io/servers/ai-arclan-registry/arclan)

## Channel facts

- Endpoint: `https://arclan.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-04.

- **Endpoint Security**: 51/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 869 tokens (~217/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http ai-arclan-registry https://arclan.ai/mcp
```

### Codex

```toml
[mcp_servers.ai-arclan-registry]
url = "https://arclan.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-arclan-registry": {
      "type": "remote",
      "url": "https://arclan.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-arclan-registry --url https://arclan.ai/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-arclan-registry:
    url: "https://arclan.ai/mcp"
```

### Other

```json
{
  "mcpServers": {
    "ai-arclan-registry": {
      "type": "http",
      "url": "https://arclan.ai/mcp"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-04 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-02 (score 58, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 57, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 58, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 57, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 56, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 55)

First indexed and scored.

## MCP tools (4)

### `query_registry` (~297 tokens)

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 parameters:

- `capability` (string): Filter by tool name or keyword (searches name, description, tools)
- `limit` (number): Max results to return 1–20 (default 10)
- `min_score` (number): Minimum validation score 0–100 (default 0)
- `production_safe` (boolean): Only return servers with uptime_7d > 97% and handshake_success_rate > 95%. Use when reliability matters.
- `read_only` (boolean): Only return servers with no write or exec tools — safe for read-only agent workflows.
- `status` (string): 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.
- `transport` (string): Filter by transport type

### `get_server` (~123 tokens)

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 parameters:

- `id` (string): Server name, registry ID slug, or any identifier (e.g. "github", "brave-search", "gateway-pipeworx-io-rpc-mcp")
- `url` (string): The MCP server endpoint URL (e.g. "https://mcp.example.com/mcp")

### `recommend_server` (~167 tokens)

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 parameters:

- `auth` (boolean): Include servers that require authentication (default: true)
- `limit` (number): Max results 1–20 (default: 5)
- `production_safe` (boolean): Only return production-safe servers (uptime > 97%, handshake > 95%)
- `q` (string): Task or capability query — e.g. "search the web" or "read files"
- `read_only` (boolean): Only return servers with no write-classified tools

### `report_server` (~282 tokens)

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 parameters:

- `agentId` (string): Identifier for the reporting agent (optional)
- `componentScore` (number): Score 0–100 for the specified criterion
- `criterion` (string): Specific reliability criterion being scored (enables structured component scoring)
- `environment` (string): Environment the server was used in
- `errors` (array): Array of error strings encountered during tool use
- `evidenceRef` (string): Trace ID, log URL, or other reference supporting this report
- `latencyMs` (number): Total wall-clock latency in milliseconds
- `outcome` (string, required): Result of using the server
- `serverUrl` (string, required): The MCP server endpoint URL that was used
- `severity` (string): Severity of the worst issue encountered
- `taskCategory` (string): Category of task attempted (e.g. "search", "write", "read")
- `taskDescription` (string): Brief description of what the task was
- `toolsUsed` (array): List of tool names that were called
- `turnsRequired` (number): Number of turns to complete the task

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-arclan-registry/arclan#diagnostics

## Score history

- 2026-08-04: 59
- 2026-08-03: 58
- 2026-08-02: 58
- 2026-08-01: 57
- 2026-07-31: 57
- 2026-07-30: 58
- 2026-07-29: 57
- 2026-07-28: 57
- 2026-07-27: 56
- 2026-07-26: 55

## Links

- Remote endpoint: https://arclan.ai/mcp
- Changelog RSS feed: https://verifymcp.io/servers/ai-arclan-registry/arclan/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-arclan-registry/arclan/changelog.json
- HTML version of this page: https://verifymcp.io/servers/ai-arclan-registry/arclan