AGILEX Docs MCP server
ai.agilex.service/docsservice.agilex.aistreamable-httpv1.9.2Scanned
Official AGILEX robotics product docs: manuals, CAN protocol, firmware, FAQ. Read-only.
5 tools: 5 only read.
- Reads private data · 4
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the AGILEX Docs MCP server can do
The AGILEX Docs MCP server is published by service.agilex.ai, a domain the MCP Registry verified. It has 5 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
4 tools read private data (search_docs, find_in_doc, get_doc and 1 more).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 5 times since Anlyon Radar first saw them.
Last scanned Nov 19, 2026, version 1.9.2.
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.
5 tools
Only reads 5Show 5 read-only tools
find_in_docLocate a passage *inside* one manual, without paging through it.Reads private dataNo findings
Why it is in this group
- The name "find_in_doc" says "find": a word for reading.
What it can reach
- private-dataThe name "find_in_doc" says "find" and "doc": it reads documents.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
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,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. A page whose title marks it unpublished returns ``unpublished: true`` with empty content; that is a publication decision, not a missing document.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
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, must be >= 0. Returns JSON: {space, count, offset, docs:[{doc_id,title,space,url,chars}]}. ``count`` is the number of docs in this page; compare it with ``limit`` to decide whether to request the next page. There is no total field — use ``list_spaces`` for per-space counts.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
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}]}.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
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}]}. ``count`` is the number of results in this reply (0-``limit``). Pages whose title carries 【未发】/【暂不对外】 are not offered for reading and never appear here — they are unpublished, not missing. ``doc_id`` is what ``get_doc`` expects.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
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 data4
- 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.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 18, 2026, 16:21 UTC, unchanged since Nov 4, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
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.
Tools2 changed.~2 changedView diff
- Changed:get_docOnly readsdescription
- Changed:search_docsOnly readsdescription
Tools1 changed.~1 changedView diff
- Changed:list_docsOnly readsdescription
Tools3 changed.~3 changedView diff
- Changed:find_in_docOnly readsdescription
- Changed:list_docsOnly readsdescription
- Changed:search_docsOnly readsdescription
Tools5 changed.~5 changedView diff
- Changed:find_in_docOnly readsdescriptioninputSchemaannotations
- Changed:get_docOnly readsdescriptioninputSchemaannotations
- Changed:list_docsOnly readsdescriptioninputSchemaannotations
- Changed:list_spacesOnly readsannotations
- Changed:search_docsOnly readsinputSchemaannotations
Tools1 added.+1 addedView diff
- Added:find_in_docOnly reads
Install
Pinned to version 1.9.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__find_in_doc",
"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 4 rules
- mcp__docs__search_docs private-data
- mcp__docs__find_in_doc 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://radar.anlyon.com/api/v1/servers/ai.agilex.service/docs/verify?hash=00ee128cd591fdd5912b79ed380e8e5788b5273604b8e62450e4bf635108b73b" | jq -e '.changed == false'Pinned hash 00ee128cd591, from Nov 19, 2026, 02:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/ai.agilex.service/docs/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/ai.agilex.service/docs)Source: MCP Registry · repository. Synced Nov 19, 2026, 02:17 UTC.
AGILEX Docs MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the AGILEX Docs MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the AGILEX Docs MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the AGILEX Docs MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the AGILEX Docs MCP server have?
- 5 tools: 5 read. search_docs, find_in_doc, get_doc, list_docs and list_spaces.
Does the AGILEX Docs MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the AGILEX Docs MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the AGILEX Docs MCP server changed its tools?
- Yes, 5 times since Anlyon Radar started tracking it, most recently on Nov 13, 2026. Every change is on this page and in its Atom feed.