GitHub
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
Description from the maker (original English)
Generates a pre-coding reliability skill (SKILL.md) for your agent repo from Trustabl's rules.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Download the maker’s .mcpb file
The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.
Run this in your terminal
claude mcp add agent-reliability-skills -- npx -y @trustabl/agent-reliability-skillsPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"agent-reliability-skills": {
"command": "npx",
"args": [
"-y",
"@trustabl/agent-reliability-skills"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"agent-reliability-skills": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@trustabl/agent-reliability-skills"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account trustabl, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.0-rc.2) reached the registry yesterday.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, MCPB on your computer.
In the same category: GitHub, Desktop Commander, Cloudflare MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
MCP server for terminal commands, file operations, and process management
Cloudflare MCP servers
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Forge Claude Code skills generate more reliable agents.
Agent Reliability Skills is the MCP server for Trustabl Forge. It writes a pre-coding reliability skill for your repository: Forge reads the repository's dependency manifests (package.json, pyproject.toml, requirements.txt, go.mod and others), finds the agent SDKs it uses, and builds a SKILL.md from Trustabl's detection rules for exactly those SDKs. An agent that reads the skill applies the rules while it writes code, instead of meeting them later as findings in a scan.
The skill is generated per repository. It is not a fixed skill to install, and it changes as your dependencies and Trustabl's rules change.
Supported SDKs include the Claude Agent SDK, OpenAI Agents SDK, Google ADK, MCP, LangChain and LangGraph, CrewAI, Pydantic AI, the Vercel AI SDK and AutoGen.
Requires Node.js 22 or later. Every install below downloads the release file from GitHub.
claude mcp add agent-reliability-skills -- npx -y https://github.com/trustabl/agent-reliability-skills/releases/download/v0.1.0-rc.2/agent-reliability-skills-0.1.0-rc.2.tgz
Add to .cursor/mcp.json in your project, or ~/.cursor/mcp.json for every project:
{
"mcpServers": { "agent-reliability-skills": { "command": "npx", "args": ["-y", "https://github.com/trustabl/agent-reliability-skills/releases/download/v0.1.0-rc.2/agent-reliability-skills-0.1.0-rc.2.tgz"] } } }
Open Settings → Developer → Edit Config and add the same mcpServers entry to claude_desktop_config.json, then restart Claude Desktop.
Claude Desktop has no project folder, so name the repository when you ask, for example: *"Generate the Trustabl pre-coding skill for /Users/me/code/my-agent and write it to .claude/skills/trustabl-pre-coding/SKILL.md."*
trustabl_forge tool| Input | Required | Meaning |
|---|---|---|
path | see below | Absolute path of the repository. A relative path is resolved against the client's workspace. |
policy | no | SDK categories to add on top of the detected ones, for an SDK not yet in a manifest (for example openai_sdk). |
lang | no | Languages to add: python, typescript, go. |
output_path | no | Write the skill here, relative to the repository. Usually .claude/skills/trustabl-pre-coding/SKILL.md. |
It returns a short summary (the SDKs covered, where the skill was written) and the SKILL.md content.
It writes a file only when output_path is given. The path must stay inside the repository, and an existing file is replaced only if Forge generated it, so regenerating a stale skill works but a hand-written file is never overwritten.
path is neededpath is optional when your client reports its workspace through MCP roots, and required otherwise. Forge never guesses from the server's working directory, because some clients start servers from your home directory.
| Client | Reports its workspace |
|---|---|
| Claude Code | pending |
| Cursor | pending |
| Claude Desktop | pending |
| Variable | Default | Meaning |
|---|---|---|
TRUSTABL_VERSION | latest | Analyzer release to run, for example v0.1.15. Must be v0.1.14 or later. |
GITHUB_TOKEN | unset | Used only to download the analyzer. Avoids GitHub's anonymous limit of 60 requests an hour. |
TRUSTABL_BIN | unset | Path to a local trustabl build to run instead of downloading one. |
The server runs the Trustabl analyzer's trustabl forge. On first use it downloads the analyzer release for your OS and architecture, checks it against the release's checksums.txt (a mismatch is a hard failure), and caches it in ~/.agent-reliability-skills/ /. The analyzer's own TRUSTABL_TELEMETRY setting applies to the binary it runs; analyzer telemetry is off until you configure it.
The first call fetches two things: the analyzer binary, and Trustabl's rules repository, which the analyzer caches. After that both work offline from cache. No git binary is needed.
Each release attaches agent-reliability-skills- .tgz and checksums.txt, and every install above downloads the .tgz, so GitHub counts it. pending. A weekly workflow records the counts in .github/stats/download-history.json. They are downloads, not users, and include automated installs such as CI.
version in package.json, update the release URLs in this README and mcp.json (CI fails until they match), run npm run build in server/, and commit dist/index.js.v and push the tag. The release workflow checks the tag against package.json, packs the server, and publishes the .tgz with checksums.txt.See SECURITY.md.