Developer · Remote MCP server
Zhijiangyun Cloud (智匠云)
Robot embodied-AI cloud for GPU training, inference, benchmarks, and robot data collection.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
cloud.artibot/zhijiangyun- Version
- 1.0.1
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-16
- Updated
- 2026-09-16
- Publisher
- cloud.artibot
- Namespace
- Namespace verified by the MCP Registry via the domain artibot.cloud · how
- Website
- mcp.artibot.cloud/
- Repository
- github.com/bofob/artibot-cloud
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.artibot.cloud/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; a Bearer token is asked for
- Checked on
- 2026-10-05
How to connect Zhijiangyun Cloud (智匠云)
Zhijiangyun Cloud (智匠云) is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.artibot.cloud/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 developer servers
| Server | Runs |
|---|---|
| Zeroidagent MCPA paid remote MCP for ZeroID, built to return verdicts, receipts, usage logs, and audit-ready JSON. | Remote · HTTPLive check: ✗ no handshake |
| 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 |
| ZihinChat with your Zihin.ai agents, list them and load platform skills from any MCP client. | Remote & Local · HTTP, stdioLive 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 |