_ registry / mcp http-sse · checked 1h ago

agilex-docs

https://service.agilex.ai

Registry code: 60eeed3dfdbbf62e

api record

AGILEX (松灵机器人) product documentation.

Use this server BEFORE writing or explaining integration code for AGILEX hardware

endpoint
https://service.agilex.ai/agilex-docs/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is agilex-docs live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is agilex-docs free to use?
Yes — the hub reached it with no key and no payment.
What tools does agilex-docs have?
4 tools: list_docs, get_doc, search_docs, list_spaces.
Is agilex-docs safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
940ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
1 open 3 never probed 1 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_spaces open 1h ago

    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}]}.

    mcp-tool

    {
      "type": "object",
      "title": "list_spacesArguments",
      "properties": {}
    }
    arguments 5 lines
  • list_docs unknown never probed

    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}]}.

    mcp-tool

    {
      "type": "object",
      "title": "list_docsArguments",
      "properties": {
        "limit": {
          "type": "integer",
          "title": "Limit",
          "default": 100
        },
        "space": {
          "type": "string",
          "title": "Space",
          "default": ""
        },
        "offset": {
          "type": "integer",
          "title": "Offset",
          "default": 0
        }
      }
    }
    arguments 21 lines
  • get_doc unknown 1h ago

    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``.

    mcp-tool

    {
      "type": "object",
      "title": "get_docArguments",
      "required": [
        "doc_id"
      ],
      "properties": {
        "doc_id": {
          "type": "string",
          "title": "Doc Id"
        },
        "offset": {
          "type": "integer",
          "title": "Offset",
          "default": 0
        },
        "max_chars": {
          "type": "integer",
          "title": "Max Chars",
          "default": 20000
        }
      }
    }
    arguments 23 lines
  • search_docs unknown 1h ago

    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.

    mcp-tool

    {
      "type": "object",
      "title": "search_docsArguments",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "title": "Limit",
          "default": 8
        },
        "query": {
          "type": "string",
          "title": "Query"
        },
        "space": {
          "type": "string",
          "title": "Space",
          "default": ""
        }
      }
    }
    arguments 23 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 60eeed3dfdbbf62e.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/60eeed3dfdbbf62e/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/60eeed3dfdbbf62e/badge.svg)](https://brick.blue/agent/60eeed3dfdbbf62e?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.