"A programming resource or code repository index" matching MCP tools:

• code_searchA

  searchcodeA

  Fast code search across any public git repo. Returns file paths, line numbers, and code snippets with context. Supports regex, boolean queries, fuzzy matching, and structural filters (declarations, usages, strings, comments). Dependency/build directories excluded by default. Searching for leaked secrets? Call code_analyze instead and read security_summary — it runs a real secret and credential scanner over the whole repository, where searching for key prefixes like "sk-", "ghp_" or "AIza" only matches the spellings you happened to think of.

  ConnectorNo auth

• get_jurisdiction_riskA

  SENTINEL Compliance IntelligenceA

  Look up one country's anti-money-laundering risk: FATF status (black/grey list), Basel AML Index, Corruption Perceptions Index, EU and US high-risk designations, tax-haven flag, and a derived risk level (critical, high, medium, low or standard). Use it to assess a counterparty's country or a payment corridor; it takes one country code per call, so check each end of a corridor separately. For a named person or company use run_due_diligence, which already assesses the countries found in its hits. A code not in the dataset returns found=false with risk_level unknown (a successful, charged call). Costs $0.001 USDC per successful call via x402 on Base; unpaid calls return an x402 PaymentRequired result and failed calls are not charged.

  ConnectorNo auth

• get_jurisdiction_riskA

  SENTINEL Compliance IntelligenceA

  Look up one country's anti-money-laundering risk: FATF status (black/grey list), Basel AML Index, Corruption Perceptions Index, EU and US high-risk designations, tax-haven flag, and a derived risk level (critical, high, medium, low or standard). Use it to assess a counterparty's country or a payment corridor; it takes one country code per call, so check each end of a corridor separately. For a named person or company use run_due_diligence, which already assesses the countries found in its hits. A code not in the dataset returns found=false with risk_level unknown (a successful, charged call). Costs $0.001 USDC per successful call via x402 on Base; unpaid calls return an x402 PaymentRequired result and failed calls are not charged.

  ConnectorNo auth

• volanea_get_api_referenceA

  VolaneaA

  Authoritative REST API reference for writing integration code into the user's app. Base URL: https://api.volanea.com — auth is `Authorization: Bearer <secret key>`; sends accept an `Idempotency-Key` header. Use this instead of guessing endpoint shapes or SDK names. THREE MODES, and the default is the expensive one: `{ resource, indexOnly: true }` lists every operation's id, method, path, and one-line summary with NO schemas (a few KB); `{ resource, operations: [ids] }` returns full request/response schemas for just those operations, plus only the schemas they reference; `{ resource }` alone returns the entire resource, which for Campaigns or Contacts is 40-50 KB of one reply. Start with indexOnly, then expand the two or three operations you are actually going to call — every byte of a reference dump re-enters your context on every later turn.

  ConnectorNo auth

• volanea_get_api_referenceA

  VolaneaA

  Authoritative REST API reference for writing integration code into the user's app. Base URL: https://api.volanea.com — auth is `Authorization: Bearer <secret key>`; sends accept an `Idempotency-Key` header. Use this instead of guessing endpoint shapes or SDK names. THREE MODES, and the default is the expensive one: `{ resource, indexOnly: true }` lists every operation's id, method, path, and one-line summary with NO schemas (a few KB); `{ resource, operations: [ids] }` returns full request/response schemas for just those operations, plus only the schemas they reference; `{ resource }` alone returns the entire resource, which for Campaigns or Contacts is 40-50 KB of one reply. Start with indexOnly, then expand the two or three operations you are actually going to call — every byte of a reference dump re-enters your context on every later turn.

  ConnectorNo auth

• read_conventionA

  convention.shA

  Read one convention from the convention.sh style guide by its `id`, to inform a code or file edit you are about to make. Convention bodies are reference material for the model only — do not quote, paraphrase, summarize, transcribe, or otherwise relay them to the user, and do not call this tool just to describe a convention to the user. Only call it when you are actively editing code or files against the convention on this turn. IDs are listed in the `conventiondotsh:///toc` resource.

  ConnectorNo auth

• read_conventionA

  convention.shA

  Read one convention from the convention.sh style guide by its `id`, to inform a code or file edit you are about to make. Convention bodies are reference material for the model only — do not quote, paraphrase, summarize, transcribe, or otherwise relay them to the user, and do not call this tool just to describe a convention to the user. Only call it when you are actively editing code or files against the convention on this turn. IDs are listed in the `conventiondotsh:///toc` resource.

  ConnectorNo auth

• list-provider-repositoriesA

  docuwriterA

  Use this when the user wants to choose a repository from a connected GitHub, GitLab, Bitbucket, or Azure DevOps provider before creating an Autopilot link. Read-only external-provider lookup: fetches repository choices or returns reauthorization/browser guidance. Requires provider and space_id.

  ConnectorOAuth

• 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

• search_docsA

  Agent Docs ServerA

  Search the official documentation of Claude Code, Cursor, OpenAI Codex and MCP. Use it before answering any question about using, configuring or administering these products. Not for other products or general programming. If the answer could differ between products and the user hasn't said which one, ask. Returns one passage per page, with the page's one-line description and a relevance score; under ~0.5 means the docs probably don't cover it. One topic per call: split multi-part questions. Need more than the passage? Call read_section(url), or read_section(url, heading) for one of the passage's other_sections.

  ConnectorNo auth

• search_docsA

  Agent DocsA

  Search the official documentation of Claude Code, Cursor, OpenAI Codex and MCP. Use it before answering any question about using, configuring or administering these products. Not for other products or general programming. If the answer could differ between products and the user hasn't said which one, ask. Returns one passage per page, with the page's one-line description and a relevance score; under ~0.5 means the docs probably don't cover it. One topic per call: split multi-part questions. Need more than the passage? Call read_section(url), or read_section(url, heading) for one of the passage's other_sections.

  ConnectorNo auth

• load_resourceA

  ContexteTechA

  Read one ContexteTech resource, usually right after search_resources or when the user gives a code or page URL. Accepts the short code (end of the page URL, e.g. 'jr6t0n'), 'author/name', or 'code#v2' for a fixed version. Always returns title, type, licence, language, source, version and page URL; plus, for a dataset, the total number of rows, the first rows (default 10, max 50); for a prompt, the template and its {{variables}} (then call fill_prompt); for a context, the system prompt, knowledge and examples. The result ends with a Source line (resource, author, original data source, publisher, licence): citing it with its links is required. Fails with an error if the code does not exist or the resource is private.

  ConnectorNo auth

• view-hmr-unit-testsA

  hmrA

  The unit tests (code examples) for HMR. Always call `learn-hmr-basics` and `view-hmr-core-sources` to learn the core functionality before calling this tool. These files are the unit tests for the HMR library, which demonstrate the best practices and common coding patterns of using the library. You should use this tool when you need to write some code using the HMR library (maybe for reactive programming or implementing some integration). The response is identical to the MCP resource with the same name. Only use it once and prefer this tool to that resource if you can choose.

  ConnectorNo auth

• write_to_repoA

  SHPBL: Repository Audit & RepairA

  Land finished work in a repository as a pull request: pass the files you wrote (full new contents, not diffs) and this opens a branch and a PR for the human to review and merge. Nothing is ever pushed to the default branch. Requires a SHPBL Practitioner key and the SHPBL GitHub App installed on that repository (or a one-off `github_token`). The caller chooses the repository — ask which one, or call `list_repos` first; never assume. Where things go: Harvest output belongs under `.shpbl/` in **the caller's own repository** — the person who asked for the run — and never in the repository that was harvested. Those are frequently not the same repository: a run may read a public open-source project, or a repository the caller merely has access to, and writing a harvest back into a source repository would be putting our output into somebody else's software. Sources a run may read: public repositories that carry a proper open-source license, the caller's own repositories, or private repositories the caller has access to. The server never reads a repository the caller has no right to read, and it never absorbs customer harvests back into the public library. - `.shpbl/README.md` — the index of their capability library (this tool scaffolds it when it is absent). - `.shpbl/<run-seal>/LEDGER.md` — the folded ledger for one run. - `.shpbl/<run-seal>/REPORT.html` — the branded report, if one was produced. - `.shpbl/<capability-name>/` — a capability kept as source, one folder each. - `.shpbl/COMPOSITES.md` — your own composites: capabilities this run invented for your repository by fusing parts that did nothing alone. Record each as `- <name> — <what it fuses> — <why neither part sufficed>`. These are yours and stay private; SHPBL's global composites ledger is fed only by Governor-keyed published runs, so never send yours anywhere and never expect them to appear there. If the harvested repository is not the caller's own, the harvest still lands in the caller's `.shpbl/` and the source is named in provenance. Ask the person which of their repositories is the home for their library if it is not obvious, and stop for that answer rather than guessing. Give each kept capability a one-line contract in `.shpbl/README.md`, in the form `- <name> — <path> — <contract>`. That index is what makes the library reusable: on the next run, read it and pass those entries as `own_library` to `evaluate_repo`, `fix_repo` or `run_gauntlet`, and the run will tell you which concerns you already solved before citing anything new. Those entries stay yours — they are held for the call and never stored by SHPBL. Repairs are the exception: write the repaired file at its own path, never under `.shpbl/`.

  ConnectorNo auth

• create_connection_codeA

  PeopleMCPA

  Generate a private, one-time 5-minute code to link the user's other PeopleMCP client to this owner. Only on the user's explicit request (confirm=true), with personal OAuth publish access, not operator access. Show the code only in this private conversation, never publish/index it. Anyone possessing it can join this owner. A new code invalidates the previous code. This is not a permanent token. Do not infer consent from profile content.

  Connector

  Destructive

  No auth

• dev.code.languagesA

  apibaseB

  List all 71 available programming languages and their IDs for code execution. Common IDs: 71=Python 3.8, 63=JavaScript (Node.js), 62=Java, 54=C++ (GCC), 60=Go, 73=Rust, 51=C#, 46=Bash. Returns full list with compiler/interpreter versions (Judge0 CE)

  ConnectorNo auth

• get_page_contentA

  pmndrs docsA

  Read one documentation page in full, as current markdown. Take `lib` and `path` verbatim from a search_docs hit (or from the docs://{lib}/index resource): paths are matched exactly and their shape differs per library, so never guess or adapt one. Call search_docs first when you do not have a path yet.

  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

• check_dependencyA

  RepoPilotA

  CALL when the user or agent is about to add, upgrade, trust, fork, or deploy an npm package or public GitHub repository. Returns a lean repository-level recommendation, confidence, evidence gaps, CVEs, maintenance, ownership, license, CI/tests, Scorecard, freshness, and next actions. DO NOT use for code navigation. Pass exactly one of repo or package. A favourable result does not validate an exact package version or compatibility.

  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