TokRepo — AI Asset Registry
NPM · TOKREPO-MCP-SERVER · SCANNED SEP 20
TokRepo MCP: tokrepo_discover, tokrepo_verify, tokrepo_install_plan for reusable AI assets.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 116 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2660 tokens (~156/item across 17 items; 17 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the TokRepo — AI Asset Registry MCP server?
TokRepo — AI Asset Registry runs locally as an npm package, launched with npx -y tokrepo-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · tokrepo-mcp-server
claude mcp add henu-wang-tokrepo-mcp-server -- npx -y tokrepo-mcp-server
{
"mcpServers": {
"henu-wang-tokrepo-mcp-server": {
"command": "npx",
"args": [
"-y",
"tokrepo-mcp-server"
]
}
}
} {
"servers": {
"henu-wang-tokrepo-mcp-server": {
"command": "npx",
"args": [
"-y",
"tokrepo-mcp-server"
]
}
}
} codex mcp add henu-wang-tokrepo-mcp-server -- npx -y tokrepo-mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"henu-wang-tokrepo-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"tokrepo-mcp-server"
],
"enabled": true
}
}
} openclaw mcp add henu-wang-tokrepo-mcp-server --command npx --arg -y --arg tokrepo-mcp-server
mcp_servers:
henu-wang-tokrepo-mcp-server:
command: "npx"
args: ["-y", "tokrepo-mcp-server"] {
"McpServers": {
"henu-wang-tokrepo-mcp-server": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"tokrepo-mcp-server"
]
}
}
} assistant mcp add henu-wang-tokrepo-mcp-server -t stdio -c npx -a -y tokrepo-mcp-server
{
"mcpServers": {
"henu-wang-tokrepo-mcp-server": {
"command": "npx",
"args": [
"-y",
"tokrepo-mcp-server"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −2
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- Security disclosure: fail → unverified ▼ functional
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −2
- Stability: pass → 0.83 functional
- 9 Sept 26 0
- Stability: 0.97 → pass security
- Security disclosure: unverified → fail ▼ functional
- 8 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/tokrepo-mcp-server@2.16.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
tokrepo_codex_install ~214
STEP 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).
| Name | Type | Req | Description |
|---|---|---|---|
| approve_risk | boolean | – | Required to activate assets whose policy decision is confirm or stage_only. Prefer stage=true for high-risk assets. |
| confirm | boolean | – | Required when dry_run=false to prevent accidental writes. |
| dry_run | boolean | – | When true, return the plan only and do not write files. Default true. |
| stage | boolean | – | Write only a staged install plan under ~/.codex/tokrepo/staged instead of activating a skill. |
| uuid | string | yes | Asset UUID, workflow URL, or search term accepted by the TokRepo CLI |
No output schema declared.
No examples provided.
tokrepo_detail ~46
Get full details of a TokRepo asset by UUID, including description, content, tags, install instructions, and metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| uuid | string | yes | Asset UUID (from search results) |
No output schema declared.
No examples provided.
tokrepo_discover ~188
Planning-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]]
| Name | Type | Req | Description |
|---|---|---|---|
| constraints | object | – | Optional constraints such as kind, policy, risk, language, prefer_verified, or must_not_modify_files. |
| environment | object | – | Optional local environment signals, such as project_type, frameworks, language, can_run_shell, can_write_files, or browser_available. |
| limit | number | – | Max candidates (default 6, max 10) |
| target | string | – | Optional agent/runtime target. Use "any" or "all" for generic cross-agent discovery. |
| task | string | yes | The user goal, subtask, or capability gap the agent is planning for. |
No output schema declared.
No examples provided.
tokrepo_edges ~157
Read 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.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | out = this asset → other assets (deps); in = other assets → this asset (depended-on); both (default). |
| slug | string | – | Asset slug. Either uuid or slug is required. |
| types | string | – | Optional comma-separated edge_type filter, e.g. "requires,co_used". Omit for all types. |
| uuid | string | – | Asset UUID. Either uuid or slug is required. |
No output schema declared.
No examples provided.
tokrepo_find_for_task ~226
ATOMIC 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 planning-time capability scan use tokrepo_discover; for the canonical find→install→harvest lifecycle this is the find entry point.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | – | Optional agent identifier (claude_code, codex, cursor, cline, gemini_cli, copilot, windsurf, roo, openhands). |
| limit | number | – | Max candidates (default 3, max 10). |
| repo_context | object | – | Optional repo signals: language, framework, existing_assets[]. |
| task | string | yes | Free-text task description, e.g. "add Stripe webhook handler with idempotency". |
No output schema declared.
No examples provided.
tokrepo_handoff_plan ~107
Inspect 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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max candidates to return (default 12, max 30). |
| paths | array | – | Optional explicit local paths to inspect. Omit to scan common reusable agent asset files in the current project. |
No output schema declared.
No examples provided.
tokrepo_harvest ~171
ATOMIC 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 leaves valuable per-session work stranded; this is how the agent contributes back to the find pool.
| Name | Type | Req | Description |
|---|---|---|---|
| changed | boolean | – | When true, inspect git-changed files from the current repository. |
| limit | number | – | Max drafts to return (default 12, max 30). |
| paths | array | – | Optional explicit local paths to inspect. Omit to scan common reusable agent asset files. |
No output schema declared.
No examples provided.
tokrepo_install_plan ~150
STEP 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 escape.
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | – | Install target adapter. Codex is native; other adapters may return planned or staged contracts as they become available. |
| uuid | string | yes | Asset UUID, workflow URL slug, or workflow UUID from search/detail results |
No output schema declared.
No examples provided.
tokrepo_installed ~31
List Codex assets installed by TokRepo from the local install manifest, including file status and session ids.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
tokrepo_push ~194
Push 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.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Optional description |
| files | array | yes | Only the specific files for THIS asset — not all project files. Each file you list will be uploaded. |
| tags | array | – | Optional tags (e.g. ["coding", "agent"]) |
| title | string | yes | Asset title (descriptive name for this specific asset) |
| visibility | number | – | 0 = private (only visible to you, safe default for personal assets), 1 = public (visible to everyone). When unsure, default to 0 (private). |
No output schema declared.
No examples provided.
tokrepo_resolve_capability ~268
Resolve 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.
| Name | Type | Req | Description |
|---|---|---|---|
| constraints | object | – | Optional constraints such as kind, policy, risk, language, prefer_verified, or must_not_modify_files. |
| environment | object | – | Optional local environment signals, such as project_type, frameworks, language, can_run_shell, can_write_files, or browser_available. |
| kind | string | – | Optional asset kind preference, e.g. skill, prompt, knowledge, mcp_config, script, workflow. |
| limit | number | – | Max discovery candidates (default 6, max 10). |
| min_fit | number | – | Minimum fit score threshold before recommending direct use. Default 70. |
| min_trust | number | – | Minimum trust_score_v2 threshold before recommending direct use. Default 70. |
| policy | string | – | Optional install policy preference. |
| target | string | – | Optional agent/runtime target. Use "any" or "all" for generic cross-agent resolution. |
| task | string | yes | The user goal, subtask, or capability gap the agent needs to solve. |
No output schema declared.
No examples provided.
tokrepo_rollback ~172
STEP 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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | Required when dry_run=false to prevent accidental deletes. |
| dry_run | boolean | – | When true, return the rollback plan without deleting files. Default true. |
| force | boolean | – | Allow rollback when local files changed since installation. |
| last | boolean | – | Use the latest install/stage session. Default true. |
| session_id | string | – | Session id to roll back. Omit when last=true. |
No output schema declared.
No examples provided.
tokrepo_search ~205
Search 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.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | Optional asset kind filter, e.g. skill, prompt, knowledge, mcp_config, script |
| limit | number | – | Max results (default 10, max 20) |
| policy | string | – | Optional Codex install policy filter. |
| query | string | yes | Search keywords (e.g. "cursor rules", "mcp database", "claude skill code review") |
| tag | string | – | Optional tag filter: agent, coding, efficiency, cost-saving, methodology, data-analysis, writing, marketing, learning, research |
| target | string | – | Optional agent target filter. Use "any", "all", or omit it for generic discovery. |
No output schema declared.
No examples provided.
tokrepo_session_init ~133
Call 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]]
| Name | Type | Req | Description |
|---|---|---|---|
| compact | boolean | – | Return ultra-compact (≤50 tok per item) per-candidate response. Default true. |
| project_hint | string | – | Optional project signal (path basename, package.json name, or repo description) to bias the asset inventory. |
| target | string | – | Optional agent runtime target. |
No output schema declared.
No examples provided.
tokrepo_uninstall ~115
Safely 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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | Required when dry_run=false to prevent accidental deletes. |
| dry_run | boolean | – | When true, return the removal plan without deleting files. Default true. |
| force | boolean | – | Allow removal when local files changed since installation. |
| uuid | string | yes | Installed asset UUID, UUID prefix, or title. |
No output schema declared.
No examples provided.
tokrepo_update ~122
Check 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.
| Name | Type | Req | Description |
|---|---|---|---|
| approve_risk | boolean | – | Allow updates whose install policy requires explicit risk approval. |
| confirm | boolean | – | Required when dry_run=false to prevent accidental writes. |
| dry_run | boolean | – | When true, check for updates and return the plan without writing files. Default true. |
| stage | boolean | – | Stage risky updates under ~/.codex/tokrepo/staged instead of activating them. |
No output schema declared.
No examples provided.
tokrepo_verify ~161
STEP 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.
| Name | Type | Req | Description |
|---|---|---|---|
| offline | boolean | – | Use the bundled offline fixture. Intended for agent/toolchain self-tests. |
| strict | boolean | – | When true, warnings fail the verification report. |
| target | string | – | Verification target adapter. |
| uuid | string | yes | Asset UUID, workflow URL slug, or workflow UUID from search/detail results. Ignored when offline=true. |
No output schema declared.
No examples provided.
What is the TokRepo — AI Asset Registry MCP server?
TokRepo — AI Asset Registry is an MCP server listed in the public MCP registry as io.github.henu-wang/tokrepo-mcp-server. TokRepo MCP: tokrepo_discover, tokrepo_verify, tokrepo_install_plan for reusable AI assets. This page covers its npm package (tokrepo-mcp-server).
Is the TokRepo — AI Asset Registry MCP server safe to use?
TokRepo — AI Asset Registry scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the TokRepo — AI Asset Registry MCP server expose?
TokRepo — AI Asset Registry exposes 17 tools: tokrepo_session_init, tokrepo_find_for_task, tokrepo_discover, tokrepo_resolve_capability, tokrepo_search, and 12 more. Their descriptions and schemas cost roughly 2,660 tokens of context every time the server is loaded.
Is the TokRepo — AI Asset Registry MCP server still maintained?
TokRepo — AI Asset Registry is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the TokRepo — AI Asset Registry MCP server under?
TokRepo — AI Asset Registry declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.