Treering
MCPB · LINUX-X64 · 2 COMPONENTS
A local map of your codebase over time: symbols, callers, subgraphs and structural change.
Available components
Last scanned (11 hours ago)
Scores higher than 87% of MCPB servers
Category Code Search and Documentation
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 & 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 (Apache-2.0).Pass
- Actively maintained (last published 19 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 536 tokens (~89/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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.
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.
- 17 Oct 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.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 50. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +6
- Stability: unverified → 0.43 ▲ functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 41
First indexed and scored.
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 17 Oct 2026 · Analysed mcpb/https://github.com/RedholeTechnologies/Treering/releases/download/v0.7.1/treering-linux-x64.mcpb
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 →
callers_of ~83
The types that call this one, rolled up to type level. The «who» of a reference is inferred from position, so method level is unreliable.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string|null | – | Which imported project to ask: its name or id, as list_projects gives them. Empty means the most recently imported one. |
| type | string | yes | Type name. Exact match. |
No output schema declared.
No examples provided.
changed_since ~118
Dependencies that appeared or went away between two snapshots. Answers «how has the structure moved since the last release» in one call.
| Name | Type | Req | Description |
|---|---|---|---|
| fromOrd | integer | yes | The snapshot ord to measure from. |
| granularity | string | – | One of module, namespace, type. Default module. |
| project | string|null | – | Which imported project to ask: its name or id, as list_projects gives them. Empty means the most recently imported one. |
| toOrd | integer|null | – | The snapshot ord to compare against. Empty means the latest. |
No output schema declared.
No examples provided.
find_symbol ~86
Find a symbol by name. Looks at types, methods, namespaces and packages alike.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum results. Default 20. |
| name | string | yes | The name to look for. Substring match. |
| project | string|null | – | Which imported project to ask: its name or id, as list_projects gives them. Empty means the most recently imported one. |
No output schema declared.
No examples provided.
list_projects ~40
The repositories imported into Treering: name, id, languages, where they are and when they were imported. Every other tool takes one of these as project.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
snapshots ~55
The snapshots on file. Pick the ord to hand to changed_since from here.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string|null | – | Which imported project to ask: its name or id, as list_projects gives them. Empty means the most recently imported one. |
No output schema declared.
No examples provided.
subgraph ~154
The subgraph around one point. Budgets apply (2,000 nodes, degree 50) and whatever was cut comes back under truncated. Narrow the seed and ask again if needed.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | integer | – | How many hops. Default 1. |
| granularity | string | – | One of module, namespace, type. Default type. |
| ownOnly | boolean | – | Leave out what this repo did not write - system and package types. Default false. |
| project | string|null | – | Which imported project to ask: its name or id, as list_projects gives them. Empty means the most recently imported one. |
| seed | string|null | – | Seed symbol name. Leave it empty to see the whole level. |
No output schema declared.
No examples provided.
How do I install the Treering MCP server?
Treering 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, 5bd87749b76cee3603301220de078694dbd38eeb07c7f2a4f33de553639a5882; the commands to do that are on this page. If it does not match, do not open it.
mcpb · linux-x64
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
5bd87749b76cee3603301220de078694dbd38eeb07c7f2a4f33de553639a5882
macOS / Linux
echo "5bd87749b76cee3603301220de078694dbd38eeb07c7f2a4f33de553639a5882 treering-linux-x64.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\treering-linux-x64.mcpb).Hash -eq "5bd87749b76cee3603301220de078694dbd38eeb07c7f2a4f33de553639a5882"
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 Treering MCP server?
Treering is an MCP server listed in the public MCP registry as io.github.RedholeTechnologies/treering. A local map of your codebase over time: symbols, callers, subgraphs and structural change. This page covers its MCPB bundle (https://github.com/RedholeTechnologies/Treering/releases/download/v0.7.1/treering-linux-x64.mcpb).
Is the Treering MCP server safe to use?
Treering scores 51 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 Treering MCP server expose?
Treering exposes 6 tools: find_symbol, callers_of, snapshots, subgraph, changed_since, list_projects. Their descriptions and schemas cost roughly 536 tokens of context every time the server is loaded.
What licence is the Treering MCP server under?
Treering declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.