UGT: Use the GitHub Thing
MCPB · LINUX-X64 · 7 COMPONENTS
Get open-source GitHub projects running on your computer, with your AI app
Last scanned (1 day ago)
Scores higher than 72% of MCPB servers
Category Developer Tools
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 & Transparency42
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Build provenance not yet verified. View diagnostics → Unverified
- Clear OSI-approved license (Apache-2.0).Pass
- Maintenance history not yet determined.Unverified
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 15 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.
- 4 Nov 26 0
- Provenance: fail → unverified ▼ security
- Maintenance: pass → unverified ▼ functional
- 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 functional
- 3 Nov 26 39
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 4 Nov 2026 · Analysed mcpb/https://github.com/auscaster/ugt/releases/download/v0.2.2/ugt-mcp-linux-amd64.mcpb@0.2.2
Provenance Inconclusive
We could not complete the check, so nothing is claimed either way. This is a gap on our side, not a finding about the package.
| Result | Inconclusive |
|---|---|
| Ecosystem | mcpb |
| Reason | Attestation not fetched |
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 →
ugt_delete_data Delete a recipe's saved data ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| recipe | string | yes | the recipe, as owner/repo/task |
| user_agreed | boolean | yes | true only when the user has agreed to deleting the saved data for good |
| Name | Type | Req | Description |
|---|---|---|---|
| done | null|array | yes | – |
| kept | null|array | – | – |
| missing | boolean | – | – |
| recipe | string | yes | – |
No examples provided.
ugt_doctor Check this computer ~52
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| checks | null|array | yes | – |
| ok | boolean | yes | – |
| runtime | string | yes | – |
No examples provided.
ugt_exec Run a command in a recipe ~123
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.
| Name | Type | Req | Description |
|---|---|---|---|
| command | null|array | yes | the program and its arguments, such as ["sh", "-c", "ls -la outputs"] |
| dir | string | yes | the recipe folder |
| service | string | yes | the service to run in, such as task or check |
Structured output declared, but exposes no named fields.
No examples provided.
ugt_find Find recipes ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | a GitHub project as owner/repo or its link, or words describing the task |
| Name | Type | Req | Description |
|---|---|---|---|
| next | null|array | yes | – |
| project | string | – | – |
| query | string | yes | – |
| recipes | null|array | yes | – |
No examples provided.
ugt_list List what UGT holds ~35
List what UGT holds on this machine, by recipe: whether it is running, its images, saved data and results folder.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| recipes | null|array | yes | – |
No examples provided.
ugt_login Sign in to GitHub ~67
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.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
ugt_new Start a new recipe ~201
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | the GitHub project, as owner/repo or its link |
| task | string | yes | 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 |
Structured output declared, but exposes no named fields.
No examples provided.
ugt_remove Remove a recipe ~67
Remove what UGT created for a recipe: its containers, images and workspaces. Its saved data and the results in the UGT folder stay.
| Name | Type | Req | Description |
|---|---|---|---|
| recipe | string | yes | the recipe, as owner/repo/task, or owner/repo when UGT holds one of its recipes |
| Name | Type | Req | Description |
|---|---|---|---|
| done | null|array | yes | – |
| kept | null|array | – | – |
| missing | boolean | – | – |
| recipe | string | yes | – |
No examples provided.
ugt_run Run a GitHub project ~277
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 |
Structured output declared, but exposes no named fields.
No examples provided.
ugt_setup Set up UGT's engine ~99
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.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_admin | boolean | – | true only when the user agreed to admin approval and a possible restart |
Structured output declared, but exposes no named fields.
No examples provided.
ugt_status Check on a job ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| job | string | yes | the job ID |
| wait_seconds | integer | – | how long to wait for it to finish, up to 50 |
Structured output declared, but exposes no named fields.
No examples provided.
ugt_stop Stop a recipe's services ~48
Stop a recipe's running services, keeping everything else.
| Name | Type | Req | Description |
|---|---|---|---|
| recipe | string | yes | the recipe, as owner/repo/task, or owner/repo when UGT holds one of its recipes |
| Name | Type | Req | Description |
|---|---|---|---|
| done | null|array | yes | – |
| kept | null|array | – | – |
| missing | boolean | – | – |
| recipe | string | yes | – |
No examples provided.
ugt_submit Share a recipe ~141
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | – | who made and verified it, for the pull request, such as your name and model |
| dir | string | yes | the recipe folder |
| dry_run | boolean | – | show what would be proposed, and change nothing |
Structured output declared, but exposes no named fields.
No examples provided.
ugt_verify Verify a recipe ~166
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | yes | 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 |
Structured output declared, but exposes no named fields.
No examples provided.
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.
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
2b02a64c5eb224254901879e467b1cc3baf71b9a598f00512561df554c19ee15
macOS / Linux
echo "2b02a64c5eb224254901879e467b1cc3baf71b9a598f00512561df554c19ee15 ugt-mcp-linux-amd64.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\ugt-mcp-linux-amd64.mcpb).Hash -eq "2b02a64c5eb224254901879e467b1cc3baf71b9a598f00512561df554c19ee15"
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 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.