Developer · Remote MCP server
Zihin
Chat with your Zihin.ai agents, list them and load platform skills from any MCP client.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
ai.zihin/mcp-server- Version
- 2.2.1
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-09-02
- Updated
- 2026-09-02
- Publisher
- ai.zihin
- Namespace
- Namespace verified by the MCP Registry via the domain zihin.ai · how
- Repository
- github.com/zihin-ai/zihin-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://llm.zihin.ai/mcp | X-Api-Key (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
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @zihin/mcp-server | 2.2.1 | stdio |
How to connect Zihin
Zihin is a remote MCP server: there is nothing to install. Its endpoint is https://llm.zihin.ai/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: X-Api-Key (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.
It can also run locally from a Node.js package published to the npm registry: @zihin/mcp-server version 2.2.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @zihin/mcp-server@2.2.1. It reads the environment variable ZIHIN_API_KEY (required, secret); set it in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@zihin/mcp-server@2.2.1"
],
"env": {
"ZIHIN_API_KEY": "<secret>"
}
}
}
}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 developer servers
| Server | Runs |
|---|---|
| Zerolangcompiler MCPA paid remote MCP for ZeroLang, built to return verdicts, receipts, usage logs, and audit-ready JSON. | Remote · HTTPLive check: ✗ no handshake |
| Zeta Chain CliCreate friendly, customizable greetings for any name or audience. Break the ice in demos, onboardi… | Remote · HTTPLive check: ✗ no handshake |
| Zhiji LLM Router - Signal GatewayLLM routing and A-share market phase signals via LG framework. | Remote · HTTPLive check: ✓ handshake |
| Zhijiangyun Cloud (智匠云)Robot embodied-AI cloud for GPU training, inference, benchmarks, and robot data collection. | Remote · HTTPLive check: sign-in required |
| ZikkaronBiologically-inspired persistent memory engine for Claude Code MCP agents. | Local · stdio |
| ZKshareZKshare stdio MCP: store/prove/share, semantic search, sandbox proxy to HTTPS /api/v1/context. | Local · stdio |
| Zoekt MCPFast indexed code search for AI agents, powered by Sourcegraph Zoekt. | Local · stdio |
| ZoneFoundry for SonosControl Sonos from any MCP client. No bridge hardware; connects over OAuth - no API key to paste. | Remote · HTTPLive check: sign-in required |