
Capabilities Txt Registry
io.github.capabilityhostprotocol由 GitHub 账号 capabilityhostprotocol 发布v0.1.0更新于 Oct 24, 2026
Discover what websites across the agentic web can do — query the capabilities.txt registry.
概览
一个远程 MCP 服务器,让助手查询 capabilities.txt 注册表,发现智能体网络中各网站能做什么。
- 可以做什么
- 查询 capabilities.txt 注册表,依据公开的 capabilities.txt 约定及其结构化 JSON 形式,发现各主机声明自己具备的能力。清单未列出具体工具,因此确切的查询操作未在此说明。该注册表只是发现层:它公布能力,并指向 MCP 服务器、HTTP API 或其他端点以执行实际调用。
- 适用场景
- 当助手需要查明哪些网站或主机提供某项能力(例如创建支持工单或查询库存),再决定如何调用时使用。它适合发现与查找,而非亲自执行这些操作。
- 运行要求
- 位于 capabilitiestxt.org 的远程 streamable HTTP 端点;未声明任何软件包、环境变量、请求头或身份验证,清单标注其可在网页中执行。
安装
在 SourceWeft 中
- 打开 控制台中的 Capabilities Txt Registry,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。
交给智能体安装
把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。
阅读 https://sourceweft.com/mcp/io.github.capabilityhostprotocol%2Fcapabilities-txt-registry/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。其他 MCP 客户端
把它添加到你客户端的 mcpServers 配置中。
{
"mcpServers": {
"capabilities-txt-registry": {
"type": "http",
"url": "https://capabilitiestxt.org/api/mcp"
}
}
}README
capabilities.txt
A simple, open convention for a website to declare what it can do — the capabilities an agent can discover and invoke — at a well-known location.
The web taught machines to read in layers. robots.txt says what a crawler may
access. sitemap.xml says what exists. llms.txt says what's worth reading.
Each answers one narrow question for an automated reader.
None of them answers the question agents now ask: what can this host actually do?
Agents have stopped only reading the web and started acting on it. An agent that lands on your site can summarize your docs — but it has no standard way to discover that you expose a "create support ticket" capability, a "check inventory" capability, or "start a return," and how to call them. Today that happens through bespoke, one-vendor-at-a-time integrations.
capabilities.txt is the missing layer: a public, well-known file where a host
declares the capabilities it offers, so any agent can discover what it can do.
It is deliberately small. llms.txt worked because you could adopt it in an
afternoon. capabilities.txt follows the same rule.
The two forms
A host publishes one or both:
/capabilities.txt— human- and agent-readable markdown: capabilities grouped by category, each with an id, version, and one-line description./.well-known/capabilities.json— the structured form: an array of capability references, each resolvable to a full descriptor.
The markdown form is for discovery and reading. The JSON form is for machines that want structure. Publishing the markdown form alone is a perfectly good start.
Format (/capabilities.txt)
Rules, kept minimal:
- Line 1 is
# capabilities.txt. - A blockquote (
>) summary follows: one sentence on what the host offers, plus optional links (the JSON form, docs, an invocation endpoint). ##headings group capabilities by category (free-form, your choice).###headings name a group, optionally with a stable(group-id).- Each capability is a list item: a stable
capability-id, an optional(v<version>), and a short— description. - It's just markdown. If a human can read it and an agent can parse it, it's valid.
Structured form (/.well-known/capabilities.json)
Each entry is a reference; descriptor (optional) points to a full machine-readable
description of inputs, permissions, and how to invoke.
Where it sits among the standards
It is not a replacement for MCP or an API spec. The Model Context Protocol is a
stateful connection-and-invocation protocol; OpenAPI describes an HTTP API.
capabilities.txt is the layer before invocation — a static, public, crawlable
advertisement an agent (or a search engine) can read with no live connection, that
points to your MCP server, HTTP API, or other endpoint for the actual call.
Discovery and invocation are different jobs. capabilities.txt does discovery; it
hands off invocation.
Adopt it
Fastest (no spec): copy the prompt at capabilitiestxt.org/implement
and hand it to your AI coding agent — it writes your capabilities.txt from your code.
Have an OpenAPI spec? Generate it in your browser (paste the URL) — or keep it current automatically in CI with the GitHub Action:
Then check it at capabilitiestxt.org/submit for a grade, fixes, and a badge — and it’s discoverable in the directory + map.
By hand:
- List the capabilities your site exposes (or could).
- Write them into
/capabilities.txtusing the format above. - Optionally publish
/.well-known/capabilities.json. - Add yourself to
adopters.mdwith a pull request.
Already have an OpenAPI spec? Generate it — no manual authoring:
Working references — a real, live capabilities.txt plus illustrative templates
across markets (e-commerce, support, banking, healthcare, dev platform) — are in
examples/. The tools in tools/ generate and validate files.
Where this goes next
Discovery is the first step. Once an agent knows what you can do, the next
questions are may I, what happened, and can I prove it — invocation,
governance, and evidence. Those are defined by the
Capability Host Protocol (CHP), an open
protocol for which capabilities.txt is the natural public face. You can adopt
capabilities.txt on its own; CHP is where it leads if you need the rest.
Status & license
This is a proposal with a working reference, not a finished standard — and it's better for your feedback. Open an issue or PR.
- Specification & site text (
README.md,index.html,SPEC.md): CC BY 4.0 — seeLICENSE-DOCS. - Tooling (
tools/): Apache-2.0 — seeLICENSE. - "capabilities.txt" is a free, open convention — use it freely. (No trademark.)
Copyright © 2026 Project Auxo, Inc. and contributors.
来源:README.md,提交 1f62cab
工具
0版本历史
1- v0.1.0最新Sep 16, 2026
评分
已满足适用检查项的 40%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通必需25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式必需10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分
请在仓库或注册中心条目中声明许可证。