# AGILEX Docs (remote · service.agilex.ai) Official AGILEX robotics product docs: manuals, CAN protocol, firmware, FAQ. Read-only. - Trust score: 68/100 (medium) - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-11-05 ## Components - remote · `service.agilex.ai`: 68/100 (this document), [markdown](https://verifymcp.io/servers/ai-agilex-service-docs/agilex-docs-mcp.md), [page](https://verifymcp.io/servers/ai-agilex-service-docs/agilex-docs-mcp) ## Channel facts - Endpoint: `https://service.agilex.ai/agilex-docs/mcp` - Transports: `streamable-http` - Auth: `none` - Version: `1.2.1` ## Trust breakdown How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-11-05. - **Endpoint Security**: 74/100 - The endpoint's TLS certificate is valid, in date, and uses a strong key. - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. - HTTPS is enforced; there's no plaintext access path. - HSTS check failed: the Strict-Transport-Security header is absent. - DNSSEC check failed: this domain isn't protected by DNSSEC. - **Transport & Reachability**: 100/100 - Verified streamable-http transport via a live MCP handshake. - **Schema Quality & AI Usability**: 63/100 - AI-judged instruction clarity (excellent). - Context-footprint check failed: tool/resource definitions use about 1620 tokens (~324/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 7/100 - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 71/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 0% of tool parameters carry a description. - Structured output schemas are declared (100% of tools); any adoption earns full credit. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation. - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 100/100 - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. ## Install ### How do I install the AGILEX Docs MCP server? AGILEX Docs is a hosted endpoint at https://service.agilex.ai/agilex-docs/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation. ### Claude ```bash claude mcp add --transport http ai-agilex-service-docs 'https://service.agilex.ai/agilex-docs/mcp' ``` ### Cursor ```json { "mcpServers": { "ai-agilex-service-docs": { "url": "https://service.agilex.ai/agilex-docs/mcp" } } } ``` ### VS Code ```json { "servers": { "ai-agilex-service-docs": { "type": "http", "url": "https://service.agilex.ai/agilex-docs/mcp" } } } ``` ### Codex ```toml [mcp_servers.ai-agilex-service-docs] url = "https://service.agilex.ai/agilex-docs/mcp" ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "ai-agilex-service-docs": { "type": "remote", "url": "https://service.agilex.ai/agilex-docs/mcp", "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add ai-agilex-service-docs --url 'https://service.agilex.ai/agilex-docs/mcp' --transport streamable-http ``` ### Hermes ```yaml mcp_servers: ai-agilex-service-docs: url: "https://service.agilex.ai/agilex-docs/mcp" ``` ### Netclaw ```json { "McpServers": { "ai-agilex-service-docs": { "Transport": "http", "Url": "https://service.agilex.ai/agilex-docs/mcp" } } } ``` ### Vellum ```bash assistant mcp add ai-agilex-service-docs -t streamable-http -u 'https://service.agilex.ai/agilex-docs/mcp' ``` ### Other ```json { "mcpServers": { "ai-agilex-service-docs": { "type": "http", "url": "https://service.agilex.ai/agilex-docs/mcp" } } } ``` The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs. ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-11-05 (score 68, +1) No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-11-04 (score 67, +6) - [security improvement] Authorization: unverified → partial - [security] The server rewrote its instructions, which are the text every model session reads - [security] Tool “find_in_doc” rewrote its description, which is the text the model reads - [security] Tool “search_docs” rewrote its description, which is the text the model reads - [security] Tool “get_doc” rewrote its description, which is the text the model reads - [security] Tool “list_docs” rewrote its description, which is the text the model reads - [functional regression] Schema quality: 209 → 324 - [functional regression] Schema quality: 209 → 285 - [functional regression] Schema quality: 209 → 267 - [functional improvement] Stability: unverified → 0.03 - [functional] Server version: 1.2.0 → 1.2.1 - [functional] Server version: 1.30.0 → 1.2.0 - [functional] New tool “find_in_doc” ### 2026-11-03 (score 61) First indexed and scored. ## MCP tools (5) ### `search_docs` (~275 tokens) Full-text search over the official AGILEX product documentation. Use this first for any question about AGILEX hardware: pinouts, CAN protocol details, baud rate, firmware upgrade, error codes, LED/beep meanings, installation, calibration, SDK usage. Args: query: Chinese or English keywords. Include the product name (piper / pika / nero / ranger / limo / scout / bunker / hunter / tracer / umr) plus the concept, e.g. "piper CAN 波特率". limit: 1-25 results, default 8. space: optional space slug or name fragment to narrow the search, e.g. "agx-chassis-manual-cn-en" or "底盘使用手册". Returns JSON: {query, count, results:[{doc_id,title,space,url,score,chars,snippet}]}. ``count`` is the number of results in this reply (0-``limit``). A result whose title carries 【未发】/【暂不对外】 includes ``status_note``. ``doc_id`` is what ``get_doc`` expects. Input parameters: - `limit` (integer) - `query` (string, required) - `space` (string) Output parameters: - `result` (string) ### `find_in_doc` (~460 tokens) Locate a passage *inside* one manual, without paging through it. Use this after ``search_docs`` whenever you need a specific table, command or error code rather than the whole page — including short documents, because manuals commonly open with a preamble and page 1 rarely answers a question. It returns the exact ``offset`` of each match, so one ``get_doc(doc_id, offset=...)`` lands on the right section. Prefer this over repeatedly calling ``get_doc`` with increasing offsets. Args: doc_id: id from ``search_docs`` (also accepts the page slug). query: the *concept*, not the product name — e.g. "波特率" or "急停 接线". Terms that already appear in this page's title are ignored, because ``search_docs`` picked the page by them; passing the product name again only adds noise. Generic words that appear in nearly every manual are down-weighted, so one distinctive term is enough. limit: 1-10 passages, default 5. Matching is OR, not AND: a passage is returned when it contains at least one term with enough weight. Terms that are absent from this page therefore do **not** force a zero result — check ``missing_terms`` to see which of your words this page never mentions, and ``matched_terms`` for the ones it does. A query made only of stop words (or nothing) returns ``count: 0`` with a hint. Returns JSON: {doc_id,title,space,url,chars,query,count,returned, matched_terms,missing_terms,hits:[{offset,heading,score,matched,excerpt}], hint}. ``count`` is the total number of matched passages; ``returned`` is how many are in ``hits`` (capped by ``limit``). ``heading`` is the nearest heading above the passage; ``offset`` is absolute in the page body. Input parameters: - `doc_id` (string, required) - `limit` (integer) - `query` (string, required) Output parameters: - `result` (string) ### `get_doc` (~247 tokens) Read one documentation page as Markdown. Call this with a ``doc_id`` returned by ``search_docs`` (or a slug such as ``ymZimX7JLe``). Manuals are often 20k-60k characters, so this tool paginates: if the reply has ``truncated: true`` and a ``next_offset``, call again with that ``offset`` to continue. Do not re-request the same offset. Args: doc_id: id from search_docs (also accepts the page slug). max_chars: characters per call, default 20000, max 120000. offset: start position, default 0. Returns JSON: {doc_id,title,space,url,chars,offset,returned,max_chars, truncated,next_offset,updated_at,content}. Always cite ``url``. If the page has no body (folder or unwritten page), the reply has ``empty: true`` and a hint — do not retry with other offsets. Input parameters: - `doc_id` (string, required) - `max_chars` (integer) - `offset` (integer) Output parameters: - `result` (string) ### `list_docs` (~188 tokens) List documented pages, optionally inside one space. Use when the caller wants an inventory ("what manuals exist for ranger") rather than an answer. Args: space: optional space slug or name fragment. limit: 1-300, default 100. offset: pagination offset, must be >= 0. Returns JSON: {space, count, offset, docs:[{doc_id,title,space,url,chars}]}. ``count`` is the number of docs in this page; there is no total field. ``count`` is the number of docs in this page; compare with ``limit`` to decide whether to request the next page. There is no total field — use ``list_spaces`` for per-space counts. Input parameters: - `limit` (integer) - `offset` (integer) - `space` (string) Output parameters: - `result` (string) ### `list_spaces` (~60 tokens) List the public documentation spaces with page counts. Call this when the caller is unsure which product family a document belongs to, or to explain coverage. Returns JSON: {count, spaces:[{space,name,docs,chars}]}. Output parameters: - `result` (string) ## Diagnostics Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-agilex-service-docs/agilex-docs-mcp#diagnostics ## Score history - 2026-11-05: 68 - 2026-11-04: 67 - 2026-11-03: 61 ## Common questions ### What is the AGILEX Docs MCP server? AGILEX Docs is an MCP server listed in the public MCP registry as ai.agilex.service/docs. Official AGILEX robotics product docs: manuals, CAN protocol, firmware, FAQ. Read-only. This page covers its hosted endpoint (https://service.agilex.ai/agilex-docs/mcp). ### Is the AGILEX Docs MCP server safe to use? AGILEX Docs scores 68 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm. ### What tools does the AGILEX Docs MCP server expose? AGILEX Docs exposes 5 tools: search_docs, find_in_doc, get_doc, list_docs, list_spaces. Their descriptions and schemas cost roughly 1,230 tokens of context every time the server is loaded. ### Does the AGILEX Docs MCP server require authentication? No. We connected to AGILEX Docs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address. ### Is the AGILEX Docs MCP server still maintained? AGILEX Docs is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced. ## Links - Remote endpoint: https://service.agilex.ai/agilex-docs/mcp - Repository: https://github.com/wgjsg/agilex-docs-mcp - Website: https://service.agilex.ai/agilex-docs/ - Changelog RSS feed: https://verifymcp.io/servers/ai-agilex-service-docs/agilex-docs-mcp.xml - Changelog JSON feed: https://verifymcp.io/servers/ai-agilex-service-docs/agilex-docs-mcp.json - HTML version of this page: https://verifymcp.io/servers/ai-agilex-service-docs/agilex-docs-mcp