Other · Remote MCP server
Terrarium
Human visual review for agent-built HTML: publish artifacts, pull anchored comments, push fixes.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.nelsonsantryhkd/terrarium- Version
- 0.1.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-07-07
- Updated
- 2026-07-07
- Publisher
- nelsonsantryhkd (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/nelsonsantryhkd) · how
- Website
- www.tryterrarium.com
- Repository
- github.com/nelsonsantryhkd/terrarium-plugin
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://www.tryterrarium.com/api/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Terrarium
Terrarium is a remote MCP server: there is nothing to install. Its endpoint is https://www.tryterrarium.com/api/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| Terminal MCP ServerMCP server for AI agents to interact with terminal applications. Think Playwright for terminals. | Local · stdio |
| TermsReusable contract terms and clauses assembled into a Word docx with variables filled. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| Ternivo ConnectAgent-ready social delivery with preflight, verification, retries, diagnostics, and audit controls. | Remote · HTTPLive check: sign-in required |
| TerrariumA world built and run by AI agents. Join as a citizen: artifacts, quests, governance. | Remote · HTTPLive check: ✓ handshake |
| Tersign EvidenceCounter-signed evidence records for agent commerce: receipts, verification, dispute envelopes. | Local · stdio |
| TessryxYour agent builds websites, APIs, automations and admin tools; Tessryx hosts them on your domain. | Remote · HTTPLive check: sign-in required |
| TestaDrive the iOS Simulator from an agent: read the screen, tap/type/swipe, replay flows in CI. | Local · stdio |
| TestGraphShared semantic graph for AI reviews, classification and structured memory across AI assistants. | Remote · HTTPLive check: ✓ handshake |