AGILEX Docs
ai.agilex.service/docsservice.agilex.aistreamable-httpv1.0.2Scanned
Official AGILEX robotics product docs: manuals, CAN protocol, firmware, FAQ. Read-only.
4 tools: 4 only read.
- Reads private data · 3
- Reads text others write · 0
- Can send data out · 0
- No findings
Anlyon alternative
Run the operations that matter as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Only reads 4Show 4 read-only tools
get_docRead one documentation page as Markdown.Reads private dataNo findings
Why it is in this group
- The name "get_doc" says "get": a word for reading.
What it can reach
- private-dataThe name "get_doc" says "get" and "doc": it reads documents.
Description, as the server wrote it 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,truncated, next_offset,updated_at,content}. Always cite ``url``.
list_docsList documented pages, optionally inside one space.Reads private dataNo findings
Why it is in this group
- The name "list_docs" says "list": a word for reading.
What it can reach
- private-dataThe name "list_docs" says "list" and "doc": it reads documents.
Description, as the server wrote it 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. Returns JSON: {count, total_shown, docs:[{doc_id,title,space,url,chars}]}.
list_spacesList the public documentation spaces with page counts.No findings
Why it is in this group
- The name "list_spaces" says "list": a word for reading.
Description, as the server wrote it 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}]}.
search_docsFull-text search over the official AGILEX product documentation.Reads private dataNo findings
Why it is in this group
- The name "search_docs" says "search": a word for reading.
What it can reach
- private-dataThe name "search_docs" says "search" and "doc": it reads documents.
Description, as the server wrote it 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}]}. ``doc_id`` is what ``get_doc`` expects.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.
- Reads private data3
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http docs https://service.agilex.ai/agilex-docs/mcpclaude mcp add --transport http docs https://service.agilex.ai/agilex-docs/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__docs__search_docs",
"mcp__docs__get_doc",
"mcp__docs__list_docs",
"mcp__docs__list_spaces"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as docs. Review it before you use it.
Capability tags behind 3 rules
- mcp__docs__search_docs private-data
- mcp__docs__get_doc private-data
- mcp__docs__list_docs private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://anlyon.dev/api/v1/servers/ai.agilex.service/docs/verify?hash=09bc4eb7598bf1d3f55272c12aa1a823d5d4d8d3edefe2337dcfc80e7f9d3f7a" | jq -e '.changed == false'Pinned hash 09bc4eb7598b, from Nov 3, 2026, 11:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://anlyon.dev/servers/ai.agilex.service/docs/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://anlyon.dev/servers/ai.agilex.service/docs)Source: MCP Registry · repository. Synced Nov 3, 2026, 11:17 UTC.