# UGT: Use the GitHub Thing (mcpb · linux-x64)

Get open-source GitHub projects running on your computer, with your AI app

- Trust score: 39/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- remote · `mcp.usegithubthing.com`: 73/100, [markdown](https://verifymcp.io/servers/com-usegithubthing-ugt/mcp.md), [page](https://verifymcp.io/servers/com-usegithubthing-ugt/mcp)
- mcpb · `osx-x64`: 10/100, [markdown](https://verifymcp.io/servers/com-usegithubthing-ugt/ugt-mcp-darwin-amd64.md), [page](https://verifymcp.io/servers/com-usegithubthing-ugt/ugt-mcp-darwin-amd64)
- mcpb · `osx-arm64`: 10/100, [markdown](https://verifymcp.io/servers/com-usegithubthing-ugt/ugt-mcp-darwin-arm64.md), [page](https://verifymcp.io/servers/com-usegithubthing-ugt/ugt-mcp-darwin-arm64)
- mcpb · `linux-x64`: 39/100 (this document), [markdown](https://verifymcp.io/servers/com-usegithubthing-ugt/ugt-mcp-linux-amd64.md), [page](https://verifymcp.io/servers/com-usegithubthing-ugt/ugt-mcp-linux-amd64)
- mcpb · `linux-arm64`: 10/100, [markdown](https://verifymcp.io/servers/com-usegithubthing-ugt/ugt-mcp-linux-arm64.md), [page](https://verifymcp.io/servers/com-usegithubthing-ugt/ugt-mcp-linux-arm64)
- mcpb · `win-x64`: 10/100, [markdown](https://verifymcp.io/servers/com-usegithubthing-ugt/ugt-mcp-windows-amd64.md), [page](https://verifymcp.io/servers/com-usegithubthing-ugt/ugt-mcp-windows-amd64)
- mcpb · `win-arm64`: 10/100, [markdown](https://verifymcp.io/servers/com-usegithubthing-ugt/ugt-mcp-windows-arm64.md), [page](https://verifymcp.io/servers/com-usegithubthing-ugt/ugt-mcp-windows-arm64)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/auscaster/ugt/releases/download/v0.2.2/ugt-mcp-linux-amd64.mcpb`
- Version: `0.2.2`
- Transport: `stdio`
- SHA-256: `2b02a64c5eb224254901879e467b1cc3baf71b9a598f00512561df554c19ee15`

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

- **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**: 42/100
  - Source repository is publicly reachable at the declared URL.
  - Build provenance not yet verified.
  - Clear OSI-approved license (Apache-2.0).
  - Maintenance history not yet determined.
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2082 tokens (~148/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 15 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 UGT: Use the GitHub Thing MCP server?

UGT: Use the GitHub Thing 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, 2b02a64c5eb224254901879e467b1cc3baf71b9a598f00512561df554c19ee15; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/auscaster/ugt/releases/download/v0.2.2/ugt-mcp-linux-amd64.mcpb`
- SHA-256: `2b02a64c5eb224254901879e467b1cc3baf71b9a598f00512561df554c19ee15`

### Verify on macOS / Linux

```bash
echo "2b02a64c5eb224254901879e467b1cc3baf71b9a598f00512561df554c19ee15  ugt-mcp-linux-amd64.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\ugt-mcp-linux-amd64.mcpb).Hash -eq "2b02a64c5eb224254901879e467b1cc3baf71b9a598f00512561df554c19ee15"
```

## 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-11-04 (score 39, 0)

- [security regression] Provenance: fail → unverified
- [functional regression] Maintenance: pass → unverified
- [functional improvement] Stability: unverified → 0.03
- [functional] Destructive annotations: All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
- [functional] Package version: 0.2.1 → 0.2.2

### 2026-11-03 (score 39)

First indexed and scored.

## MCP tools (14)

### `ugt_delete_data` (~84 tokens)

Delete a recipe's saved data

Delete a recipe's saved data (its named volumes) for good. Only after the user has agreed in so many words; set user_agreed to true to say they did.

Input parameters:

- `recipe` (string, required): the recipe, as owner/repo/task
- `user_agreed` (boolean, required): true only when the user has agreed to deleting the saved data for good

Output parameters:

- `done` (null|array)
- `kept` (null|array)
- `missing` (boolean)
- `recipe` (string)

### `ugt_doctor` (~52 tokens)

Check this computer

Check this machine for UGT: the runtime, the engine and its memory, and the network it needs, each with the exact fix. Call it when a run or verification fails for reasons outside the recipe.

Output parameters:

- `checks` (null|array)
- `ok` (boolean)
- `runtime` (string)

### `ugt_exec` (~123 tokens)

Run a command in a recipe

Run a command inside one of a recipe's services, in the workspace and with the image of its last verification, to look at the real environment: the outputs it made, what the image holds, what a check sees. Returns the exit code and the output's last 20 KB.

Input parameters:

- `command` (null|array, required): the program and its arguments, such as ["sh", "-c", "ls -la outputs"]
- `dir` (string, required): the recipe folder
- `service` (string, required): the service to run in, such as task or check

### `ugt_find` (~91 tokens)

Find recipes

Find the recipes UGT has for a GitHub project, or for words describing a task. Call it first whenever the user says "Use the GitHub Thing" or gives a GitHub repository with a job. No recipe is a normal answer: the result says how to make one.

Input parameters:

- `query` (string, required): a GitHub project as owner/repo or its link, or words describing the task

Output parameters:

- `next` (null|array)
- `project` (string)
- `query` (string)
- `recipes` (null|array)

### `ugt_list` (~35 tokens)

List what UGT holds

List what UGT holds on this machine, by recipe: whether it is running, its images, saved data and results folder.

Output parameters:

- `recipes` (null|array)

### `ugt_login` (~67 tokens)

Sign in to GitHub

Sign the user in to GitHub, which sharing a recipe needs. Its progress gives a code for the user to enter at the address it names, in their own browser; the job finishes when they approve it. The login goes to the system's secret store; you never see it.

### `ugt_new` (~201 tokens)

Start a new recipe

Start a recipe for a GitHub project and task when ugt_find has none. It adopts the project's own Compose file when there is one, otherwise writes a blank recipe whose Dockerfile builds the pinned commit. Returns the recipe's folder and files, what to write next, and anything to resolve.

Input parameters:

- `blank` (boolean): start blank even when the project ships a Compose file
- `from` (string): a Compose file to adopt: a path in the project, or a github.com link to a file in any repository
- `kind` (string): job (runs to completion and writes files) or service (keeps running); inferred when left out
- `project` (string, required): the GitHub project, as owner/repo or its link
- `task` (string, required): a slug naming what the recipe produces, such as subtitles or markdown
- `what` (string): the task in plain words, as the user would say it

### `ugt_remove` (~67 tokens)

Remove a recipe

Remove what UGT created for a recipe: its containers, images and workspaces. Its saved data and the results in the UGT folder stay.

Input parameters:

- `recipe` (string, required): the recipe, as owner/repo/task, or owner/repo when UGT holds one of its recipes

Output parameters:

- `done` (null|array)
- `kept` (null|array)
- `missing` (boolean)
- `recipe` (string)

### `ugt_run` (~277 tokens)

Run a GitHub project

Get a GitHub project working for the user with its recipe: it builds or pulls what it needs and proves it with its check. A job does the user's task on their files and delivers the results to their UGT folder. A service keeps running and returns its pages and endpoints, at addresses that stay the same. Commands the recipe provides go on the user's PATH, and the tools of its MCP servers join UGT's own here, at once. A recipe that needs a secret, or one from outside the catalogue that reaches the computer itself, first asks the user in UGT's own dialog. Returns the result, or a job for ugt_status.

Input parameters:

- `inputs` (null|array): the user's files, as paths or as NAME=PATH; a bare file name is looked for in the UGT folder
- `project` (string, required): the GitHub project, as owner/repo or its link
- `settings` (object): value settings by name; never secrets
- `task` (string): the recipe's task, when the project has several
- `texts` (object): inputs you write yourself, by input name, such as a script or a list of URLs; ugt_find lists each recipe's inputs
- `to` (string): a folder for the results, when the user names one

### `ugt_setup` (~99 tokens)

Set up UGT's engine

Set this machine up to run recipes in UGT's own Linux engine: in WSL on Windows, and UGT's own Linux machine on an Apple silicon Mac and on Linux; an Intel Mac uses the engine already there. Installing WSL needs admin approval and may restart Windows: set allow_admin only once the user has agreed to that.

Input parameters:

- `allow_admin` (boolean): true only when the user agreed to admin approval and a possible restart

### `ugt_status` (~89 tokens)

Check on a job

Report a job started by ugt_new, ugt_verify, ugt_run or ugt_exec: its state, progress and, once finished, its result. Waits up to wait_seconds (default 20) for it to finish.

Input parameters:

- `job` (string, required): the job ID
- `wait_seconds` (integer): how long to wait for it to finish, up to 50

### `ugt_stop` (~48 tokens)

Stop a recipe's services

Stop a recipe's running services, keeping everything else.

Input parameters:

- `recipe` (string, required): the recipe, as owner/repo/task, or owner/repo when UGT holds one of its recipes

Output parameters:

- `done` (null|array)
- `kept` (null|array)
- `missing` (boolean)
- `recipe` (string)

### `ugt_submit` (~141 tokens)

Share a recipe

Share a recipe with the catalogue when the user asks to: it verifies the recipe (or uses a passing verification of the same revision), refuses anything personal in it (the user's paths, secrets, input files, keys) with the file and line, and opens a pull request with the user's GitHub login (ugt_login signs them in). Try dry_run first to show the user what would be sent.

Input parameters:

- `agent` (string): who made and verified it, for the pull request, such as your name and model
- `dir` (string, required): the recipe folder
- `dry_run` (boolean): show what would be proposed, and change nothing

### `ugt_verify` (~166 tokens)

Verify a recipe

Verify a recipe folder the way every machine runs it: build, then the sample, task, check and sample-check services, then the check-strength test, which fails any check that accepts broken outputs. Pass edited files to write them into the folder first, when it is one ugt_new made. A failed report names the step, its log and a diagnosis. from resumes the last verification at a step, with its image, to iterate quickly.

Input parameters:

- `dir` (string, required): the recipe folder, as ugt_new returned it
- `files` (object): files to write into the folder first, by path relative to it, with their full new contents
- `from` (string): resume the last verification at sample, task, check or sample-check, with its image

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/com-usegithubthing-ugt/ugt-mcp-linux-amd64#diagnostics

## Score history

- 2026-11-04: 39
- 2026-11-03: 39

## Common questions

### What is the UGT: Use the GitHub Thing MCP server?

UGT: Use the GitHub Thing is an MCP server listed in the public MCP registry as com.usegithubthing/ugt. Get open-source GitHub projects running on your computer, with your AI app. This page covers its MCPB bundle (https://github.com/auscaster/ugt/releases/download/v0.2.2/ugt-mcp-linux-amd64.mcpb).

### Is the UGT: Use the GitHub Thing MCP server safe to use?

UGT: Use the GitHub Thing scores 39 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 UGT: Use the GitHub Thing MCP server expose?

UGT: Use the GitHub Thing exposes 14 tools: ugt_delete_data, ugt_doctor, ugt_exec, ugt_find, ugt_list, and 9 more. Their descriptions and schemas cost roughly 1,540 tokens of context every time the server is loaded.

### What licence is the UGT: Use the GitHub Thing MCP server under?

UGT: Use the GitHub Thing 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/auscaster/ugt
- Website: https://usegithubthing.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-usegithubthing-ugt/ugt-mcp-linux-amd64.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-usegithubthing-ugt/ugt-mcp-linux-amd64.json
- HTML version of this page: https://verifymcp.io/servers/com-usegithubthing-ugt/ugt-mcp-linux-amd64