Zihin MCP Server — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Zihin local stdio-to-HTTP MCP proxy: Does proxy authentication preserve the remote account's tool scope and avoid presenting the proxy as a separate hosted engine?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Invoke/manage Zihin agents and access platform skills from MCP clients through a stdio-to-HTTP proxy.

What we know

Official local proxy connecting stdio MCP clients to Zihin's hosted MCP endpoint. Also exposes/installable procedural skills/resources for agent creation, tools, triggers, diagnostics and governance.

Maintenance / activity evidence

@zihin/mcp-server 2.2.2 published 2026-10-04T21:45:37.304Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Hosted agent/platform authority according to account, plus local skill installation. Writes: Invoke agents; Potential hosted agent/tool/triggers operations; Install/update local skill files/config.
Zihin API key.
Sensitive access: Agent prompts/results, Platform configuration, API key

Hosted tool surface may mutate platform state; inspect live tools and account permissions.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Does proxy authentication preserve the remote account's tool scope and avoid presenting the proxy as a separate hosted engine?

The bounded review of the publisher's documented Zihin local stdio-to-HTTP MCP proxy and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Hosted tool surface may mutate platform state; inspect live tools and account permissions.
Hosted agent/platform authority according to account, plus local skill installation.
Zihin API key.
Agent prompts/results and platform state are processed by Zihin; local install-skills modifies project/client files.
Reviewed write actions: Invoke agents; Potential hosted agent/tool/triggers operations; Install/update local skill files/config
Sensitive access: Agent prompts/results, Platform configuration, API key
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
The local package is a proxy; hosted server determines the live tool surface and account authority.
Installing skills can modify local client/project configuration such as AGENTS.md-managed blocks.
Commercial quota/subscription errors are enforced server-side.

Original activity observations

@zihin/mcp-server 2.2.2 published 2026-10-04T21:45:37.304Z

Technical identity

npm/@zihin/mcp-server

Exact implementation source: https://www.npmjs.com/package/@zihin/mcp-server ↗
Reviewed resource type: Gateway
Repository identity: zihin-ai/zihin-mcp
Package identity: npm:@zihin/mcp-server
Service endpoint: https://llm.zihin.ai/mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry ↗
@zihin/mcp-server
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.
Repository document ↗
zihin-ai/zihin-mcp
Recorded repository material and project history.
Evidence source ↗
docs.zihin.ai/reference/sdks
Source material retained for this review.
Includes references whose attribution is not established.
Evidence source ↗
docs.zihin.ai/reference/changelog
Source material retained for this review.
Includes references whose attribution is not established.

Setup · Watchlist

Gateway setup

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Warning

Not runtime tested, no third-party installation, network authorization, paid calls, or mutation executed.
Do not claim production service is available based on README alone.
Tenant-scoped key; use real credential in MCP client environment
Official npm publisher package page README inspected for this exact npm identity; static research only. Some setup statements are conservatively summarized; no source code or live client execution checked. V2 review did not run any live client.
Check actual host syntax and supply credentials in secure client environment; do not paste placeholders verbatim.
Avoid write, payment, token transfer, publishing, sending, booking and remote account changes as tests.
Replace credential, action and registration placeholders; follow the matching publisher/client prerequisites. No execution performed.
Use the matching host, actual registration name and original installation environment; this does not revoke credentials.

Install / configure gateway service
Publisher instructions
Tenant-scoped key; use real credential in MCP client environment | Publisher npm README revisited on 2026-10-14; exact identity retained.
Reviewed setup example · Claude Code only · Publisher instructions · Review before use
```
claude mcp add zihin -e ZIHIN_API_KEY=<KEY> -- npx -y @zihin/mcp-server
```
Configure / authenticate
MCP100 setup guide
Set ZIHIN_API_KEY to a publisher-issued zhn_live_*/zhn_test_* key.
Required environment variables: ZIHIN_API_KEY
Check connection
Suggested check
Confirm Zihin MCP tools are listed, then perform an authorized read-only call.
Remove / uninstall / revoke
MCP100 setup guide
If registered by the publisher Claude Code example under `zihin`, run the provided unregister command; for a different MCP client or name, delete the actual client registration. Removing a local client entry is distinct from deleting a vendor account/token.
Remove named client registration · Claude Code only · MCP100 composed guide
claude mcp remove zihin

Official Documentation & Sources

What it does

Official local proxy connecting stdio MCP clients to Zihin's hosted MCP endpoint. Also exposes/installable procedural skills/resources for agent creation, tools, triggers, diagnostics and governance.

Capability: AI & Reasoning
Resource type: Gateway
Best fit: Invoke/manage Zihin agents and access platform skills from MCP clients through a stdio-to-HTTP proxy.

Representative uses

List/invoke Zihin agents
Use hosted Zihin MCP tools
Load platform skills/resources
Install client-native skills into supported IDEs

Limitations

The local package is a proxy; hosted server determines the live tool surface and account authority.
Installing skills can modify local client/project configuration such as AGENTS.md-managed blocks.
Commercial quota/subscription errors are enforced server-side.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Zihin API key.
Permissions: Hosted agent/platform authority according to account, plus local skill installation.
Data handling: Agent prompts/results and platform state are processed by Zihin; local install-skills modifies project/client files.
Cost: subscription_or_quota
Risk and cautions: Hosted tool surface may mutate platform state; inspect live tools and account permissions.

Access scope and cautions

Write actions: Invoke agents Potential hosted agent/tool/triggers operations Install/update local skill files/config
Sensitive access: Agent prompts/results Platform configuration API key
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which implementation does this page cover?

Official local proxy connecting stdio MCP clients to Zihin's hosted MCP endpoint. Also exposes/installable procedural skills/resources for agent creation, tools, triggers, diagnostics and governance.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @zihin/mcp-server. Recorded endpoint: https://llm.zihin.ai/mcp. Recorded transport: stdio, streamable_http. Recorded environment-variable notes: ZIHIN_API_KEY. No configuration values are supplied here. Prerequisites: Node.js >=20; Zihin account/key. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Zihin API key (`zhn_live_*`) forwarded to hosted MCP.

Can it modify data or perform write operations?

Documented write actions include: Invoke agents; Potential hosted agent/tool/triggers operations; Install/update local skill files/config. Recorded permission boundary: Hosted agent/platform authority according to account, plus local skill installation.

What data-handling boundary should I consider?

Agent prompts/results and platform state are processed by Zihin; local install-skills modifies project/client files. Recorded sensitive-access context: Agent prompts/results; Platform configuration; API key.

What limitations and risks should I check before use?

Hosted tool surface may mutate platform state; inspect live tools and account permissions. The local package is a proxy; hosted server determines the live tool surface and account authority. Installing skills can modify local client/project configuration such as AGENTS.md-managed blocks. Commercial quota/subscription errors are enforced server-side. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

What cost model is recorded?

The reviewed cost model is subscription or quota. This classification does not establish current prices, quotas or the cost of every downstream operation. Check the applicable service terms before authorizing paid actions.

Why we’re tracking it

Best fit

What we know

Maintenance / activity evidence

Verification gaps / watch-outs

Original activity observations

Evidence & Sources

Gateway setup

Install / configure gateway service

Configure / authenticate

Check connection

Remove / uninstall / revoke

Official Documentation & Sources

What it does

Representative uses

Limitations

Access & risk

Access scope and cautions

FAQ