Get a journey by ID. Pass version=draft to retrieve the working draft, or version=vN for a historical version. Defaults to published.
Connector
294,571 tools. Last updated 2026-07-13 13:31
"A version control system for managing code" matching MCP tools:
- Returns the MCP knowledge version: gitSha, indexedAt, componentCount, patternCount, uptimeSeconds. Call this ONCE per session before generating UI code so you know how fresh the design-system data is. Cheap to call. If gitSha is "unknown" or indexedAt is far in the past, surface that to the user before relying on the data.Connector
- Rollback a project to a previous version. ⚠️ WARNING: This reverts schema AND code to the specified commit. Database data is NOT rolled back. Use get_version_history to find the commit SHA of the version you want to rollback to. After rollback, use get_job_status to monitor the redeployment. Rollback is useful when a schema change breaks deployment.Connector
- Permanently and immediately erase a verifier you own (``scope=user`` only). ``verifier_id`` accepts a UUID string. This is permanent: the verifier, all its versions (criterion, calibration examples, input contracts), all run records, and all access grants are removed from the live system at once. There is no recovery path. Use ``revoke_verifier`` if you want to deactivate the verifier without erasing it, keeping the audit trail intact. 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: if any live published template version carries a snapshot that references this verifier, deletion is refused with a Conflict. Unpublish the relevant template version(s) first, then call this operation. Platform-managed (``scope=system``) verifiers and another user's verifiers always surface as NotFound. No confirmation token is required. Returns ``{verifier_id, name, deleted: true}``.Connector
- 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.Connector
- Returns the MCP knowledge version: gitSha, indexedAt, componentCount, patternCount, uptimeSeconds. Call this ONCE per session before generating UI code so you know how fresh the design-system data is. Cheap to call. If gitSha is "unknown" or indexedAt is far in the past, surface that to the user before relying on the data.Connector
Matching MCP Servers
- Flicense-qualityBmaintenanceEnables AI agents to monitor system resources and control media, brightness, volume, and other Windows PC functions through natural language commands.Last updated
- Flicense-qualityDmaintenanceProvides an intelligent, graph-based memory system for LLM agents using the Zettelkasten principle, enabling automatic note construction, semantic linking, memory evolution, and autonomous graph maintenance with background optimization processes.Last updated10
Matching MCP Connectors
Corporate travel: search and book flights, hotels, rail and transfers, manage orders.
Cloudflare Workers MCP server: code-explainer
- Paid tier only. Fetch a senior-QS skill methodology by slug (see list_skills) and APPLY it to the user's documents — the returned body is the system instruction for you to run the methodology on the customer's tokens; CivilQuants does not run inference. Paid callers get the full methodology; anonymous/free callers get a TIER_INSUFFICIENT upsell body; a rejected token gets an INVALID_TOKEN re-authenticate body. The document-heavy skills assume you can chunk/parse the customer's files and render a Word pack locally — that needs a code-execution client (Claude Code / Codex / VS Code) and the pack from get_document_pipeline; on a chat connector you can still read and reason with the methodology. Sign up at https://civilquants.com/pricing. Example: get_skill(skill="tender_risk_assessment").Connector
- Validate whether a US medical code exists, is current, and is billable in the active bundled release. Returns a discriminated status — valid_billable, valid_not_billable, valid_header, or terminated — with a `whyNot` explaining non-billable and terminated cases (e.g. "valid ICD-10-CM category but not billable — submit a more specific child code"). This is the detail a coder needs before submitting a claim. Auto-detects the system from the code's shape; pass an explicit `system` to disambiguate. A non-billable or terminated code is a successful result with a whyNot, not an error — only a code that exists in no bundled system raises unknown_code.Connector
- Deploy a reusable semantic verifier (an LLM-judge check workflows reference by id) that scores agent output against a criterion: creates it or appends a version. A semantic verifier is a single judgment ("does this output satisfy this criterion?") evaluated by an LLM judge. Verifiers are private and owner-scoped. Workflows reference them by ``verifier_id`` (or ``verifier_id@version``). You cannot deploy a **new** verifier whose ``name`` matches an active platform ``scope=system`` verifier: those definitions are server-owned, never listed or fetched, and only executable through ``run_verifier``. Versioning: the first deploy with a given ``name`` creates the verifier 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 verifier must omit the token; an existing one without a token returns Conflict. Input contracts: - ``text``: ``input_fields`` required, ``media_url`` rejected. - ``text_image``: ``input_fields`` plus ``media_url`` required at run time. - ``image``: ``input_fields`` empty, only ``media_url`` at run time. Few-shot examples (3 to 10 typical) calibrate the judge; each example must match the contract (text-only inputs, text+image, or image-only). Returns: ``{verifier_id, name, current_version, version, version_token, status, input_contract, config_hash}``. Persist ``version_token`` for the next re-deploy.Connector
- 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 workflow 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.Connector
- Deploy a reusable image generator that workflows 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. Workflows 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.Connector
- Restore an earlier artifact version (F5) to current and return the now-current version: the existing current version is flipped to 'reverted' (kept for the learning signal) and the chosen version becomes current again. A write — not idempotent, since re-running reverts again. version_id is the version you want to RESTORE; get it from list_artifact_versions and never guess it. Optional reason is recorded.Connector
- Retrieve the full GLEIF LEI record for one legal entity using its 20-character LEI code. Returns legal name, registration status, legal address, headquarters address, managing LOU, and renewal dates. Use this tool when: - You have a LEI (from SearchLEI) and need full entity details - You want to verify the registration status and renewal date - You need the exact legal address and jurisdiction of an entity Source: GLEIF API (api.gleif.org). No API key required.Connector
- List and keyword-search federal accounts by agency identifier or title keyword. Returns account numbers, names, managing agencies, and budgetary resources. Use account_number from results as input to usaspending_get_federal_account for full budget detail. Use usaspending_list_agencies to look up agency_identifier codes (3-digit strings, e.g. "097" for DoD).Connector
- 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) — hyphenated or 10/11-digit — directly to its RxNorm product offline, tagged `source: "NDC"`. 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. The resolved `system` is echoed on every result for chaining into medcode_map_codes or a billability check.Connector
- Permanently and immediately erase a single non-current workflow 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_workflow`` if you want a reversible alternative for the whole workflow. 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_workflow`` to permanently remove the entire workflow 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 workflow raises NotFound.Connector
- 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.Connector
- Catalog of every field the server can return, by tool tier (search card -> full profile -> full record), with code tables and availability/null rules. Read-only, no parameters. This describes the SCHEMA only (field names, types, code tables, null rules) so you can pick the right tool and interpret its output. It returns no company data itself; for that call search_companies (many) or get_company_details / get_full_record (one). Call this once up front when unsure what a field means or which tool to use. Human-readable version: https://www.agentic-firmenbuch.at/felder.htmlConnector
- List the Control Plane Template Catalog — production-ready stacks (Postgres, Redis, Kafka, MongoDB, nginx, …) you can install instead of hand-authoring resources. Returns each template’s name, category, latest version, and whether it creates its own GVC. Reach for this first whenever the user wants a database, cache, queue, or other common service. Pass `filter` to narrow. Then call get_template for versions and the example values.yaml.Connector
- Screen goods for export-control restrictions to a destination country. Combines the goods classification with the destination's restriction status and returns whether a license is required, the risk level, applicable license policies (e.g. presumption of denial), control reasons (NS, MT, NP, CB, AT), and proliferation/dual-use flags. Identify the goods by ANY of: ECCN, HS code, or a free-text description (English or Russian). IMPORTANT — jurisdiction nexus: each jurisdiction's controls only bind a payment/shipment when there is a nexus to that jurisdiction (US EAR binds US persons, USD-clearing, and US-origin items; EU/UK/JP bind their persons, currencies, and origin). Use jurisdiction="ALL" for a comprehensive multi-jurisdiction view, or pick the one matching the actual touchpoints. Args: destination_country: ISO 3166-1 alpha-2 destination code (e.g. "RU", "CN"). eccn: Optional Export Control Classification Number (e.g. "3A001"). hs_code: Optional Harmonized System code, 4-8 digits (e.g. "854231"). goods_description: Optional free-text goods description (EN or RU). jurisdiction: "US" (default), "EU", "UK", "JP", "ITAR", or "ALL". Provide at least one of eccn / hs_code / goods_description. Examples: export_controls_screen("RU", eccn="3A001") # electronics → Russia export_controls_screen("CN", eccn="3A090") # advanced computing → China export_controls_screen("IR", goods_description="industrial valves") export_controls_screen("RU", goods_description="drone", jurisdiction="ALL") export_controls_screen("DE", hs_code="854231") # → Germany (allied) Use case: 'Can we ship integrated circuits to Russia?'Connector