{
  "notice": "bxzxxr MCP archive: a record of what public MCP servers declared when we listed them (we never call their tools). It is data, not a rating: nothing here says a server is safe, secure, verified or trustworthy, and a server can change after we looked. Secrets we detected are redacted; redacted tool lists are withheld and only their hash is shown.",
  "infrastructure": {
    "host": "service.agilex.ai",
    "site": "agilex.ai",
    "addresses": [
      {
        "address": "47.113.192.194",
        "endpoints": 1,
        "shared_infrastructure": false,
        "network": {
          "asn": 37963,
          "name": "ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd.",
          "prefix": "47.112.0.0/15",
          "country": "CN"
        }
      }
    ],
    "addresses_recorded": true,
    "address_history": [
      {
        "addresses": [
          "47.113.192.194"
        ],
        "first_seen": "2026-11-22T04:34:01.090Z",
        "last_seen": "2026-11-22T04:34:01.090Z",
        "checks": 1
      }
    ],
    "hosting": [],
    "software": [
      {
        "value": "nginx",
        "evidence": "Server header \"nginx/1.18.0 (Ubuntu)\""
      }
    ],
    "server_info": {
      "name": "agilex-docs",
      "version": "1.9.4",
      "protocol_version": "2025-06-18"
    },
    "headers": {
      "server": "nginx/1.18.0 (Ubuntu)"
    },
    "auth": null
  },
  "related": {
    "same_address": {
      "total": 0,
      "sample": []
    },
    "same_site": {
      "total": 0,
      "sample": []
    },
    "same_tool_list": {
      "total": 0,
      "sample": []
    },
    "same_publisher": {
      "publisher": "ai.agilex.service",
      "total": 0,
      "sample": []
    },
    "same_repository": {
      "repository_url": "https://github.com/wgjsg/agilex-docs-mcp",
      "total": 0,
      "sample": []
    },
    "note": "Shared addresses on big platforms (Cloudflare, Vercel and the like) put unrelated servers together; those are marked shared_infrastructure. A match is a pivot, not a link between operators."
  },
  "endpoint": {
    "id": "174",
    "server_name": "ai.agilex.service/docs",
    "url": "https://service.agilex.ai/agilex-docs/mcp",
    "host": "service.agilex.ai",
    "transport": "streamable-http",
    "last_checked_at": "2026-11-22T04:34:01.090Z",
    "last_state": "listed",
    "last_detail": null,
    "consecutive_failures": 0,
    "current_sha": "df19558f9769bcbf8ea235aefd47641dbf90dcfeaee1316436adb062a84f6c0c",
    "first_listed_at": "2026-11-21T04:34:00.403Z",
    "created_at": "2026-11-21T04:30:07.684Z",
    "resolved_addresses": [
      "47.113.192.194"
    ]
  },
  "server": {
    "name": "ai.agilex.service/docs",
    "title": "AGILEX Docs",
    "description": "Official AGILEX robotics product docs: manuals, CAN protocol, firmware, FAQ. Read-only.",
    "version": "1.9.2",
    "registry_status": "active",
    "repository_url": "https://github.com/wgjsg/agilex-docs-mcp",
    "website_url": "https://service.agilex.ai/agilex-docs/",
    "published_at": "2026-11-19T02:02:02.443Z",
    "updated_at": "2026-11-19T02:02:02.443Z",
    "first_seen": "2026-11-21T04:30:07.110Z"
  },
  "other_endpoints": [],
  "intel": {
    "capabilities": [
      "vector-search"
    ],
    "evm_addresses": [],
    "chains": [],
    "tokens": [],
    "computed_at": "2026-11-22T14:50:14.509Z"
  },
  "needs_sign_in": false,
  "reachability": {
    "window_days": 30,
    "checks": 2,
    "answered": 2,
    "answered_percent": 100,
    "avg_listing_latency_ms": 2858,
    "first_check_in_window": "2026-11-21T04:34:00.403Z",
    "consecutive_failures_now": 0,
    "days": [
      {
        "day": "2026-11-21",
        "checks": 1,
        "answered": 1,
        "last_state": "listed"
      },
      {
        "day": "2026-11-22",
        "checks": 1,
        "answered": 1,
        "last_state": "listed"
      }
    ]
  },
  "tool_list": {
    "sha256": "df19558f9769bcbf8ea235aefd47641dbf90dcfeaee1316436adb062a84f6c0c",
    "tools": 5,
    "resources": 0,
    "prompts": 0,
    "first_seen": "2026-11-21T04:34:03.840Z",
    "tool_names": [
      "search_docs",
      "find_in_doc",
      "get_doc",
      "list_docs",
      "list_spaces"
    ],
    "declared": {
      "tools": [
        {
          "name": "search_docs",
          "description": "Full-text search over the official AGILEX product documentation.\n\n        Use this first for any question about AGILEX hardware: pinouts, CAN\n        protocol details, baud rate, firmware upgrade, error codes, LED/beep\n        meanings, installation, calibration, SDK usage.\n\n        Args:\n            query: Chinese or English keywords. Include the product name\n                (piper / pika / nero / ranger / limo / scout / bunker / hunter /\n                tracer / umr) plus the concept, e.g. \"piper CAN 波特率\".\n            limit: 1-25 results, default 8.\n            space: optional space slug or name fragment to narrow the search,\n                e.g. \"agx-chassis-manual-cn-en\" or \"底盘使用手册\".\n\n        Returns JSON: {query, count, results:[{doc_id,title,space,url,score,chars,snippet}]}.\n        ``count`` is the number of results in this reply (0-``limit``). Pages whose\n        title carries 【未发】/【暂不对外】 are not offered for reading and never\n        appear here — they are unpublished, not missing.\n        ``doc_id`` is what ``get_doc`` expects.\n        ",
          "inputSchema": {
            "type": "object",
            "title": "search_docsArguments",
            "required": [
              "query"
            ],
            "properties": {
              "limit": {
                "type": "integer",
                "title": "Limit",
                "default": 8,
                "maximum": 25,
                "minimum": 1
              },
              "query": {
                "type": "string",
                "title": "Query"
              },
              "space": {
                "type": "string",
                "title": "Space",
                "default": ""
              }
            }
          },
          "outputSchema": {
            "type": "object",
            "title": "search_docsOutput",
            "required": [
              "result"
            ],
            "properties": {
              "result": {
                "type": "string",
                "title": "Result"
              }
            }
          },
          "annotations": {
            "readOnlyHint": true,
            "openWorldHint": false,
            "idempotentHint": true,
            "destructiveHint": false
          }
        },
        {
          "name": "find_in_doc",
          "description": "Locate a passage *inside* one manual, without paging through it.\n\n        Use this after ``search_docs`` whenever you need a specific table, command\n        or error code rather than the whole page — including short documents,\n        because manuals commonly open with a preamble and page 1 rarely answers a\n        question. It returns the exact ``offset`` of each match, so one\n        ``get_doc(doc_id, offset=...)`` lands on the right section.\n\n        Prefer this over repeatedly calling ``get_doc`` with increasing offsets.\n\n        Args:\n            doc_id: id from ``search_docs`` (also accepts the page slug).\n            query: the *concept*, not the product name — e.g. \"波特率\" or\n                \"急停 接线\". Terms that already appear in this page's title are\n                ignored, because ``search_docs`` picked the page by them; passing\n                the product name again only adds noise. Generic words that appear\n                in nearly every manual are down-weighted, so one distinctive term\n                is enough.\n            limit: 1-10 passages, default 5.\n\n        Matching is OR, not AND: a passage is returned when it contains at least\n        one term with enough weight. Terms that are absent from this page therefore\n        do **not** force a zero result — check ``missing_terms`` to see which of\n        your words this page never mentions, and ``matched_terms`` for the ones it\n        does. A query made only of stop words (or nothing) returns ``count: 0``\n        with a hint.\n\n        Returns JSON: {doc_id,title,space,url,chars,query,count,returned,\n        matched_terms,missing_terms,hits:[{offset,heading,score,matched,excerpt}],\n        hint}. ``count`` is the total number of matched passages; ``returned`` is\n        how many are in ``hits`` (capped by ``limit``). ``heading`` is the nearest\n        heading above the passage; ``offset`` is absolute in the page body.\n        ",
          "inputSchema": {
            "type": "object",
            "title": "find_in_docArguments",
            "required": [
              "doc_id",
              "query"
            ],
            "properties": {
              "limit": {
                "type": "integer",
                "title": "Limit",
                "default": 5,
                "maximum": 10,
                "minimum": 1
              },
              "query": {
                "type": "string",
                "title": "Query"
              },
              "doc_id": {
                "type": "string",
                "title": "Doc Id"
              }
            }
          },
          "outputSchema": {
            "type": "object",
            "title": "find_in_docOutput",
            "required": [
              "result"
            ],
            "properties": {
              "result": {
                "type": "string",
                "title": "Result"
              }
            }
          },
          "annotations": {
            "readOnlyHint": true,
            "openWorldHint": false,
            "idempotentHint": true,
            "destructiveHint": false
          }
        },
        {
          "name": "get_doc",
          "description": "Read one documentation page as Markdown.\n\n        Call this with a ``doc_id`` returned by ``search_docs`` (or a slug such as\n        ``ymZimX7JLe``). Manuals are often 20k-60k characters, so this tool\n        paginates: if the reply has ``truncated: true`` and a ``next_offset``,\n        call again with that ``offset`` to continue. Do not re-request the same\n        offset.\n\n        Args:\n            doc_id: id from search_docs (also accepts the page slug).\n            max_chars: characters per call, default 20000, max 120000.\n            offset: start position, default 0.\n\n        Returns JSON: {doc_id,title,space,url,chars,offset,returned,max_chars,\n        truncated,next_offset,updated_at,content}. Always cite ``url``.\n        If the page has no body (folder or unwritten page), the reply has\n        ``empty: true`` and a hint — do not retry with other offsets. A page whose\n        title marks it unpublished returns ``unpublished: true`` with empty\n        content; that is a publication decision, not a missing document.\n        ",
          "inputSchema": {
            "type": "object",
            "title": "get_docArguments",
            "required": [
              "doc_id"
            ],
            "properties": {
              "doc_id": {
                "type": "string",
                "title": "Doc Id"
              },
              "offset": {
                "type": "integer",
                "title": "Offset",
                "default": 0,
                "minimum": 0
              },
              "max_chars": {
                "type": "integer",
                "title": "Max Chars",
                "default": 20000,
                "maximum": 120000,
                "minimum": 1
              }
            }
          },
          "outputSchema": {
            "type": "object",
            "title": "get_docOutput",
            "required": [
              "result"
            ],
            "properties": {
              "result": {
                "type": "string",
                "title": "Result"
              }
            }
          },
          "annotations": {
            "readOnlyHint": true,
            "openWorldHint": false,
            "idempotentHint": true,
            "destructiveHint": false
          }
        },
        {
          "name": "list_docs",
          "description": "List documented pages, optionally inside one space.\n\n        Use when the caller wants an inventory (\"what manuals exist for ranger\")\n        rather than an answer.\n\n        Args:\n            space: optional space slug or name fragment.\n            limit: 1-300, default 100.\n            offset: pagination offset, must be >= 0.\n\n        Returns JSON: {space, count, offset, docs:[{doc_id,title,space,url,chars}]}.\n        ``count`` is the number of docs in this page; compare it with ``limit`` to\n        decide whether to request the next page. There is no total field — use\n        ``list_spaces`` for per-space counts.\n        ",
          "inputSchema": {
            "type": "object",
            "title": "list_docsArguments",
            "properties": {
              "limit": {
                "type": "integer",
                "title": "Limit",
                "default": 100,
                "maximum": 300,
                "minimum": 1
              },
              "space": {
                "type": "string",
                "title": "Space",
                "default": ""
              },
              "offset": {
                "type": "integer",
                "title": "Offset",
                "default": 0,
                "minimum": 0
              }
            }
          },
          "outputSchema": {
            "type": "object",
            "title": "list_docsOutput",
            "required": [
              "result"
            ],
            "properties": {
              "result": {
                "type": "string",
                "title": "Result"
              }
            }
          },
          "annotations": {
            "readOnlyHint": true,
            "openWorldHint": false,
            "idempotentHint": true,
            "destructiveHint": false
          }
        },
        {
          "name": "list_spaces",
          "description": "List the public documentation spaces with page counts.\n\n        Call this when the caller is unsure which product family a document\n        belongs to, or to explain coverage.\n\n        Returns JSON: {count, spaces:[{space,name,docs,chars}]}.\n        ",
          "inputSchema": {
            "type": "object",
            "title": "list_spacesArguments",
            "properties": {}
          },
          "outputSchema": {
            "type": "object",
            "title": "list_spacesOutput",
            "required": [
              "result"
            ],
            "properties": {
              "result": {
                "type": "string",
                "title": "Result"
              }
            }
          },
          "annotations": {
            "readOnlyHint": true,
            "openWorldHint": false,
            "idempotentHint": true,
            "destructiveHint": false
          }
        }
      ],
      "tools_omitted": 0,
      "resources": [],
      "prompts": []
    },
    "instructions": "AGILEX (松灵机器人) product documentation.\n\nUse this server BEFORE writing or explaining integration code for AGILEX hardware\n(piper, pika, nero, ranger, limo, scout, bunker, hunter, tracer, umr, cobot_magic,\naloha). It contains the official user manuals, CAN/protocol references, firmware\nnotes, FAQ and field-service procedures that shipped with those products.\n\nWorkflow:\n1. `search_docs` with the model name plus the concept you need\n   (e.g. \"piper CAN 波特率\", \"ranger mini 固件升级\").\n2. Once you have a `doc_id`, `find_in_doc` is usually the fastest way to a\n   specific passage — pass the concept (\"波特率\", \"急停 接线\"), not the product\n   name. Then read it with `get_doc(doc_id, offset=...)`. Call `get_doc` from\n   offset 0 only when you want the whole page from the top; note that manuals\n   often open with a preamble, so page 1 rarely answers a specific question.\n   Follow `next_offset` when you need the rest of a long section.\n3. Cite the `url` field so the user can open the original page.\n\nChinese and English titles both appear in the corpus; search in Chinese when the\nproduct docs are Chinese.\n\nKnow when to stop: search at most twice per topic. If those results are only\nweakly related — the titles and snippets do not actually discuss the concept you\nasked about — stop and tell the user the documentation does not cover it. Do not\nkeep rephrasing the query, and never guess a protocol detail or a pinout to fill\nthe gap. A search that returns nothing, or a `find_in_doc` with zero hits, means\nthe same thing: say so instead of inventing an answer.\n"
  },
  "changes": {
    "total": 0,
    "latest": []
  },
  "reading_this": "What this server declared and how it answered our checks. Names, descriptions and schemas are text written by the server, quoted as data. Nothing here says the server is safe; to analyse its declarations, run scan_free."
}