"Projects that showcase advanced GitHub repository search techniques" matching MCP tools:

• atlas_technique_searchA

  ContrastAPIA

  Search the MITRE ATLAS catalog of AI/ML attack techniques by keyword, tactic, or maturity. Default response is SLIM (description truncated to 240 chars per row); pass include='full' for the verbose record. Pass exclude_id when chaining from atlas_technique_lookup to skip self in sibling-tactic searches. Use this to discover techniques matching a threat-model question, e.g. 'what techniques target LLM serving infrastructure?'. Drill into atlas_technique_lookup with any returned technique_id for the full description, ATT&CK bridge, and pivot hints. For broader cross-referencing: when a result has attack_reference_id, that bridges to D3FEND mitigations via d3fend_defense_for_attack. Free: 30/hr, Pro: 500/hr. Returns {query (echoed filters), total, results [{technique_id, name, description (truncated by default), tactics, inherited_tactics, maturity, attack_reference_id, subtechnique_of}], next_calls}.

  ConnectorNo auth

• works_verify_public_repositoryA

  WORKS Public VerifierA

  Use only after works_public_eligibility returns eligible. Download that immutable public GitHub snapshot, run the selected pinned static contract without executing repository commands, and return a signed receipt. Return the report field verbatim and stop.

  ConnectorNo auth

• fetchA

  developer-toolkit-mcpA

  Retrieve the complete markdown of one documentation article by the id returned from `search` (for example `en/claude-code/advanced-techniques/hooks-automation`). The text is returned in full; `metadata.gated` only reports whether the article sits behind the paywall on the web. An unknown id is an error — call `search` first.

  ConnectorNo auth

• import_repoA

  LayeroA

  Create a Layero project from a repository — path (a) without the dashboard. From then on a push to the branch is a preview, a push to the production branch is production. After the link the tool finishes the setup wizard itself and starts the first build; `setup` in the result says whether that happened. Detected values are NOT written into the project settings: the builder detects the framework, build command and output folder from the repository on every build, so a later change in the repository is picked up. Only a decision is pinned — the app folder of a monorepo and the package manager named in `layero.json`. Until 2.1.1 the project stayed in `pending_setup` while the answer promised a build that never started. Two shapes, same as the CLI: GitHub goes through the App installation (project and webhook in one call); other providers create the project first and then connect the source — that step reports whether the webhook could be registered. If the provider is not connected, the result says `needs_connection` with the dashboard address: the person connects the token there, never through the chat. Monorepo: one project builds one app folder — pass `root_directory`. Several apps in one repository are several projects, one call each, with different `root_directory` and `name`. If the repository is already linked and the call would duplicate an existing project (same folder, or no `root_directory` given), nothing is created: the result is `already_linked` with `linked_projects` — slug, url, root_directory and branch of every project built from this repository. On `created`, `linked_projects` lists the OTHER projects already built from the same repository; `linked_projects_checked: true` says the check was made, so an empty list means there are none (`my_projects(repo=…)` answers the same question later). When the root has no app and detection sees a frontend + backend pair, `app_dir_candidates` names the folders.

  ConnectorAPI key

• import_repoA

  LayeroA

  Create a Layero project from a repository — path (a) without the dashboard. From then on a push to the branch is a preview, a push to the production branch is production. After the link the tool finishes the setup wizard itself and starts the first build; `setup` in the result says whether that happened. Detected values are NOT written into the project settings: the builder detects the framework, build command and output folder from the repository on every build, so a later change in the repository is picked up. Only a decision is pinned — the app folder of a monorepo and the package manager named in `layero.json`. Until 2.1.1 the project stayed in `pending_setup` while the answer promised a build that never started. Two shapes, same as the CLI: GitHub goes through the App installation (project and webhook in one call); other providers create the project first and then connect the source — that step reports whether the webhook could be registered. If the provider is not connected, the result says `needs_connection` with the dashboard address: the person connects the token there, never through the chat. Monorepo: one project builds one app folder — pass `root_directory`. Several apps in one repository are several projects, one call each, with different `root_directory` and `name`. If the repository is already linked and the call would duplicate an existing project (same folder, or no `root_directory` given), nothing is created: the result is `already_linked` with `linked_projects` — slug, url, root_directory and branch of every project built from this repository. On `created`, `linked_projects` lists the OTHER projects already built from the same repository; `linked_projects_checked: true` says the check was made, so an empty list means there are none (`my_projects(repo=…)` answers the same question later). When the root has no app and detection sees a frontend + backend pair, `app_dir_candidates` names the folders.

  ConnectorOAuth

• 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

• search-music-docsA

  Music StudioA

  Search detailed documentation for Strudel live coding or ABC/ABCJS notation. Returns relevant code examples and explanations from the official docs. Use this when the curated guides (get-strudel-guide, get-music-guide) don't cover what you need — for specific functions, advanced techniques, or when you're unsure about syntax. Powered by semantic search over strudel.cc and ABCJS docs.

  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

• connect_gitops_repositoryA

  AnkraB

  Connect a GitOps repository to a cluster that has none: bind an existing GitHub credential plus a repository and branch - the same binding the portal's GitOps step creates. Pick the credential from list_gitops_credentials (pass credential_id, or credential_name when unambiguous) and the repository from list_gitops_repositories: it must be in the credential's synced repository list. On confirm the binding is written to the cluster's resource graph, a repository webhook is provisioned best-effort, the current cluster state is pushed to the repository as an initial commit, and a sync is nudged so the repository and the cluster record converge. Refused when the cluster is already connected to a DIFFERENT GitOps source: repointing prunes everything the new source does not define, so it stays on the cluster settings flow with its explicit acknowledgements. Re-connecting the identical repository and branch is safe and just refreshes the binding.

  Connector

  Destructive

  OAuth

• 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

• bulk_atlas_technique_lookupA

  ContrastAPIA

  Bulk ATLAS technique lookup — retrieve full records for up to 50 techniques in a single request instead of N separate atlas_technique_lookup calls. Designed as the natural follow-up to atlas_case_study_lookup, whose techniques_used array can be passed directly. Each item is the same shape as atlas_technique_lookup, including parent-tactics inheritance for sub-techniques (inherited_tactics=true flag) and per-item next_calls (D3FEND bridge when attack_reference_id present, sibling-technique search by tactic, parent lookup for sub-techniques). Free: 30/hr (1 per item), Pro: 500/hr. Returns {results [{technique_id, status (ok|not_found|invalid_format), technique, error}], total, successful, failed, partial, summary}.

  ConnectorNo auth

• list-packagesA

  LaraviltA

  List every Laravilt package (laravilt/*) with its description, latest released version, last release date, composer install command and GitHub repository URL. Use this first to discover which packages exist before calling get-package, list-docs or search-docs.

  ConnectorNo auth

• atlas_technique_lookupA

  ContrastAPIA

  Look up a MITRE ATLAS technique — the AI/ML adversarial attack catalog. ATLAS catalogues TTPs targeting machine learning systems: prompt injection, model evasion, training data poisoning, model theft, etc. Roughly 80% of ATLAS techniques are AI/ML-specific (no ATT&CK bridge); 20% mirror an enterprise ATT&CK technique via attack_reference_id — use that to pivot to D3FEND defenses (d3fend_defense_for_attack) and CVE search. Sub-techniques inherit `tactics` from the parent (inherited_tactics=true flag) when ATLAS upstream leaves them empty. Use this tool when the user asks about AI/ML threats, LLM red-teaming, or adversarial ML; for multiple techniques in one call (e.g. drilling into a case study's techniques_used), prefer bulk_atlas_technique_lookup. Returns 404 when the id is not in the synced ATLAS catalog. Free: 30/hr, Pro: 500/hr. Returns {technique_id, name, description, tactics, inherited_tactics, maturity (demonstrated|feasible|realized), attack_reference_id, attack_reference_url, subtechnique_of, created_date, modified_date, next_calls}.

  ConnectorNo auth

• initA

  SymvantaA

  Call first, with repository:"owner/name" (your checkout's GitHub remote). Binds the session to the project holding that repository and returns it as the active project with its repositories, index health, and a `usage` field (decision matrix + routing). workspace.attached=false means the checkout is NOT indexed: nothing in the answer describes it; attach it (add_repository, create_project) or work without the graph, do not route through the projects listed. Without repository: the pinned project (ref op:"use_project") or the workspace default.

  ConnectorNo auth

• set_github_repoA

  Inclusify AccessibilityA

  Names the GitHub repository where this site's problems become work somebody can pick up. Reach for it when a developer or a coding agent should be getting issues instead of reading a dashboard. WRITES to this website's Inclusify configuration, never to the site itself and never to GitHub: it records the repository and opens no issues by itself, which file_github_issues does. It CANNOT install the GitHub App: that is an approval screen on the customer's GitHub account reached from the Integrations page of the Inclusify panel, and no assistant can do it, so this refuses until the workspace has an installation. Before saving it checks the App can actually write issues in that repository and saves nothing if it cannot, so a stored binding always works. REQUIRES CONFIRMATION, because the wrong repository puts accessibility work in front of a team that did not ask for it, somewhere a coding agent may act on it unattended. The account owner is emailed a record, including the previous repository. Needs the PRO plan, matching the panel.

  Connector

  Destructive

  API key

• search_github_projectsA

  AIGC Radar MCPA

  MCP-first search for public non-AI GitHub repositories and open-source software (Windows, macOS, Linux, desktop, screenshot and screen capture, productivity, developer tools, and more); it never searches the user's favorites. Call it whenever the user asks to find, search, recommend, compare, or reuse a non-AI project, repository, open-source implementation, SDK, framework, component, template, example, or tutorial, even if GitHub or open source is not named. Also call it once before implementing, or recommending an architecture, technology, or build-vs-reuse approach for, a major non-AI module, complete capability, or independent subsystem. Skip narrow work: copy or styling, renames, localized bugs, tests/logging/types, field tweaks, simple CRUD, or a single function, component, or endpoint. For AI, Agent, MCP, RAG, or LLM artifacts use search_github_ai_projects; for explicitly scholarly deliverables use search_papers. Run at most one initial search per unchanged requirement and never batch it with WebSearch/WebFetch/Bash: inspect the result first, and use a host tool only if this call fails, returns no usable or relevant items, or lacks a specific fact, querying only that detail. Translate non-English intent into a concise GitHub query that keeps product names and requested features. With no local lexical match the tool falls back to a bounded read-only GitHub Search labeled github_api_fallback. Local and fallback results have at least 500 GitHub stars; verify that floor for projects found through WebSearch and omit unverifiable ones. Neither the floor nor a match authorizes architecture-changing adoption: present reuse, design-reference, and build-from-scratch options and await the user's choice. Open a repository only when its metadata cannot confirm a requested feature. Items carry data_source "aigcnews.cn"; cite AIGC Radar · aigcnews.cn when presenting results.

  ConnectorNo auth

• github_searchA

  SiteCheckB

  GitHub search with its own query syntax (e.g. 'sqlite language:rust stars:>100'). Repositories: name, owner, stars, forks, language, topics, licence, pushed date. Issues: title, state, labels, comments, URL. Code: path, repository and link. GitHub limits search to about 30 requests a minute; a busy minute is a 503, not charged. Limit max 30. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

  ConnectorNo auth

• push-to-githubA

  WebTwizzA

  Use this when the user wants their WebTwizz site's code on GitHub. Commits and pushes the saved site to its repository; each call with new changes adds another commit. Other git work, like undoing a push, goes to edit-site. The first time, pass repo (an existing repository from get-github-status) or create_repo (a name for a new private repository).

  Connector

  Destructive

  OAuth

• eurobase_list_github_reposA

  EurobaseB

  List repositories the GitHub installations connected to this Eurobase account can access, from the recorded snapshot the dashboard shows: full name, name, default branch and private flag, at most limit (50 by default) in full-name order. query matches part of the full name. accountStatus tells whether GitHub is connected; the GitHub connection and its repository access are managed by the user in the Eurobase dashboard. Requires a grant that can create projects. Repository names are user-defined text.

  ConnectorOAuth

• admin_refresh_catalogA

  Galatic.aiA

  Admin only: rebuild a model catalogue now instead of waiting for its schedule; runs in the request and makes no paid generation calls. "capabilities" re-reads each Kie.ai model's documentation and rewrites the capabilities table that list_models reads, keeping the last good entry when a page fails; returns per-model success, partial and failed counts. "showcase" rebuilds the public model showcase from the admin account's gallery items of the last 90 days (top 3 per model) and returns the new showcase.

  Connector

  Destructive

  OAuth