ToolsMCP
GitHub Issue MCP
Listed in the official MCP Registry with an installable npm package. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- sarim-aliii (GitHub)
- Prerequisites
- Install github-issue-mcp from npm (stdio transport). Declares 2 secret inputs. Inspect it before installing; AgentsByTask never installs discovered packages.
- Current version
- 1.1.2 · updated
- Official links
Publisher’s description
AI-powered MCP server for generating GitHub issues and detecting semantic duplicates.
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 1.1.2, registry status active. 1 package (npm)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- sarim-aliii (GitHub)
- Version observed
- 1.1.2
- Source
- registry.modelcontextprotocol.io/v0.1/servers/io.github.sarim-aliii%2Fgithub-issue-mcp/versions/1.1.2
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Work with issues and pull requests | Publisher description mentions “github”, “issue”, “issues”. | No connection check or task run. Capability is as described by the publisher. | Rule code-repositories matched: “github”, “issue”, “issues”. 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-issue-mcp(npm, stdio, 2 secret inputs)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
io.github.sarim-aliii/github-issue-mcp
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.