m5-doc-server
Registry code: a7cd8591d89ea011
优先使用 knowledge_search 获取低延迟原始资料;需要整理后的完整答复时使用 knowledge_answer。资料缺失、错误、示例损坏或工具异常时,应主动调用 knowledge_feedback 提交可复现反馈。
- endpoint
- https://mcp.m5stack.com/sse
- protocol
- streamable-http ·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 m5-doc-server live?
- Yes — it answered the hub's last check (checked 11h ago). It answered 100% of checks over the last 30 days.
- Is m5-doc-server free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does m5-doc-server have?
- 3 tools: knowledge_answer, knowledge_feedback, knowledge_search.
- Is m5-doc-server 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.
90 days 100%· all time 100%
last good check
of 3 tools
- unknown → live
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.
through this hub
successful
what callers paid
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
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.
knowledge_answer unknown 11h ago
调用 M5Stack FAE AI,将原始问题整理成可直接使用的专业答复。 复杂问题可能耗时一分钟以上,客户端应等待工具完成。只需要低延迟原文片段时使用 knowledge_search;回答缺失、错误或无法复现时请调用 knowledge_feedback。
{ "type": "object", "title": "knowledge_answer_toolArguments", "required": [ "question" ], "properties": { "question": { "type": "string", "title": "Question", "maxLength": 20000, "minLength": 1, "description": "用户原始问题" } } }arguments 16 linesknowledge_feedback unknown never probed
向 M5Stack 提交知识缺失、内容错误、未支持功能、损坏示例或工具 bug。 反馈会重点写入云日志并进入人工评估。鼓励 Agent 在检索或回答不完整时大胆反馈,说明 原始问题、相关产品、缺失内容、复现方式和期望资料,不必等待用户明确要求。
{ "type": "object", "title": "knowledge_feedback_toolArguments", "required": [ "category", "feedback" ], "properties": { "product": { "anyOf": [ { "type": "string", "maxLength": 200 }, { "type": "null" } ], "title": "Product", "default": null, "description": "相关产品、芯片、Unit、Module 或 SDK" }, "category": { "enum": [ "missing_documentation", "incorrect_information", "unsupported_feature", "broken_example", "tool_error", "other" ], "type": "string", "title": "Category", "description": "反馈分类" }, "feedback": { "type": "string", "title": "Feedback", "maxLength": 8000, "minLength": 10, "description": "可复现的问题或缺失资料" }, "severity": { "enum": [ "low", "medium", "high" ], "type": "string", "title": "Severity", "default": "medium", "description": "影响程度" }, "source_tool": { "enum": [ "knowledge_search", "knowledge_answer", "other" ], "type": "string", "title": "Source Tool", "default": "knowledge_search", "description": "发现问题时使用的工具" }, "original_question": { "anyOf": [ { "type": "string", "maxLength": 8000 }, { "type": "null" } ], "title": "Original Question", "default": null, "description": "触发反馈的原始问题" }, "expected_information": { "anyOf": [ { "type": "string", "maxLength": 4000 }, { "type": "null" } ], "title": "Expected Information", "default": null, "description": "期望补充或修正的资料" } } }arguments 94 linesknowledge_search unknown 11h ago
从 M5Stack 官方知识库检索产品、硬件、编程和芯片资料。 适用于产品规格、SKU、接口引脚、GPIO、供电、电气特性、兼容性、选型、Arduino、 UIFlow/UIFlow2、MicroPython、ESP-IDF、ESPHome、代码示例、芯片手册和故障排除。 结果有服务端字符上限(默认 12000);若末尾提示分页,请带上返回的 offset 继续检索后续内容。 如果检索不到需要的功能、说明或示例,请继续调用 knowledge_feedback 主动反馈。
{ "type": "object", "title": "knowledge_search_toolArguments", "required": [ "query" ], "properties": { "query": { "type": "string", "title": "Query", "maxLength": 20000, "minLength": 1, "description": "知识库查询词或用户原始问题" }, "offset": { "type": "integer", "title": "Offset", "default": 0, "maximum": 1000000000, "minimum": 0, "description": "结果字符偏移量;首次调用传 0,继续翻页时传 next_offset" }, "is_chip": { "type": "boolean", "title": "Is Chip", "default": false, "description": "是否需要检索芯片手册和底层电气资料" }, "filter_type": { "anyOf": [ { "enum": [ "product", "product_no_eol", "program", "arduino", "uiflow", "esp-idf", "esphome" ], "type": "string" }, { "type": "null" } ], "title": "Filter Type", "default": null, "description": "限定检索的知识库类型" } } }arguments 52 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's ida7cd8591d89ea011.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/a7cd8591d89ea011/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/a7cd8591d89ea011?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.