
TokRepo — AI Asset Registry
io.github.henu-wang由 GitHub 账号 henu-wang 发布v2.16.1更新于 Oct 24, 2026
TokRepo MCP: tokrepo_discover, tokrepo_verify, tokrepo_install_plan for reusable AI assets.
概览
TokRepo MCP 让助手搜索可复用 AI 资产注册表、核验其信任证据、规划并管理安装,以及准备待发布资产。
- 可以做什么
- 搜索和浏览 TokRepo 注册表中的技能、提示词、MCP 配置、脚本和智能体,按资产 ID 或关键词查看详情与依赖关系,并把任务或能力缺口转化为带匹配理由和安装命令的候选列表。激活前核验信任:内容与安装计划哈希、权限范围、策略、信任评分、证据包、SBOM-lite、签名证据、阻断项和警告。获取含策略决策、回滚和验证的安装计划,然后对受管的 Codex 安装执行试运行、暂存、安装、列出、更新、卸载或回滚。任务完成后准备可复用的本地成果:只读的交接打包计划和针对变更或指定文件的采集草稿。
- 适用场景
- 当助手应在自行编写一次性工具前先查找现成的技能、提示词、MCP 配置或工作流时适用;也适合在安装第三方 AI 资产前需要信任检查和回滚方案时使用。还可把已完成的项目工作整理成可复用的包草稿。
- 运行要求
- 以 stdio 在本地运行,通常通过 npx 启动,需要 Node.js 18 或更高版本。需要联网,因为会查询 tokrepo.com 的 API。未声明账号、API 密钥或请求头。可选的 init-agent 命令会向项目中写入指令文件。
安装
在 SourceWeft 中
- 打开 控制台中的 TokRepo — AI Asset Registry,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
README
TokRepo MCP Server
Agent-native MCP server for TokRepo: session bootstrap, capability discovery, search/detail, trust verification, install planning, Codex staging, lifecycle inspection/update/uninstall/rollback, handoff/harvest planning, and human-confirmed publishing of reusable AI assets.
Quick Start
Claude Code
Cursor / Windsurf
Add to your MCP config (~/.cursor/mcp.json):
OpenAI Codex / Gemini CLI
What It Does
Once connected, your AI assistant can:
- Discover during planning — turn a task or capability gap into structured candidate skills, prompts, MCP configs, scripts, and workflows
- Resolve capability gaps — select a candidate with verification evidence, install plan, lifecycle contract, next MCP calls, and CLI fallbacks before local build
- Search public AI assets by keyword or category with agent fit signals
- Browse trending assets, filter by type (MCP, Skill, Prompt, Agent, Script)
- Get details — full documentation, install instructions, and metadata
- Verify trust — read-only content hash, install plan hash, permission envelope, policy, trust_score_v2,
evidence_bundle, SBOM-lite,signature_evidence, blockers, and warnings - Plan before install — get install plan v2 with policy decisions, rollback, verification,
evidence_bundle, SBOM-lite, andsignature_evidence - Safe Codex install — dry-run by default; risky assets must be staged or explicitly approved
- Lifecycle control — list, update, uninstall, and roll back managed Codex installs
- Post-task harvest — inspect changed or explicit local files with
tokrepo_harvestbefore any push, including private package drafts,quality_gate, package manifest, SBOM-lite, and provenance - Project memory — pair with
tokrepo init-agent --target allso future agents know to call TokRepo during planning - Discovery surfaces — official MCP
server.json, A2A agent card, portable agent manifest, tool catalog,.well-known,agents.txt,llms.txt, and npm metadata are kept machine-readable for agents and registries - Funnel visibility — anonymous aggregate events show whether agents actually discover, plan, install, hand off, and push reusable assets
Available Tools
Example Conversations
Make Future Agents Discover TokRepo
Run this once in a project:
It writes managed instructions to AGENTS.md, CLAUDE.md, GEMINI.md, Cursor rules, GitHub Copilot instructions, Cline rules, Windsurf rules, Roo rules, OpenHands microagents, Aider conventions, .mcp.json, and .tokrepo/agent.json. The rule is simple: during planning, when the agent sees a capability gap, it should call tokrepo_resolve_capability or tokrepo_discover before inventing a one-off local tool. After a task, agents can call tokrepo_harvest or run tokrepo harvest --changed --json to suggest reusable files for user-confirmed private publishing.
Machine-Readable Listing
Registries and agents can discover this server through:
- MCP server manifest: tokrepo.com/.well-known/mcp/server.json
- TokRepo manifest: tokrepo.com/.well-known/tokrepo.json
- Portable agent manifest: tokrepo.com/.well-known/agent.json
- A2A agent card: tokrepo.com/.well-known/agent-card.json
- Tool catalog: tokrepo.com/.well-known/tool-catalog.json
- Trust manifest: tokrepo.com/.well-known/tokrepo-trust.json
- Default agent policy pack: tokrepo.com/policy-packs/default-agent-policy.json
- Eval evidence: tokrepo.com/evals/agent-discovery.json
- Multi-agent compatibility: tokrepo.com/evals/multi-agent-compatibility.json
- Agent memory schema: tokrepo.com/schemas/agent-memory.schema.json
- Agent evidence bundle schema: tokrepo.com/schemas/agent-evidence-bundle.schema.json
- Capability resolution schema: tokrepo.com/schemas/capability-resolution.schema.json
- Harvest report schema: tokrepo.com/schemas/harvest-report.schema.json
- Handoff package schema: tokrepo.com/schemas/handoff-package.schema.json
- Agent text entry: tokrepo.com/agents.txt
- Agent instructions: tokrepo.com/agent-instructions/tokrepo.md
- Agent ecosystem distribution pack: tokrepo.com/agent-ecosystem.json
- LLM crawler entry: tokrepo.com/llms.txt
Use https://tokrepo.com/agent-ecosystem.json for agent marketplace submissions, starter templates, README snippets, install guides, and example projects. It contains canonical listing copy, ecosystem channels, target project-memory files, and verification commands.
TokRepo emits anonymous aggregate funnel events for tokrepo_resolve_capability, tokrepo_discover, tokrepo_verify, tokrepo_install_plan, install dry-runs, installs, harvests, handoffs, and pushes. It does not send task text or file contents. Disable with TOKREPO_TELEMETRY=0.
Why TokRepo?
TokRepo is the open registry for AI assets — like npm for packages, but for AI skills, prompts, MCP configs, and workflows.
- Curated assets — quality-reviewed, not a dump
- Agent-native — every asset has machine-readable install contracts
- Universal — works with Claude Code, Cursor, Codex, Gemini CLI, and any MCP client
- CLI available —
npx tokrepo search "query"/npx tokrepo install <uuid>
Requirements
- Node.js >= 18
- Internet connection (queries tokrepo.com API)
Links
- Website: tokrepo.com
- CLI: npm: tokrepo
- GitHub: henu-wang/tokrepo-mcp-server
- API: tokrepo.com/.well-known/tokrepo.json
License
MIT
来源:README.md,提交 a02ef9e
工具
0版本历史
1- v2.16.1最新Sep 16, 2026
评分
已满足适用检查项的 50%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分