Remote MCP server exposing GitHub (repos, issues, PRs, contents, search) to MCP clients, authenticated via a GitHub App OAuth user-to-server flow. Deployed on Cloudflare Workers.
19 tools with consistent verb-noun naming (github_get_*, github_create_*, github_list_*, github_delete_*). All tools have descriptions (avg ~120 chars, within baseline 34-392). Input schemas present with typed parameters. However, parameter descriptions are sparse or null across most tools, owner, repo, path, issue_number, pull_number lack descriptions entirely. Output schemas are not documented. Error handling is minimal; no recovery guidance or actionable error messages visible in tool definitions. Destructive tools (delete_file, merge_pull_request) lack confirmation patterns. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk levels.
Close an issue, optionally as 'completed' or 'not_planned'.
Add a comment to an issue or pull request (PRs are issues for commenting purposes).
Create a new issue in a repository.
Create a new file or update an existing one. If updating, the current file SHA is fetched automatically unless provided — pass it explicitly when you already have it to save a round trip or to guard against concurrent modification.
Open a new pull request from one branch into another.
Delete a file from a repository. Irreversible via this tool — confirm with the user before calling.
Parameter descriptions missing or null for core identifiers (owner, repo, path, issue_number, pull_number). LLMs cannot infer whether 'owner' is a username, org name, or ID.
Output schemas not documented. LLMs cannot plan downstream tool calls or extract required fields (e.g., what does github_get_file_contents return? file_content? content? data.content?).
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 65 | <=2025-11-25 | v2 |
Get full details of a single commit, including changed files and their patches.
Read a file's contents, or list a directory's entries if the path points to a directory.
Get full details of a single issue, including its body text.
Get full details of a pull request, including mergeability and review-required status.
Get metadata for a single repository (description, default branch, visibility, topics, etc).
List branches in a repository.
List commits on a branch (or the default branch if none given), optionally filtered to a path.
List issues in a repository. Excludes pull requests by default (GitHub's API treats PRs as issues internally).
List the files changed in a pull request, with per-file diff stats.
List pull requests in a repository.
List repositories this GitHub App installation can access for the authenticated user. Use this first if you don't already know the exact owner/repo.
Merge a pull request. Destructive and irreversible via this tool — confirm with the user before calling.
Update repository metadata: description, homepage URL, and/or topics. Requires the GitHub App to have the Administration repository permission — if it doesn't, this returns a 403 and the change must be made another way.
Destructive tools (github_delete_file, github_merge_pull_request) lack confirmation or dry-run patterns. Agents can irreversibly delete files or merge PRs without user confirmation.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk levels. Agents cannot distinguish safe reads from destructive writes without parsing descriptions.
Error handling not visible in tool definitions. No recovery guidance, actionable error messages, or error classification (retryable vs user-fixable vs fatal).