dotrepo
MCPB · DOTREPO-MCP-2.0.0-RC.2.MCPB
Preview repository facts with evidence. Choose your release channel at dotrepo.org/docs.
Available components
Last scanned (10 hours ago)
Scores higher than 77% of MCPB servers
Category Version Control
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 Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
Provenance & Transparency19
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- 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 7 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 639 tokens (~71/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 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
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (12)
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (4)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain Security (scores 0 for this)No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
- Known CVEs in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
- Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
- Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 −5
- Source repository: pass → fail ▼ security
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 −6
- Stability: pass → 0.63 functional
- 29 Oct 26 0
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Security disclosure: fail → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Package version: 2.0.0-rc.1 → 2.0.0-rc.2 functional
- 27 Oct 26 +1
- Stability: 0.97 → pass security
- Package version: 1.0.3 → 2.0.0-rc.1 functional
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Analysed mcpb/https://github.com/maxwellsantoro/dotrepo/releases/download/v2.0.0-rc.2/dotrepo-mcp-2.0.0-rc.2.mcpb@2.0.0-rc.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
dotrepo.adoption_status Inspect native adoption readiness ~48
Summarize native-record readiness for validation, claim identity, CI onboarding, and managed-surface drift.
| Name | Type | Req | Description |
|---|---|---|---|
| root | string | – | Repository root containing the native .repo to inspect. |
No output schema declared.
No examples provided.
dotrepo.claim_inspect Inspect maintainer claim ~72
Inspect one maintainer-claim directory and return current state, target context, derived handoff, and ordered event history.
| Name | Type | Req | Description |
|---|---|---|---|
| claimPath | string | yes | Claim directory relative to root or an absolute path. |
| root | string | – | Index root containing repos/<host>/<owner>/<repo>/claims/... |
No output schema declared.
No examples provided.
dotrepo.generate_check Preview generated outputs ~42
Check dotrepo-managed outputs and report which generated files are stale without writing files.
| Name | Type | Req | Description |
|---|---|---|---|
| root | string | – | Repository root containing .repo or record.toml. |
No output schema declared.
No examples provided.
dotrepo.import_preview Preview imported manifest ~68
Preview a native or overlay import derived from README.md, CODEOWNERS, and SECURITY.md.
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | – | Import mode; defaults to native. |
| root | string | – | Repository root to import from. |
| source | string | – | Absolute repository URL required for overlay imports. |
No output schema declared.
No examples provided.
dotrepo.import_write Write imported manifest ~85
Write a native .repo or overlay record.toml plus evidence.md using the same import pipeline as import_preview.
| Name | Type | Req | Description |
|---|---|---|---|
| force | boolean | – | Overwrite existing import artifacts when true. |
| mode | string | – | Import mode; defaults to native. |
| root | string | – | Repository root to import from. |
| source | string | – | Absolute repository URL required for overlay imports. |
No output schema declared.
No examples provided.
dotrepo.lookup Lookup hosted public repository ~136
Resolve a repository URL or identity against the hosted public surface and return summary, trust, and query entrypoints without cloning.
| Name | Type | Req | Description |
|---|---|---|---|
| baseUrl | string | – | Hosted public origin; defaults to https://dotrepo.org. |
| host | string | – | Repository host when resolving by identity. |
| owner | string | – | Repository owner when resolving by identity. |
| path | string | – | Optional dot-path to resolve immediately through the hosted query route. |
| repo | string | – | Repository name when resolving by identity. |
| repositoryUrl | string | – | Repository URL such as https://github.com/owner/repo or a hosted dotrepo repository URL. |
No output schema declared.
No examples provided.
dotrepo.query Query manifest path ~60
Query a dot-path such as repo.name or record.trust.provenance and return the value with record trust context.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Dot-path to query. |
| root | string | – | Repository root containing .repo or record.toml. |
No output schema declared.
No examples provided.
dotrepo.trust Read trust metadata ~45
Return record status, mode, source, and trust metadata for the manifest at the given root.
| Name | Type | Req | Description |
|---|---|---|---|
| root | string | – | Repository root containing .repo or record.toml. |
No output schema declared.
No examples provided.
dotrepo.validate Validate dotrepo record ~39
Validate the manifest at the given repository root and return trust-aware diagnostics.
| Name | Type | Req | Description |
|---|---|---|---|
| root | string | – | Repository root containing .repo or record.toml. |
No output schema declared.
No examples provided.
How do I install the dotrepo MCP server?
dotrepo ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 7123ebca346d1f53f960bdefc5ccb98d70ca66d6015454b61bd35ce294d75f3d; the commands to do that are on this page. If it does not match, do not open it.
mcpb · dotrepo-mcp-2.0.0-rc.2.mcpb
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
7123ebca346d1f53f960bdefc5ccb98d70ca66d6015454b61bd35ce294d75f3d
macOS / Linux
echo "7123ebca346d1f53f960bdefc5ccb98d70ca66d6015454b61bd35ce294d75f3d dotrepo-mcp-2.0.0-rc.2.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\dotrepo-mcp-2.0.0-rc.2.mcpb).Hash -eq "7123ebca346d1f53f960bdefc5ccb98d70ca66d6015454b61bd35ce294d75f3d"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
What is the dotrepo MCP server?
dotrepo is an MCP server listed in the public MCP registry as io.github.maxwellsantoro/dotrepo. Preview repository facts with evidence. Choose your release channel at dotrepo.org/docs. This page covers its MCPB bundle (https://github.com/maxwellsantoro/dotrepo/releases/download/v2.0.0-rc.2/dotrepo-mcp-2.0.0-rc.2.mcpb).
Is the dotrepo MCP server safe to use?
dotrepo scores 47 out of 100 on VerifyMCP. 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 dotrepo MCP server expose?
dotrepo exposes 9 tools: dotrepo.validate, dotrepo.query, dotrepo.trust, dotrepo.adoption_status, dotrepo.lookup, and 4 more. Their descriptions and schemas cost roughly 595 tokens of context every time the server is loaded.
What licence is the dotrepo MCP server under?
dotrepo declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the dotrepo MCP server?
VerifyMCP ran 12 checks on dotrepo, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about dotrepo: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.