Shua Labs · Registry
The catalogue, and the
checks that keep it true.
Most AI setups are a folder of prompts nobody has looked at in months. This is the same thing with a manifest, a validator, and a health check — so when it breaks, something says so.
- agents
- 8agents
- MCP servers
- 5MCP servers
- harness tools
- 5harness tools
- public
- 6public
The problem this exists for
AI dev configuration rots silently. Model IDs go stale. MCP servers die. Environment variables get referenced but never exported. None of it raises an error you would notice — you find out weeks later, if ever. A single audit of this machine turned up 24 definitions pinned to a dead model generation, a server that had been down for weeks, two editors wired to a variable nobody had ever set, and a live credential in plaintext.
Projects
1Built to learn the stack, not to demo it. Each claim below is backed by a command that actually ran — captured while building, not written up afterwards.
Agents
8Specialists that do the work. Each declares its tools, model tier, and who it hands off to. Three hold no write tools at all.
MCP Servers
5What the agents can actually reach. Without one, a model cannot touch that system at all.
Harness Tools
5Never in the path when work happens. They exist only to notice when everything above breaks.
Agent entries on this page are generated from the registry file on the machine that runs them, and CI fails if the two fall out of step. The site cannot claim something the registry no longer says.