search_issues
12 registry entries were observed exposing a tool named search_issues — none of them flagged as a privileged capability.
Every row is point-in-time scan output, dated below. Forge has an observed tool surface for 8,491 of 26,663 scannable entries (32%) — an entry that has not been scanned cannot appear here, so absence from this list is not evidence that an entry does not expose this tool.
- MCP serverobserved · static extractionReference MCP servers that are no longer maintained
- MCP serverobserved · static extractionMCP server for GitHub — search repos/code/issues, read repos/issues/PRs/files, and create issues, authenticated via OAuth device flow or a t
- MCP serverobserved · static extractionMantisBT MCP server – manage issues, notes, files, tags, and relationships. With semantic search.
- MCP serverobserved · static extractionPersistent memory for AI coding agents — past bugs, decisions, and your corrections, in your repo.
- MCP serverobserved · static extractionSearch and analyze 7M+ newsletters, issues, contacts, and chart rankings from Reletter.
- MCP serverobserved · static extractionA Forgejo MCP Server
- MCP serverobserved · static extractionShared, permission-aware company context for AI agents, with provenance, approvals and audit.
- MCP serverobserved · static extractionConvert any GitHub repo to MCP server - automatic tool generation API wrap
- MCP serverobserved · static extractionGitLab Public MCP — wraps the GitLab REST API v4 (public endpoints, no auth)
- MCP serverobserved · static extractionMCP server for Huly — manage projects, issues, documents and more via natural language.
- MCP serverobserved · static extractionMCP server for Backlog API integration with AI agents.
- MCP serverobserved · static extractionMCP server for Redmine API integration with AI agents.