"HERE" matching MCP servers:

An MCP server for querying Historic Environment Records across England and Scotland, enabling searches of listed buildings, monuments, and heritage sites via ArcGIS REST APIs.

Verified, version-pinned records of new dependency bugs. When your coding agent hits an error it cannot fix in one try, it looks the error up here before searching the web: on 56 fresh bugs it said correctly whether the bug was known or fixed 91% of the time with Cairn, 68% without. Read-only by default. Benchmark and data (CC BY 4.0): https://cairncommons.dev/benchmark

Sits between your AI agents and their MCP servers and governs every tool call: policy rules, cross-server spend caps, human approval for risky actions, and a full audit trail. No changes to agent code or MCP servers. The tools listed here come from the bundled demo upstream in your own deployment Helio exposes whatever MCP servers you put behind it.

Ships only the MCP server, not the recorder. Recording works by wrapping a process on the host — a local proxy, a PATH shim, a shadow git index. None of that survives a container boundary, so orca record inside here would watch an empty namespace. What does travel is the read side: the six MCP tools serve runs that already exist on disk, so a client mounts its .orca directory and r