Arclan MCP Registry
REMOTE · ARCLAN.AI · SCANNED AUG 3
MCP server registry — validated by live handshake, scored on reliability, monitored continuously.
Available components
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 →
Endpoint Security51
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · arclan.ai
claude mcp add --transport http ai-arclan-registry https://arclan.ai/mcp
[mcp_servers.ai-arclan-registry] url = "https://arclan.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-arclan-registry": {
"type": "remote",
"url": "https://arclan.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-arclan-registry --url https://arclan.ai/mcp --transport streamable-http
mcp_servers:
ai-arclan-registry:
url: "https://arclan.ai/mcp" {
"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.
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.
- 2 Aug 26 +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.
- 31 Jul 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +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.
- 28 Jul 26 +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.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 55
First indexed and scored.
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 3 Aug 2026 · Probed https://arclan.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.arclan.ai | CN=YR2,O=Let's Encrypt,C=US | 12 Jul 2026 | 10 Oct 2026 | RSA 2048 | SHA256-RSA | 580836a8763c6d002d511fea328714bbad1 |
| SANs: arclan.ai, www.arclan.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 |
DNSSEC insecure
Validation of arclan.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| arclan.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=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | sameorigin |
| referrer-policy | same-origin |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://arclan.ai/mcp | Verified | 200 | |
| http (plaintext) | http://arclan.ai/mcp | Inconclusive | 404 |
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.
get_server ~123
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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") |
No output schema declared.
No examples provided.
query_registry ~297
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
recommend_server ~167
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
report_server ~282
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Result of using the server |
| serverUrl | string | yes | 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 |
No output schema declared.
No examples provided.