# Treering (mcpb · linux-x64)

A local map of your codebase over time: symbols, callers, subgraphs and structural change.

- Trust score: 51/100 (low)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- mcpb · `linux-x64`: 51/100 (this document), [markdown](https://verifymcp.io/servers/redholetechnologies-treering/https-github-com-redholetechnologies-treering-releases-download-v0-7-0-treering.md), [page](https://verifymcp.io/servers/redholetechnologies-treering/https-github-com-redholetechnologies-treering-releases-download-v0-7-0-treering)
- mcpb · `win-x64`: 9/100, [markdown](https://verifymcp.io/servers/redholetechnologies-treering/https-github-com-redholetechnologies-treering-releases-download-v0-7-0-treering-2.md), [page](https://verifymcp.io/servers/redholetechnologies-treering/https-github-com-redholetechnologies-treering-releases-download-v0-7-0-treering-2)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/RedholeTechnologies/Treering/releases/download/v0.7.1/treering-linux-x64.mcpb`
- Transport: `stdio`
- SHA-256: `5bd87749b76cee3603301220de078694dbd38eeb07c7f2a4f33de553639a5882`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-17.

- **Supply Chain Security**: 0/100
  - 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 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-script risk not yet assessed.
  - 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).
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 19 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 536 tokens (~89/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 67/100
  - Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**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.

## Install

### 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.

- Download bundle: `https://github.com/RedholeTechnologies/Treering/releases/download/v0.7.1/treering-linux-x64.mcpb`
- SHA-256: `5bd87749b76cee3603301220de078694dbd38eeb07c7f2a4f33de553639a5882`

### Verify on macOS / Linux

```bash
echo "5bd87749b76cee3603301220de078694dbd38eeb07c7f2a4f33de553639a5882  treering-linux-x64.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\treering-linux-x64.mcpb).Hash -eq "5bd87749b76cee3603301220de078694dbd38eeb07c7f2a4f33de553639a5882"
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-17 (score 51, +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.

### 2026-10-15 (score 50, +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.

### 2026-10-13 (score 49, +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.

### 2026-10-12 (score 48, +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.

### 2026-10-10 (score 47, +6)

- [functional improvement] Stability: unverified → 0.43

### 2026-09-28 (score 41, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 41)

First indexed and scored.

## MCP tools (6)

### `find_symbol` (~86 tokens)

Find a symbol by name. Looks at types, methods, namespaces and packages alike.

Input parameters:

- `limit` (integer): Maximum results. Default 20.
- `name` (string, required): 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.

### `callers_of` (~83 tokens)

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.

Input parameters:

- `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, required): Type name. Exact match.

### `snapshots` (~55 tokens)

The snapshots on file. Pick the ord to hand to changed_since from here.

Input parameters:

- `project` (string|null): Which imported project to ask: its name or id, as list_projects gives them. Empty means the most recently imported one.

### `subgraph` (~154 tokens)

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.

Input parameters:

- `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.

### `changed_since` (~118 tokens)

Dependencies that appeared or went away between two snapshots. Answers «how has the structure moved since the last release» in one call.

Input parameters:

- `fromOrd` (integer, required): 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.

### `list_projects` (~40 tokens)

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.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/redholetechnologies-treering/https-github-com-redholetechnologies-treering-releases-download-v0-7-0-treering#diagnostics

## Score history

- 2026-10-17: 51
- 2026-10-16: 50
- 2026-10-15: 50
- 2026-10-14: 49
- 2026-10-13: 49
- 2026-10-12: 48
- 2026-10-10: 47
- 2026-10-04: 41
- 2026-10-03: 41
- 2026-10-02: 41
- 2026-10-01: 41
- 2026-09-30: 41
- 2026-09-29: 41
- 2026-09-28: 41
- 2026-09-27: 41

## Common questions

### 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.

## Links

- Repository: https://github.com/RedholeTechnologies/Treering
- Changelog RSS feed: https://verifymcp.io/servers/redholetechnologies-treering/https-github-com-redholetechnologies-treering-releases-download-v0-7-0-treering.xml
- Changelog JSON feed: https://verifymcp.io/servers/redholetechnologies-treering/https-github-com-redholetechnologies-treering-releases-download-v0-7-0-treering.json
- HTML version of this page: https://verifymcp.io/servers/redholetechnologies-treering/https-github-com-redholetechnologies-treering-releases-download-v0-7-0-treering