
TokRepo — AI Asset Registry
io.github.henu-wangPublished by GitHub account henu-wangv2.16.1Updated Oct 24, 2026
TokRepo MCP: tokrepo_discover, tokrepo_verify, tokrepo_install_plan for reusable AI assets.
Overview
TokRepo MCP lets an assistant search a registry of reusable AI assets, verify their trust evidence, plan and manage installs, and prepare assets for publishing.
- What you can do
- Search and browse the TokRepo registry of skills, prompts, MCP configs, scripts and agents, with details and dependency edges by asset ID or keyword, and turn a task or capability gap into ranked candidates with match reasons and install commands. Verify trust before activation: content and install-plan hashes, permission envelope, policy, trust score, evidence bundle, SBOM-lite, signature evidence, blockers and warnings. Get install plans with policy decisions, rollback and verification, then dry-run, stage, install, list, update, uninstall or roll back managed Codex installs. Prepare reusable local work after a task: read-only handoff packaging plans and harvest drafts of changed or named,
- When to use it
- Use it when an assistant should look for an existing skill, prompt, MCP config or workflow before building a one-off tool, or when you want trust checks and a rollback plan before installing a third-party AI asset. Also useful for turning finished project work into a reusable package draft.
- Requirements
- Runs locally over stdio, typically via npx with Node.js 18 or newer. Needs an internet connection because it queries the tokrepo.com API. No accounts, API keys or headers are declared. The optional init-agent command writes instruction files into a project.
Installation
In SourceWeft
- Open TokRepo — AI Asset Registry in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
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
Source: README.md at commit a02ef9e
Tools
0Version history
1- v2.16.1LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts