"A version control system for managing code" matching MCP tools:

• get_verifierA

  GoodeyeA

  Read a verifier's full definition (criterion, calibration examples, judge config); user-scoped verifiers only. ``verifier_id`` accepts a verifier UUID string or an accessible user-scope name. Any caller who can reach the verifier can read it: the owner, and skill grantees at any role (a view/exec grantee can read, not only run). Platform ``system:...`` aliases and system verifier UUIDs are never returned (NotFound): system rows are run-only and their internal config never surfaces through list, get, deploy, or revoke. Defaults to the current version; pass ``version`` to pin. Returns the full deploy-time payload (``criterion``, ``input_contract``, ``input_fields``, ``few_shot_examples``, ``judge_model_config``, ``reasoning_field_description``) plus ``config_hash`` (canonical-JSON SHA-256 over the config) so callers can detect drift across versions. A verifier you have no access to (and any revoked one) surfaces as NotFound. Platform-managed verifiers are run-only and never returned here.

  ConnectorOAuth

• linux_auditA

  ZEN SecDBA

  Perform a Linux package vulnerability audit using SecDB. ## What this tool does Analyzes the installed packages of a Linux system-identified by OS and OS version-and returns vulnerability information plus a Markdown summary. The audit results are based exclusively on the package list provided by the user. ## When to use this tool Use this tool when the user wants to determine: - whether installed packages contain known vulnerabilities - whether a host, VM, container, or base image is affected by security advisories - which packages require patching or upgrading If the user does not know the valid values for `os` or `version`, first call the `linux_os` tool to retrieve the exact supported combinations. ## Inputs - **os**: Linux distribution identifier supported by SecDB (use `linux_os` to obtain allowed values). - **version**: OS version or codename corresponding to the selected distribution. - **packages**: list of installed packages, **one per line**, generated using the appropriate system command: ### For RPM-based distributions (RHEL, CentOS, Rocky, Alma, SUSE) rpm -qa --qf '%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}\n' ### For DEB-based distributions (Ubuntu, Debian) dpkg-query -W -f='${Package} ${Version} ${Architecture}\n' ### For Alpine Linux apk list -I The raw output of these commands can be passed directly as the `packages` input (one package per line). ... python3 3.12.3-0ubuntu2.1 amd64 systemd 255.4-1ubuntu8.10 amd64 tmux 3.4-1ubuntu0.1 amd64 ... ## Outputs - **report**: structured objects describing the advisories affecting the audited packages. - **summary**: Markdown summary including total vulnerabilities, severity breakdown, and key findings. ## LLM usage guidelines - Never guess whether a package is vulnerable-always call this tool for Linux audits. - If `os` or `version` is unclear or missing, call `linux_os` and ask the user to choose a valid combination. - Normalize the package list to “one entry per line” if the user provides unstructured output. - The `summary` is already Markdown and can be shown directly. - Use `report` when deeper technical analysis is required.

  ConnectorNo auth

• medcode_get_codeA

  medical-codes-mcp-serverA

  Decode one or more US medical codes to their official descriptions across ICD-10-CM (diagnoses), ICD-10-PCS (inpatient procedures), HCPCS Level II (supplies/drugs/services), and RxNorm (drugs, by RXCUI). Also decodes a National Drug Code (NDC) directly to its RxNorm product offline, tagged `source: "NDC"` — hyphenated in an FDA segment configuration (4-4-2, 5-3-2, 5-4-1, or the 11-digit 5-4-2) or as bare 10/11 digits; any other segment widths are malformed and stay unresolved. Auto-detects the system from each code's shape; pass an explicit `system` only when a value is genuinely ambiguous. Accepts 1–50 codes and returns partial success: resolved codes in `found`, unresolved in `notFound` with a per-code reason, so one bad code never fails the batch. Set `includeHierarchy` to attach each code's parent and immediate children (with a `childrenTruncated` flag when a code has more children than the cap returns — walk the full set via medcode_browse_hierarchy or medcode_map_codes). The resolved `system` is echoed on every result for chaining into medcode_map_codes or a billability check; a code string that also exists in another bundled system carries `alsoInSystems` naming it, so a single answer to a colliding code is never mistaken for the only one.

  ConnectorNo auth

• goods_classifyA

  banking-intelligenceA

  Classify goods for export control from a description (or HS code). Bilingual (English / Russian, auto-detected) goods classifier. Returns the best-matching HS code (with EN+RU descriptions), related ECCNs, control reasons (NS, MT, NP, CB, AT...), an export-control level (high/medium/low/ none), a confidence score, and alternative matches for review. This is destination-agnostic — it identifies WHAT the goods are and whether they are controlled in principle. To get the license decision FOR A SPECIFIC destination, pass the result into export_controls_screen. IMPORTANT, the matcher is lexical, and confidence scores the strength of the string match, not the correctness of the classification: "equipment" returns semiconductor manufacturing equipment at confidence 1.0. Treat the code as a suggestion for narrowing the question. When no hs_code was supplied the result carries classification_basis and classification_confidence_note; read them before quoting any code, and ask the user for the HS code or ECCN on their shipping documentation. Args: description: Goods description, min 2 chars (e.g. "uranium centrifuge", "центрифуга для урана"). Required. hs_code: Optional known HS code (4 or 6 digits) for a direct lookup. language: Optional hint — "en" or "ru" (auto-detected if omitted). Examples: goods_classify("uranium centrifuge") # → HS 840120, ECCN 0B001 goods_classify("центрифуга для обогащения урана") # Russian query, same result goods_classify("semiconductor manufacturing equipment") goods_classify("", hs_code="840120") # direct HS lookup Use case: 'Is a semiconductor lithography machine export-controlled?'

  ConnectorNo auth

• whoamiA

  shiplyA

  Who am I? Returns the signed-in account: email, @handle, plan + limits, counts of sites/domains/drives, and connected DNS providers. Call this first to orient before managing sites or domains.

  ConnectorNo auth

• delete_skill_versionA

  GoodeyeA

  Permanently and immediately erase a single non-current skill version. This is permanent: the version row, all its attached files, and any content that is no longer referenced by any surviving version or published template version are removed from the live system at once. There is no recovery path. Use ``archive_skill`` if you want a reversible alternative for the whole skill. Encrypted backups age out within the platform's standard retention window (up to three months), so the data is not instantly erased from all systems everywhere, but it is no longer accessible through any product surface after this call. The current (live) version cannot be erased with this call. Use ``delete_skill`` to permanently remove the entire skill including its current version. Version numbers remain monotonic with a gap where the erased version was. Surviving versions are not renumbered. Owner only. Pointing at another user's skill raises NotFound.

  Connector

  Destructive

  OAuth

• get_law_articleA

  justicelibreA

  Renvoie le texte d'un article de loi à une date donnée (ou version actuelle si `date` vide). Particularité justicelibre : quand une décision de 1992 cite l'article 1128 du Code civil, l'article a été totalement réécrit en 2016. Avec ce tool on récupère le texte **tel qu'il existait en 1992** (l'ancienne version napoléonienne), pas le texte actuel. Codes/textes supportés : ~80 sigles courts — les grands codes (CC, CP, CPC, CPP, CT, CSP, CJA, CRPA, CSS, COJ, CGFP, LPF, CSI, CSport…), la Constitution (CONST) et des lois non codifiées (LIL, LO58, L2005-102). Liste complète : resource `justicelibre://codes-supportes`. Pour tout autre texte (loi, ordonnance, décret), passer un identifiant LEGITEXT/JORFTEXT direct — `resolve_law_number()` le trouve depuis un numéro ("78-17" → JORFTEXT…). Args: code: code court (ex : "CC" pour Code civil, "CT" pour Code du travail) num: numéro de l'article (ex : "1128", "L1152-1", "132-1") date: date ISO YYYY-MM-DD (optionnel — si absent, version en vigueur). Utiliser la date de la décision citante pour obtenir la version contemporaine de la citation. Returns: dict avec `legiarti`, `num`, `code`, `titre_texte`, `texte`, `etat` (VIGUEUR/MODIFIE/ABROGE), `date_debut`, `date_fin`, `nota`. Plus un champ `note` si la version retournée n'est pas celle demandée. `titre_texte` est le titre du TEXTE parent (« Code civil ») ; `titre_section` est le dernier niveau du plan du code (« Chapitre Ier : La responsabilité extracontractuelle en général »), servi depuis la ré-ingestion du 10 septembre 2026 (colonne `hierarchie`) et mesuré juste sur 30 articles de 30 codes le 13 septembre 2026. Le plan complet (partie / livre / titre / chapitre / section) n'est pas encore servi : ne pas l'inventer, renvoyer vers Légifrance s'il est demandé.

  ConnectorNo auth

• search_legal_textsA

  LibreJusticeA

  Find legal articles from their subject or wording when the article number is unknown; returns a ranked shortlist with highlighted snippets and the exact `total`. Query in French, descriptive terms (« délai de recours contentieux refus implicite »); put the code in the `code` filter (slug or exact name), keep the query for the subject. The response carries a `facets` block (`code`, `jurisdiction`): per filter name, a map of filter value to article count, reuse those keys verbatim to refine. Chain a hit into get_legal_text with its `url`, plus `date` when the dispute is governed by an earlier version.

  ConnectorOAuth

• explain_reason_codeA

  Export ControlA

  Expand a reason-for-control code such as NS, AT or CB into its full name. Use this when reading a Control List entry or a chart column and the two-letter code is not obvious. Returns the code and the name it stands for, or the whole glossary when called with no argument. This is a glossary lookup only: it reports what a code means, never whether that control applies to anything you are shipping, and it cannot tell you whether a licence is required.

  ConnectorNo auth

• get_resource_schemaA

  Control PlaneA

  Return the exact object schema and REST API endpoints for a Control Plane resource kind, so you can author an accurate manifest for `cpln apply` or call the API directly. ALWAYS call this FIRST whenever you are about to write a cpln apply YAML/JSON file, set up CI/CD that applies Control Plane resources, or build a request body for the REST API — do not hand-write a manifest or guess field names from memory. Pick a `kind` and pass `org` (and `gvc` for workload/identity/volumeset). Large schemas come back as a shallow map with deep sections collapsed to {"_expand":"<path>"} stubs; pass `path` (e.g. "spec.containers") to expand a section on demand. Server-managed fields (id/status/version/etc.) are already removed; `name` and `kind` are required at create.

  ConnectorOAuth

• get_componentA

  TsehaA

  Returns the full specification for one component: import path, props schema, usage example, anti-patterns, when-to-use and when-not-to-use notes, Figma spec, and dependencies. Read-only. Call it before writing code that uses a component, so props and import path come from the design system instead of memory. The name argument must be the exact component name as returned by list_components or search_components (case-sensitive, no package prefix); an unknown name returns a not-found error rather than a near match, so resolve the name first with search_components if you are guessing. The result may carry a provenance warning when the record was LLM-generated and not yet reviewed - treat those fields as unverified. It covers one component at a time; use list_components to enumerate and get_component_updates for version-to-version changes.

  ConnectorNo auth

• get_billing_portalA

  BorealHostA

  Get a Stripe billing portal URL for managing payment methods and invoices. Returns a URL (not a redirect) that the human can open in a browser. Requires: API key with read scope. Args: flow: Optional. Set to "payment_method_update" to go directly to the payment method update page. Returns: {"url": "https://billing.stripe.com/p/session/..."}

  ConnectorNo auth

• huntA

  SpaceMoltB

  Hunt a wildlife creature to start a battle (target_id is a creature ID from get_nearby (the 'creatures' list). Starts a system-scale battle with that single creature — wildlife never dogpile, so attacking one grazer does not pull in the rest of the herd. Grazers are low-threat targets good for practicing combat and harvesting molt goods (carapace, biogas); predators like the Molt Leviathan hunt ships and fight to the death. Killing a creature drops a carcass wreck you can loot. Equivalent to 'attack' on a creature ID. Use the 'battle' command for tactical control once engaged.)

  ConnectorNo auth

• list_release_note_inputsA

  ALM X++ MCP ServerA

  WHEN: ALWAYS call this FIRST, before prepare_release_note_context -- it discovers the exact D365FO version strings and custom model ids actually indexed on THIS server, which you cannot guess. Triggers: 'release note', 'compare D365 versions', 'upgrade impact for a client', 'what changed for this client', 'regression risk', 'note de version'. Returns every indexed version (exact 'version' string to use as v1/v2, e.g. 10.0.2527.109) and every ready-to-use custom model (exact 'id' to use as customModelIds, plus its name and optional clientGroup tag -- models sharing the same clientGroup belong to the same client and should usually ALL be passed together, e.g. the client's own extensions AND a separate ISV vendor model). IMPORTANT: this server holds the ACTUAL indexed code diff and the client's ACTUAL custom code -- generic Microsoft Learn / Azure Updates / documentation-search tools do NOT have this data and must NOT be used for D365 F&O release-note or upgrade-impact questions about a specific client; those tools only know public, generic release notes, not this client's real regression/opportunity picture.

  ConnectorNo auth

• validate_artifactA

  Verificate MCPA

  Deterministic production-readiness gate for AI-built systems. Verifies the invariants that stop a system silently shipping broken: every critical component is PRESENT and LOADS, the import closure resolves (nothing assumed 'already on the box'), all runtime dependencies are declared, and health is a REAL fail-closed check. Returns approve/reject with a fix plan and ISO 27001 / ISO 5055 control evidence. Facts are gathered by the Verificate collector in your CI; the gate is the authority. Non-bypassable, fails closed. This is the control-plane sibling of validate_ai_output — code quality is one invariant; this gates the whole deployable.

  ConnectorNo auth

• findagent_reintrospect_mcpA

  FindAgentA

  Publish a NEW version of YOUR OWN published EXTERNAL MCP-server listing by RE-INTROSPECTING its remote endpoint. FindAgent re-lists the remote server's current tools (over a sandbox-gated, SSRF-hardened scan), compares them to your live listing, and — if the tool surface CHANGED — submits a new version for admin review with an auto-drafted changelog. Your LIVE listing keeps serving until the new version is approved (never auto-unpublished). If the tools are unchanged it is a no-op. If your server has started REQUIRING AUTHENTICATION, the tools can't be re-listed but the listing's 'needs your own credentials' disclosure is corrected in a new version, with your tool list left unchanged. If the remote can't be reached or the scan is unavailable, nothing changes (reported back). Pass the listing slug (you must own it); optional bump (patch|minor|major, default patch) + changelog override. The server URL is read from your stored listing — nothing executes on FindAgent. Owner-only; for external mcp-server listings only (code agents use the code wizard, doers use findagent_bump_version).

  ConnectorOAuth

• findagent_repullA

  FindAgentA

  Publish a NEW version of YOUR OWN published CODE-BUNDLE or SKILLS-BUNDLE agent by RE-PULLING your OAuth-connected GitHub repo. FindAgent re-fetches your repo (at an optional branch/tag/commit ref, default = the latest commit on your stored branch), re-snapshots + re-scans it (a code bundle also re-builds), diffs it against your live version, and — if it CHANGED — submits a new version for admin review with an auto-drafted changelog. Your LIVE version keeps serving until the new one is approved (never auto-unpublished). If the source is unchanged it is a no-op. Pass the agent slug (you must own it) + optional ref. Owner-only; the repo is pinned to your agent's own prior import (arbitrary-repo ingest is not available here). VERSION NUMBER: the new version is computed from the LISTING's current version plus `bump`, NOT from any `version` in your repo (package.json / manifest) — the listing owns its own version line, so hand-editing a version in the repo does not change what gets published here, and the two can legitimately differ. For code-bundle / skills-bundle only — doers/recipes re-version via findagent_bump_version, external mcp-server listings via findagent_reintrospect_mcp.

  ConnectorOAuth

• deploy_image_generatorA

  GoodeyeA

  Deploy a reusable image generator that skills reference to produce images from a chosen model: creates it or appends a version. An image generator is a named, versioned configuration that routes image generation calls to a specific model. Generators are private and owner-scoped. Skills reference them by UUID or ``uuid@version``. You cannot deploy a new generator whose ``name`` matches an active platform ``scope=system`` generator (those are tier-level configs that are run-only and not listed or fetched). Versioning: the first deploy with a given ``name`` creates the generator at version 1. Re-deploying the same ``name`` appends a new version and requires ``expected_version_token`` from the latest known version (returned by deploy/list/get). A new generator must omit the token; an existing one without a token returns Conflict. Deploy-time validation: the ``model`` is checked against the pricing layer. A model that does not resolve to a known image endpoint with an authoritative price is rejected before any row is written. Returns: ``{generator_id, name, description, current_version, version, version_token, status, scope, provider, model, generation_contract, config_hash, created_at}``. Persist ``version_token`` for the next re-deploy.

  ConnectorOAuth

• get_image_generatorA

  GoodeyeA

  Inspect one image generator you own (its model and full config) at head or a pinned version. ``generator_id`` accepts a UUID string. Platform ``system:...`` tier aliases and system generator UUIDs are not returned here (NotFound): system generators are run-only and their internal config never surfaces through list, get, deploy, or revoke. Defaults to the current version; pass ``version`` to pin. Returns the full deploy-time payload (``provider``, ``model``, ``generation_contract``, ``default_params``) plus ``config_hash`` (SHA-256 over the config) so callers can detect drift across versions. Requires ownership; a cross-user or revoked generator surfaces as NotFound.

  ConnectorOAuth

• delete_template_versionA

  GoodeyeA

  Permanently and immediately erase a single template version. This is permanent: the version row, all its attached files, all version verification records, and any content no longer referenced by any surviving version or skill version are removed from the live system at once. There is no recovery path. Use ``archive_template`` if you want a reversible alternative for the whole template. Encrypted backups age out within the platform's standard retention window (up to three months), so the data is not instantly erased from all systems everywhere, but it is no longer accessible through any product surface after this call. Serving gate: the version must first be unpublished (``unpublish_template_version``) before it can be erased. A still-published version cannot be permanently deleted because it is currently being served to readers. Unpublish it first, then call this operation. To remove the entire template including all its versions, use ``delete_template`` instead. Version numbers remain monotonic with a gap where the erased version was. Surviving versions are not renumbered. Owner only. Pointing at another user's template raises NotFound.

  Connector

  Destructive

  OAuth

• check_skill_safetyA

  GoodeyeA

  Run both system safety verifiers against a saved skill version. Resolves a UUID or owner-scoped slug. Visibility mirrors ``get_skill``: owner or any active grant; cross-user pointers surface as not found. Defaults to the latest version. Bills two metered verifier runs against the caller. The combined ``status`` is one of ``clean``, ``flagged``, ``blocked``, or ``error``; per-side ``block`` and ``advisory`` carry the verifier id, version, run id, verdict, and reasoning.

  ConnectorOAuth