MCP.Market

Oss Issues MCP server

by AmrMohamed17·io.github.AmrMohamed17/oss-issues-mcp·v0.1.1
No reviews yet

MCP server with derived GitHub issue tools: normalized fetch, new-issue watch, claim status.

B83/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B83/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Oss Issues yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Oss Issues tools (4)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • get_actionable_issue

    Fetch one issue, normalised for triage: template scaffolding stripped, only the fields a readiness judge needs (title, cleaned body, labels, author association, comments, state, url).

  • get_claim_status

    Is this issue already being worked on?

  • get_repo_context

    The repo's contribution rules: CONTRIBUTING.md presence/excerpt and whether issue templates are configured. Fetched once per repo and cached, since these rarely change.

  • list_new_issues

    New OPEN issues across the watch-list, pull requests excluded.

Public scan report

scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it

no findings
  • Code scan7 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 2 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 83/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Oss Issues compares

Against every graded Developer tools MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
83/100
higher than 65% of 1,119 Developer tools servers
Tools
4
the typical Developer tools server has 7
Tools that change things
0%
typical: 5%. Fewer write tools means less an agent can break

What its tools let an agent do: 4 read

Install Oss Issues in Claude Code, Cursor or VS Code

claude mcp add oss-issues-mcp -- uvx oss-issues-mcp
Add to Cursor

What the publisher says

From the Oss Issues repository's README, as published. We do not edit it. Read it on GitHub

oss-issues-mcp

<!-- mcp-name: io.github.AmrMohamed17/oss-issues-mcp --> An MCP server exposing derived, triage-oriented GitHub issue tools — not a passthrough of the GitHub API.

Where GitHub's own MCP server returns raw API responses, this server does task-specific work: stripping issue-template scaffolding, resolving whether an issue is already claimed from multiple signals, and filtering a watch-list of repositories to what is new and open.

Tools

Security

  • Repository allowlist — the server refuses any repo not explicitly allowed.
  • Read-only — no write tools exist until a human-approval gate governs them.
  • Requires a fine-grained, read-only GITHUB_TOKEN.

Run

export GITHUB_TOKEN=github_pat_...
uv sync
uv run oss-issues-mcp

License

MIT

Nothing above is checked by us. What we check is on the safety report.

Oss Issues: common questions

Is Oss Issues MCP server safe?
Mostly: it is graded B (83/100). Read the Oss Issues safety report
How do I install Oss Issues?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Oss Issues need an API key?
Yes. The registry entry asks for GITHUB_TOKEN.
Is Oss Issues maintained?
The last commit was 43 days ago (2026-09-22). The latest release is v0.1.1.
What can I use instead of Oss Issues?
Servers from other publishers that do the same job: GitHub MCP server, Gk CLI MCP server and Pare Github MCP server.
How does Oss Issues compare with other Developer tools MCP servers?
safety score 83/100 (higher than 65% of 1,119 Developer tools servers); tools 4 (the typical Developer tools server has 7); tools that change things 0% (typical: 5%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Oss Issues

Same job from other publishers: the closest match first, then the best rated.

  • GitHub
    Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
    A
  • Gk CLI
    The GitKraken MCP Server for managing repos, PRs, issues across GitHub, GitLab, Bitbucket and more.
    B
  • Pare Github
    Pare GitHub ג€” Structured GitHub operations (PRs, issues, actions) as typed JSON.
    More from Dave-London →
    A
  • Sentry
    MCP server for Sentry - error monitoring, issue tracking, and debugging for AI assistants
    A
  • GitLab MCP Server
    GitLab MCP server for projects, merge requests, issues, pipelines, wiki, releases, and more.
    B