TokRepo — AI Asset Registry MCP server
io.github.henu-wang/tokrepo-mcp-server·v2.16.1TokRepo MCP: tokrepo_discover, tokrepo_verify, tokrepo_install_plan for reusable AI assets.
0 stars81 downloads/wk
Reviews
Write oneNobody has reviewed TokRepo — AI Asset Registry yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
TokRepo — AI Asset Registry tools (23, 2 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
tokrepo_clone_planPlan a bulk Codex install from a TokRepo user profile using the TokRepo CLI. Returns JSON dry-run output without writing files.
tokrepo_codex_installSTEP 3 of ATOMIC ACTION 2 (install safely into this repo). Safely install a TokRepo asset into local Codex. Defaults to dry_run=true. To write files, set dry_run=false and confirm=true. Risky assets require stage=true or approve_risk=true. Always call tokrepo_install_plan + tokrepo_verify first. On any failure call tokrepo_rollback (STEP 4 — the escape).
tokrepo_detailGet full details of a TokRepo asset by UUID, including description, content, tags, install instructions, and metadata.
tokrepo_discoverPlanning-time capability discovery for agents. Call this during autonomous planning when the task may need a reusable skill, MCP config, prompt, script, workflow, or other AI asset. Returns structured candidates, fit signals, and next MCP calls. [[tokrepo.discover-before-build]]
tokrepo_edgesRead the asset relationship graph for one asset. Returns inbound + outbound edges across requires (hard deps), extends (soft pairings), and co_used (behavior-derived co-installs). Use this BEFORE planning installs to discover related assets and avoid solo installs of assets that pair with others.
tokrepo_eval_agentwrite actionRun TokRepo agent-native evals through the CLI. Verifies filtered search, install-plan contracts, metadata quality reporting, Codex install verification, manifest state, and rollback using temporary local state.
tokrepo_find_for_taskATOMIC ACTION 1 of 3 (find / install / harvest). Find a TokRepo asset for a concrete task. Returns top-N ranked public workflows + match_reasons + install_command + url, backed by /api/v1/tokenboard/agent/find_for_task and counted in the find_for_task funnel step. Use this as the first call when the agent has a task and wants to discover whether an existing asset already solves it. For a broader p
tokrepo_handoff_planInspect local files after a task and return an agent handoff packaging plan with quality_gate, package_manifest, SBOM-lite, and provenance. This is read-only and never publishes automatically; use tokrepo_push only after human confirmation with explicit reviewed files.
tokrepo_harvestATOMIC ACTION 3 of 3 (harvest what this agent just created). Call at the END of every task that produced reusable artifacts. Inspects changed or explicit local files and produces private-by-default reusable asset package drafts with metadata, usage examples, risk notes, compatibility, and quality gates. Never publishes automatically — `tokrepo_push` is a separate user-gated call. Skipping harvest
tokrepo_installGet the install command and raw content for a TokRepo asset. Returns the content ready to be saved to a file or executed.
tokrepo_install_planSTEP 1 of ATOMIC ACTION 2 (install safely into this repo). Returns an agent-native install plan v2 for a TokRepo asset: preconditions, actions, risk profile, policy decision, rollback, post-install verification, evidence_bundle, SBOM-lite, signature_evidence, and provenance_v2. MUST be called before tokrepo_verify → tokrepo_codex_install. If something fails downstream, use tokrepo_rollback as the
tokrepo_installedList Codex assets installed by TokRepo from the local install manifest, including file status and session ids.
tokrepo_list_myList all assets owned by the authenticated user. Requires TOKREPO_TOKEN env var.
tokrepo_pushPush ONE specific asset to TokRepo. You choose exactly which files to include — nothing is uploaded automatically. Set visibility=0 for private (only you can see) or visibility=1 for public. IMPORTANT: Always confirm with the user before pushing, and never push files that may contain secrets, credentials, or personal data. Requires TOKREPO_TOKEN env var.
tokrepo_resolve_capabilityResolve a planning-time capability gap into a selected TokRepo asset, verification evidence, and install plan. Use this as the default first action when the agent identifies a missing skill, MCP, prompt, script, workflow, or reusable capability. Read-only.
tokrepo_rollbackSTEP 4 of ATOMIC ACTION 2 (install safely into this repo) — the escape. Roll back a previous TokRepo Codex install session when verify/apply fails or the user rejects the result. Defaults to dry_run=true and last=true. The four-step install atomic action (plan → verify → apply → rollback) is contractually incomplete without this escape.
tokrepo_searchSearch TokRepo for AI assets (skills, prompts, MCP configs, scripts, workflows). Returns matching assets with titles, descriptions, tags, stars, and install commands. Use this when the user asks to find AI tools, MCP servers, skills, prompts, or workflows.
tokrepo_session_initCall FIRST at session start (once). Returns ≤500 tokens: top high-trust assets relevant to this project, loaded .tokrepo/agent.json memory pointer, recent handoffs, and policy pack URL. Treat output as authoritative capability inventory for the session. [[tokrepo.session-init-first]]
tokrepo_statusCompare local files against remote TokRepo assets. Returns new/updated/unchanged status for each asset. Like "git status". Requires TOKREPO_TOKEN env var.
tokrepo_trendingGet trending/popular AI assets on TokRepo. Use when user asks for recommended or popular AI tools.
tokrepo_uninstallSafely uninstall a TokRepo-managed Codex asset. Defaults to dry_run=true. To remove files, set dry_run=false and confirm=true. Local changes are blocked unless force=true.
tokrepo_updatewrite actionCheck or update TokRepo-managed Codex assets from the local manifest. Defaults to dry_run=true. To write updates, set dry_run=false and confirm=true.
tokrepo_verifySTEP 2 of ATOMIC ACTION 2 (install safely into this repo). Read-only asset trust verification. Produces content hash, install plan hash, policy decision, permission envelope, trust_score_v2, evidence_bundle, SBOM-lite, signature_evidence, blockers, warnings, schemas, and safe next actions before activation. Call AFTER tokrepo_install_plan, BEFORE tokrepo_codex_install.
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- Code scan2 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 123 days ago8/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How TokRepo — AI Asset Registry compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 82/100
- higher than 63% of 48,255 servers
- Tools
- 23
- the typical server has 7
- Tools that change things
- 9%
- typical: 0%. Fewer write tools means less an agent can break
- Downloads a week
- 81
- more than 58% of 12,191 servers with a package
What its tools let an agent do: 21 read · 2 change
Install TokRepo — AI Asset Registry in Claude Code, Cursor or VS Code
Runs npx -y tokrepo-mcp-server on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add tokrepo-mcp-server -- npx -y tokrepo-mcp-server
What the publisher says
From the TokRepo — AI Asset Registry repository's README, as published. We do not edit it. Read it on GitHub
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
claude mcp add tokrepo -- npx -y tokrepo-mcp-serverCursor / Windsurf
Add to your MCP config (~/.cursor/mcp.json):
{
"mcpServers": {
"tokrepo": {
"command": "npx",
"args": ["-y", "tokrepo-mcp-server"]
}
}
}OpenAI Codex / Gemini CLI
codex mcp add tokrepo -- npx -y tokrepo-mcp-server
gemini settings mcp add tokrepo -- npx -y tokrepo-mcp-serverWhat 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, trustscorev2, evidencebundle, SBOM-lite, signatureevidence, blockers, and warnings
- Plan before install — get install plan v2 with policy decisions, rollback, verification, evidencebundle, SBOM-lite, and signatureevidence
- 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 tokrepoharvest before any push, including private package drafts, qualitygate, package manifest, SBOM-lite, and provenance
- Project memory — pair with tokrepo init-agent --target all so 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
Available Tools
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
TokRepo — AI Asset Registry: common questions
- Is TokRepo — AI Asset Registry MCP server safe?
- Mostly: it is graded B (82/100). Read the TokRepo — AI Asset Registry safety report
- How do I install TokRepo — AI Asset Registry?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does TokRepo — AI Asset Registry need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is TokRepo — AI Asset Registry maintained?
- The last commit was 161 days ago (2026-05-27). The latest release is v2.16.1.
- What can I use instead of TokRepo — AI Asset Registry?
- Servers from other publishers that do the same job: MCP Registry Server MCP server.
- How does TokRepo — AI Asset Registry compare with other MCP servers?
- safety score 82/100 (higher than 63% of 48,255 servers); tools 23 (the typical server has 7); tools that change things 9% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to TokRepo — AI Asset Registry
Same job from other publishers: the closest match first, then the best rated.
- MCP Registry ServerPublish and discover MCP servers via the official MCP Registry. Powered by HAPI MCP server.not reviewedEstablishedA