Other · Remote MCP server
Honcho
Memory that reasons: continual learning for stateful agents. Better context, fewer tokens.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.plastic-labs/honcho- Version
- 3.0.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-08-12
- Updated
- 2026-08-12
- Publisher
- plastic-labs (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/plastic-labs) · how
- Repository
- github.com/plastic-labs/honcho
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.honcho.dev | Authorization (required, secret), X-Honcho-Workspace-ID |
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 Honcho
Honcho is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.honcho.dev, 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 HTTP headers for the connection: Authorization (required, secret) and X-Honcho-Workspace-ID. A secret header usually carries an API key or token issued by the service; clients that accept custom headers set them 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 |
|---|---|
| Homebrew MCPHomebrew formula details from the official API. No key required. | Local · stdio |
| HomeMasterHome cleaning and aircon servicing in Singapore: coverage, open times, exact prices and booking. | Remote · HTTPLive check: ✓ handshake |
| Homestead MemoryTamper-evident record of what your AI agent did, plus local-first verifiable memory. | Local · stdio |
| Homey-Wan-Kenobi MCPMCP server for Homey Pro: 60 tools for devices, flows, energy, and Z-Wave/Zigbee diagnostics. | Local · stdio |
| HoneScore your judgment over AI-assisted work. Hone scores you, not the model. | Local · stdio |
| hood. - .hood name serviceResolve.hood names on Robinhood Chain - forward/reverse, text records, availability & pricing. | Remote · HTTPLive check: ✓ handshake |
| HooklayerViral-content intelligence for AI agents - 7 read-only MCP tools, evidence-layer scoring. | Remote · HTTPLive check: ✓ handshake |
| HopToDeskReach the computers you manage: list devices, run fixes, take screenshots, add devices. | Remote · HTTPLive check: sign-in required |