"A tool to check the status of pull requests on public GitHub repositories" matching MCP tools:

• list_reposA

  SHPBL: Repository Audit & RepairA

  Lists real repository names so a run never starts on a guessed one, and answers whether a repository can be written to. Pass `github_token` to see everything that token can see, or `owner` to list a public account's repositories; with neither, it lists the repositories the SHPBL GitHub App is installed on for this key — the same ones a pull request can be opened on. Pass `repo: "owner/name"` to ask about one target instead of reading the whole list. Free — costs no allowance.

  ConnectorNo auth

• github_search_repositoriesA

  Crawlora MCPB

  Searches public GitHub repositories and returns matching repository rows for market or competitive discovery. Unauthenticated search is rate limited to roughly 10 requests per minute. q: GitHub repository search query. Use github_search_users to search public GitHub users.

  ConnectorNo auth

• github_user_pinnedA

  Crawlora MCPB

  Returns the repositories a user pinned on their public profile (showcase signal). Empty when the user pinned nothing. username: GitHub username. Use github_user_repos to list a GitHub user's public repositories.

  ConnectorNo auth

• github_search_repositoriesA

  Crawlora MCPA

  Searches public GitHub repositories and returns matching repository rows for market or competitive discovery. Unauthenticated search is rate limited to roughly 10 requests per minute. q: GitHub repository search query. Use github_search_users to search public GitHub users.

  ConnectorNo auth

• github_user_pinnedA

  Crawlora MCPA

  Returns the repositories a user pinned on their public profile (showcase signal). Empty when the user pinned nothing. username: GitHub username. Use github_user_repos to list a GitHub user's public repositories.

  ConnectorNo auth

• get-github-statusA

  WebTwizzA

  Use this when the user asks about GitHub for one of their WebTwizz sites: whether it is linked to a repository, if GitHub has changes the site does not, the last push, recent commits and open pull requests. When nothing is linked yet it says how to connect, and lists their repositories once GitHub is connected.

  ConnectorOAuth

• github_org_reposA

  Crawlora MCPB

  Returns a page of an organization's public repositories (company tech stack). org: GitHub organization login. Use github_user_repos to list a GitHub user's public repositories.

  ConnectorNo auth

• github_org_reposA

  Crawlora MCPA

  Returns a page of an organization's public repositories (company tech stack). org: GitHub organization login. Use github_user_repos to list a GitHub user's public repositories.

  ConnectorNo auth

• list_github_reposA

  StresixA

  The GitHub repositories the user gave Stresix access to, including private ones. Public repositories work without connecting GitHub.

  ConnectorNo auth

• setup_scheduled_pullA

  mcp-serverA

  End-to-end workflow for "pull files from this SFTP server / S3 bucket on a schedule" requests: reuses a matching connection if one already exists in the workspace (same hostname/username for sftp, same roleArn for aws_s3), otherwise creates one; tests it; then creates a trigger that feeds an already-analyzed data spec (see onboard_data_source) on the given frequency. Pass hostname for an sftp pull, or roleArn (+ s3Bucket, required) for an aws_s3 pull — exactly one of the two is expected. Use this instead of calling manage_connection + manage_trigger yourself for first-time setup. If the connection test fails (e.g. the sftp public key or the aws_s3 IAM role isn't set up yet on the customer's side), no trigger is created — ask the user to finish that setup and re-run this tool, which will reuse the same connection and pick up where it left off. This is for pulling a NEW file from an external source — for "run this on a schedule/after another job" where the spec queries tables already in the workspace (sourceType "tables"), use manage_trigger with type "schedule" or "spec_success" instead; there is no connection involved.

  ConnectorOAuth

• services_list_open_requestsA

  bitroadA

  Seller-side: list unanswered quote requests (status=requested). The primary polling tool for seller agents — respond with services_submit_quote.

  ConnectorNo auth

• get_job_statusA

  CatchAll (by NewsCatcher)B

  Check the status of a submitted job. Call this after submit_query to see if your job is ready. Status progression: submitted -> analyzing -> fetching -> clustering -> enriching -> completed/failed IMPORTANT: Jobs take several minutes to process. First check after ~1-2 minutes, then poll every 30-60 seconds. Broad searches can take 10-30+ minutes; for long jobs, poll every 60-120 seconds. Do NOT call this tool in a tight loop. Stop polling when status is `completed` or `failed`. Treat `submitted`, `analyzing`, `fetching`, `clustering`, and `enriching` as active states and continue polling. You don't need to wait for completion to pull results. Partial results are available during `enriching` — call pull_results after ~2 minutes, then poll status every 30-60 seconds and pull again for fresher results. Do not stop pulling just because an intermediate pull is empty/unchanged. Use `progress_validated` vs `candidate_records` to track whether more results may still appear (`progress_validated < candidate_records`). If transport/session fails, resume using the same `job_id`.

  ConnectorNo auth

• get_job_statusA

  CatchAllB

  Check the status of a submitted job. Call this after submit_query to see if your job is ready. Status progression: submitted -> analyzing -> fetching -> clustering -> enriching -> completed/failed IMPORTANT: Jobs take several minutes to process. First check after ~1-2 minutes, then poll every 30-60 seconds. Broad searches can take 10-30+ minutes; for long jobs, poll every 60-120 seconds. Do NOT call this tool in a tight loop. Stop polling when status is `completed` or `failed`. Treat `submitted`, `analyzing`, `fetching`, `clustering`, and `enriching` as active states and continue polling. You don't need to wait for completion to pull results. Partial results are available during `enriching` — call pull_results after ~2 minutes, then poll status every 30-60 seconds and pull again for fresher results. Do not stop pulling just because an intermediate pull is empty/unchanged. Use `progress_validated` vs `candidate_records` to track whether more results may still appear (`progress_validated < candidate_records`). If transport/session fails, resume using the same `job_id`.

  ConnectorNo auth

• ado_list_prsA

  ALM X++ MCP ServerA

  [~] PRIORITY TRIGGER: Use this tool when user mentions 'PR', 'Pull Request', 'list PRs', 'show PRs', 'active PRs', 'mes PR', 'liste des PR', 'pull requests ouverts', 'what PRs are open', 'PRs by [author]', 'PRs targeting [branch]'. NEVER call search_d365_code for PR listing requests. List Pull Requests in an Azure DevOps Git repository. If `repositoryId` is unknown, omit it and all repositories will be listed first. Filters: status (Active/Completed/Abandoned/All), author display name, target branch. Returns: PR ID, title, author, source->target branch, review status, linked work items, creation date. Use `ado_analyze_pr_impact` with a PR ID to get full D365 code impact analysis. Requires DEVOPS_ORG_URL + DEVOPS_PAT (Code: Read scope).

  ConnectorNo auth

• findagent_connect_githubA

  FindAgentA

  Start connecting GitHub for the CALLER'S OWN FindAgent account so findagent_import_repo / findagent_list_repos can pull their repos. Returns whether GitHub is already connected plus a browser connect URL — the caller opens it, authorizes GitHub, and the token is stored server-side (this tool grants nothing itself; the actual connect happens in the browser). Call this first if import_repo or list_repos reports github not connected. The connection is scoped to THIS FindAgent account, so authorize on the same browser account. To switch GitHub accounts, use findagent_disconnect_github first.

  ConnectorOAuth

• deploy-repository-toolA

  CoderbudsA

  Trigger a production deploy for one of your team's connected repositories. The repository must have a deploy trigger configured — either a deploy hook URL or a GitHub Actions workflow — in its Coderbuds settings. Identify the repository by name (e.g. "saas") or by full name (e.g. "patchstack/saas"). This ships whatever is currently merged; it is not a dry run. Use GetUndeployedPullRequestsTool first if you want to see what will go out.

  ConnectorOAuth

• recommend_reposA

  whichlibA

  Find the best open-source library for a need before adding a dependency. Give the need in plain words and get up to `limit` GitHub repositories ranked by fit = score x relevance to the need. Each result has a 0-100 score (momentum 40% (stars gained per week; without history, lifetime stars per week scaled by the npm/PyPI download trend), maintenance 25%, adoption incl. npm/PyPI weekly downloads 25%, license 10%), a tier (Strong >=75, Solid >=50, Watch >=25, Avoid <25; New for repos under 30 days old, too new to judge), a one-line verdict and the full breakdown. Use this when you do not yet have candidates; use compare_repos when you already have names. Makes 3 GitHub searches plus npm/PyPI lookups for the shortlist. Hosted: 50 free tool calls per day per user; send header X-GitHub-Token with your own GitHub token for unlimited use, or run the npm package locally (npx -y whichlib).

  ConnectorNo auth

• trending_reposA

  whichlibA

  Discover projects: the most-starred GitHub repositories created in the last day, week or month, or with period "rising" repositories of any age that gained the most stars this week (like GitHub Trending; risingRank keeps that order). Optionally one language; each scored and returned sorted by score (starsRank keeps the stars order). Each result has a 0-100 score (momentum 40% (stars gained per week; without history, lifetime stars per week scaled by the npm/PyPI download trend), maintenance 25%, adoption incl. npm/PyPI weekly downloads 25%, license 10%), a tier (Strong >=75, Solid >=50, Watch >=25, Avoid <25; New for repos under 30 days old, too new to judge), a one-line verdict and the full breakdown. Not the right tool for picking a dependency, since new repositories have little maintenance history; use recommend_repos for that. One GitHub search (rising: one download of the daily list from raw.githubusercontent.com instead), plus one npm/PyPI lookup per repository when withDownloads is true. Hosted: 50 free tool calls per day per user; send header X-GitHub-Token with your own GitHub token for unlimited use, or run the npm package locally (npx -y whichlib).

  ConnectorNo auth

• relate_repositoriesA

  AnkraB

  State that two repositories are related for AI code review, so a review of either may read the other. Organisation admins only. Use it for what the deploy graph cannot connect - a client and the API it calls, a shared library, a repository outside Ankra's deploy; applications installed on the same cluster are already related with no statement. The relationship is symmetric, so there is no mirror to add, and re-stating a pair changes nothing. Both repositories must be ones the named GitHub App installation can reach: Ankra checks that installation's live repository listing and refuses the pair otherwise, because the review fetches a related repository with that installation's own token. Returns the stored relationship.

  ConnectorOAuth

• submit_toolA

  AgentIndexA

  Suggest a GitHub repository (an AI agent, MCP server or AI developer tool) for listing on AgentIndex. No login or API key needed. The submission is queued for human review, usually within 1-3 days; it does not appear in search results immediately. Tools are listed only if the repository is public and has at least 100 stars. Check with search_tools first that the tool is not already listed. Returns {success, message, github_url}, or an isError result if the URL is not a GitHub repository URL or the submission service is unavailable.

  ConnectorNo auth

• list_github_reposA

  DockholdA

  List the GitHub repositories you have connected to Dockhold, across every installation. Call this before deploy_app when the target repo is private, or when the user asks which repos they can deploy. Each repo comes with its installation_id: pass that (with the repo's clone URL) to deploy_app to deploy a PRIVATE repository. Public repos don't need it.

  ConnectorNo auth