Arclan / Servers

Agent harness for GLEN apps: tool-use loop, local + MCP tool registry and MCP cl

Agent harness for GLEN apps: tool-use loop, local + MCP tool registry and MCP client in plain ES modules that run in browsers and Node

auth_gated Not production-safe Score 40/100 unknown no auth

At a glance

Endpointhttps://duckdb-mcp.carlboettiger.info/mcp
Sourcehttps://github.com/SchmidtDSE/glen-harness
Transportunknown
Tools0
Authnone
First seen2026-11-07 04:51:20
Last checked2026-11-11 04:52:19

Observed reliability

7-day uptime0%
24-hour uptime—
Handshake success0%
Latency p50 / p950 / 0 ms
Last successful check—

Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →

Validation history

CheckedReachableHandshakeLatencyScoreState
2026-11-11 04:52:19✓✗0 ms35auth_gated
2026-11-09 04:52:00✓✗0 ms35unreachable
2026-11-07 04:51:51✓✗0 ms35unreachable

Query this programmatically

Agents can pull this record live over the MCP protocol or REST:

get_server("https://duckdb-mcp.carlboettiger.info/mcp")   # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/duckdb-mcp-carlboettiger-info-mcp   # JSON