ToolsMCP
github-twin
Listed in the official MCP Registry with an installable pypi package. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- christopherdavenport (GitHub)
- Prerequisites
- Install github-twin from pypi (stdio transport). Declares 3 secret inputs. Inspect it before installing; AgentsByTask never installs discovered packages.
- Current version
- 0.0.17 · updated
- Official links
Publisher’s description
Personal RAG over your GitHub history (commits, code, reviews), served to Claude Code over MCP.
Evidence
Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.
-
Listed in the official MCP Registry
Version 0.0.17, registry status active. 1 package (pypi)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- christopherdavenport (GitHub)
- Version observed
- 0.0.17
- Source
- registry.modelcontextprotocol.io/v0.1/servers/io.github.ChristopherDavenport%2Fgithub-twin/versions/0.0.17
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Work with issues and pull requests | Publisher description mentions “github”, “commits”. | No connection check or task run. Capability is as described by the publisher. | Rule code-repositories matched: “github”, “commits”. Rule code-repositories. |
Published pricing
No published price recordedCost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.
Registry record
- Packages
github-twin(pypi, stdio, 3 secret inputs)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
io.github.ChristopherDavenport/github-twin
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.