Cork MCP Server
OfficialRead-only Cork MCP server for querying cyber-insurance, risk/compliance, vulnerability, integration, warranty, invoice, distributor, and installer metadata through 23 tools.
List clients with warranty status, integration tenants, devices, domains, inboxes, and Cork Cyber Score history.
Query compliance events, notification settings, event types, and filter by client/device/inbox/domain/event/date/resolution.
Inspect CVE vulnerabilities and product rollups with CVSS/EPSS/KEV/priority filters.
Explore available and connected integrations plus their devices, tenants, and users.
View active warranties, invoices and line items, distributor partners, software installer history/packages/setup, and authenticated user identity.
Use pagination and scoped filters; all operations are read-only and exclude credentials, raw integration data, writes, and software-install dispatch.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Cork MCP Server show warranty status and cyber scores for all clients"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Cork MCP Server
MCP server for Cork's cyber-insurance API for MSPs - clients and their warranty/coverage status, Cork Cyber Score history, risk & compliance events, software vulnerabilities (CVE/CVSS/EPSS/KEV), connected integrations, invoices, distributor partners, and software-installer metadata - for AI assistants and the WYRE Conduit gateway.
Authentication
Cork authenticates with a static Bearer API key, generated in Cork's Admin UI (Settings -> API). Cork's OpenAPI spec also documents an OAuth2 flow for their own remote MCP server, but the underlying credential is the same API key - this connector never performs an OAuth dance, it only ever holds a live bearer key, sent as Authorization: Bearer <key> to Cork's API. In gateway mode the key arrives per-request via the X-Cork-Api-Key header; in local/stdio mode it's read once from CORK_API_KEY.
Related MCP server: TicketAI
Configuration
Env var | Description |
| Bearer API key issued by Cork's Admin UI. |
|
|
|
|
| When set, the HTTP transport requires a valid |
|
|
Request limits
HTTP request bodies are capped at 256 KiB (262144 bytes). After the
X-Gateway-S2Scheck (and, in gateway mode, theX-Cork-Api-Keypresence check, both 401) passes, aContent-Lengthabove the cap returns 413 with a JSON-RPC error; bodies withoutContent-Lengthare capped by the MCP SDK transport. Unauthenticated requests still get 401 first.tools/callarguments are capped at 10,000 elements (every array item and object key at any depth). Larger inputs return anisErrortool result and are never dispatched.
These limits address CVE-2026-111768 / GHSA-46jr-4wx8-v453 (memory exhaustion during validation) and GHSA-f897-62hf-6gxq (no request body / batch cap).
Tools
Clients
cork_get_clients- list clients with warranty status, integration tenants, and recent Cork Cyber Scores.cork_get_client_devices- list devices observed for a client across all connected integrations.cork_get_client_domains- list email domains observed for a client.cork_get_client_inboxes- list email inboxes observed for a client.cork_get_client_score_history- list a client's full Cork Cyber Score history, newest first.
Risk & Compliance
cork_get_compliance_events- list policy violations and risk events detected for a client's assets.cork_get_compliance_notification_settings- list notification/alerting rules for compliance events.cork_get_compliance_event_types- list all compliance event types with descriptions and cure periods.cork_get_software_vulnerabilities- list individual CVEs with CVSS/EPSS/KEV details.cork_get_software_vulnerability_summary- get a rollup of CVEs grouped by software product.
Integrations - read-only subset
cork_get_available_integrations- list integration types that can be connected to Cork.cork_get_connected_integrations- list integrations connected to Cork.cork_get_integration_devices- list devices observed from an integration.cork_get_integration_tenants- list customer tenants observed from an integration.cork_get_integration_users- list users observed from an integration.
Warranty
cork_get_warranties- list active cyber warranty packages.
Invoice
cork_get_invoices- list billing invoices.cork_get_invoice_line_items- list billed line items for an invoice.
Distributor - read-only subset
cork_get_partners- list partner sub-accounts managed by this distributor.
Software Installer - read-only subset
cork_get_installer_history- list past software install attempts.cork_get_software_packages- list software packages available to install.cork_get_installer_setup- get one-time RMM setup instructions for software installs.
Who
cork_who_am_i- get information on the authenticated user.
Scope
This is a deliberately narrow, read-only, non-credential-exposing v1 surface, hard-scoped to exactly 23 of Cork's 31 operations (29 documented paths). Every tool is classified isAdmin: true in the Conduit gateway given the sensitivity of insurance/risk/compliance data. Roughly a third of Cork's full API is write- or secret-exposing; none of it is implemented here, by design, not by oversight:
Hard-excluded (credential-exposing) - never implemented:
GET /integrations/{uuid}/credentials(get-integration-credentials) - returns the integration's raw stored third-party secrets (credentials: {...}).
Hard-excluded (bulk raw-data exfiltration, excluded out of caution alongside credentials):
GET /integrations/{uuid}/raw-data(get-integration-raw-data) - returns a presigned download URL (10-minute expiry) to a client's full raw synced integration data. Not a credential return, but a bulk-data-exfiltration vector gated by "requires distributor privileges" in Cork's own spec. Flagged explicitly for review in the wiring PR rather than silently included.
Hard-excluded (provisioning/mutation) - never implemented:
POST /distributor/partners(provision-partner) - provisions a new Partner account.POST /integrations(connect-integration) - connects a new integration and immediately begins syncing data.PATCH /integrations/{uuid}(update-integration) - updates an integration's name and/or credentials.DELETE /integrations/{uuid}(delete-integration) - deletes an integration.POST /integrations/{uuid}/resync(resync-integration) - manually triggers a data refresh.POST /software/installer/install(install-software) - dispatches a real software install to a real managed endpoint through the client's RMM. A genuine remote-software-provisioning action.
They can be added as a follow-up if there's demand, after a deliberate scope decision - not by default.
Credential scope
This connector's own code is read-only by construction — the underlying API key is not. Cork's own documentation states API key permissions are linked to the user who creates them; no read-only or restricted-scope key type is documented. Two separate claims, kept at different confidence levels:
Structurally verified (checked directly, stated with full confidence): this connector's own code makes zero write/delete/resync/provisioning calls, and never calls the credentials or raw-data endpoints. Every function in
client.tscalls one of the 23 documented read operations above — no wildcard/passthrough call anywhere insrc/.Vendor-documented, not independently verified (hedged deliberately): Cork's own docs do not describe any narrower or read-only API key type. A key generated by a full-access Cork user can very likely reach the write/delete/credentials/raw-data operations this connector excludes — this has not been tested against a live key, and WYRE found no vendor-offered way to restrict it further at the credential level.
Do not read this connector, or this README, as having established the underlying API key is itself restricted — only that this connector's own code never attempts anything beyond its 23 read operations.
Development
npm install
npm run build
npm test
npm run lint # tsc --noEmitDocker
docker build -t cork-mcp .
docker run -p 8080:8080 -e CORK_API_KEY=... cork-mcpAvailable Tools
23 toolscork_get_available_integrationsA
List integration types that can be connected to Cork, including required credential fields. Metadata about what CAN be connected, not what IS connected - see cork_get_connected_integrations for that.
Inputs: page, page_size, vendor_type.
cork_get_client_devicesA
List devices observed for a client across all connected integrations - hostnames, IP addresses, the integration each device was seen in, whether the device can receive a future install dispatch (can_install_software), normalized OS details, resolved device type, and hardware model. Device UUIDs can be used to filter cork_get_software_vulnerabilities. Requires a client UUID from cork_get_clients.
Inputs: client_uuid (required), page, page_size.
cork_get_client_domainsA
List email domains observed for a client. Domain UUIDs can be used to filter cork_get_compliance_events. Requires a client UUID from cork_get_clients.
Inputs: client_uuid (required), page, page_size.
cork_get_client_inboxesA
List email inboxes (users and shared mailboxes) observed for a client, with inbox type, associated domains, and the integration each inbox was sourced from. Requires a client UUID from cork_get_clients.
Inputs: client_uuid (required), page, page_size.
cork_get_clientsA
List clients with their financial protection status (warranty_status), associated integration tenants, and the 10 most recent Cork Cyber Scores (newest first). For older scores or a bounded date range, use cork_get_client_score_history. Client UUIDs from this response are required by cork_get_client_devices, cork_get_client_inboxes, cork_get_client_domains, cork_get_compliance_events, and the vulnerability tools. If the API user is a distributor, pass partner_uuid to scope results to a specific partner.
Inputs: page, page_size, show_hidden, partner_uuid.
cork_get_client_score_historyA
List a client's full Cork Cyber Score history, newest first, with the risk points each category (coverage, compliance, vulnerabilities, claims) deducted from that score. Use created_after/created_before to bound a period (both inclusive) for trend reporting - cork_get_clients only carries the 10 most recent scores. Requires a client UUID from cork_get_clients.
Inputs: client_uuid (required), page, page_size, created_after, +1 more.
cork_get_compliance_eventsA
List policy violations and risk events detected for a client's assets. Filter by event_type (use cork_get_compliance_event_types for valid values), device, inbox, or domain UUID. Use at_risk=true to show only currently active risks. Resolved events are excluded by default; set show_resolved=true to include them.
Inputs: client_uuid (required), page, at_risk, page_size, +10 more.
cork_get_compliance_event_typesA
List all compliance event types with their descriptions and cure periods. Use to discover valid event_type values before filtering cork_get_compliance_events.
Inputs: no named parameters.
cork_get_compliance_notification_settingsC
List the notification and alerting rules configured for compliance events on a client's assets - which event types trigger alerts and how they are routed.
Inputs: client_uuid (required), page, page_size, inbox_uuid, +2 more.
cork_get_connected_integrationsA
List integrations connected to Cork - vendor, connection status, and sync details. RMM integrations also carry an installer block describing whether software installs can run through them (capable, requires_manual_setup, authorized, configured_package_managers). Use with cork_get_client_devices to see which integration a device is mapped through. Discovers integration UUIDs needed by cork_get_integration_devices, cork_get_integration_users, and cork_get_integration_tenants.
Inputs: page, page_size, partner_uuid.
cork_get_installer_historyA
List past software install attempts (most recent first) with dispatch state, target client/device, package, and any errors. Filter by client_uuid or device_uuid. state is one of queued, running, success, partial, error - 'success' means the RMM accepted the job, not that the on-device install finished.
Inputs: page, page_size, client_uuid, device_uuid, +1 more.
cork_get_installer_setupA
Get the one-time setup steps for an RMM vendor that requires manual setup before software installs work - the script to create in the RMM, its exact name, settings to match, and variables to declare. Use when a connected integration shows installer.requires_manual_setup=true (and the package manager is missing from installer.configured_package_managers).
Inputs: vendor_key (required), package_manager_key (required).
cork_get_integration_devicesB
List devices observed from an integration - hostnames, IP addresses, device properties, and normalized OS details for devices that have been mapped.
Inputs: integration_uuid (required), page, page_size, tenant_uuid.
cork_get_integration_tenantsB
List customer tenants observed from an integration.
Inputs: integration_uuid (required), page, page_size, tenant_uuid.
cork_get_integration_usersB
List users observed from an integration.
Inputs: integration_uuid (required), page, page_size, tenant_uuid.
cork_get_invoice_line_itemsA
List billed, top-level line items for an invoice (obtained via cork_get_invoices). Only items with a nonzero total billed are returned; discount line items are included and carry a negative total_billed. Sub-items billed as part of a parent line item (e.g. individual licenses within a bundle) are nested under that item's children field, and always carry a total_billed of 0 since their amount is rolled into the parent.
Inputs: invoice_uuid (required), page, page_size.
cork_get_invoicesA
List billing invoices. Returns invoice UUIDs required by cork_get_invoice_line_items. If the API user is a distributor, pass partner_uuid to scope results to a specific partner.
Inputs: page, page_size, partner_uuid.
cork_get_partnersA
List partner sub-accounts managed by this distributor. Returns partner UUIDs that can be passed as partner_uuid to cork_get_clients and other tools to scope results to a specific partner. Distributor accounts only.
Inputs: page, page_size.
cork_get_software_packagesA
List software packages available to install across supported package managers (WinGet, Chocolatey). Filter by package_manager_key or search (substring match against name/publisher). Returns package_id values that would be used by a future install dispatch - this connector does not implement software install itself.
Inputs: page, search, page_size, package_manager_key.
cork_get_software_vulnerabilitiesA
List individual software vulnerabilities with full CVE details including CVSS score, EPSS score, KEV (known exploited) status, and impacted version. Filter by minimum_cvss_score, minimum_epss_score, minimum_priority, or only_known_exploited=true to focus on the highest-risk findings. Scope by client_uuid or device_uuid.
Inputs: page, sort_by, page_size, sw_vendor, +8 more.
cork_get_software_vulnerability_summaryA
Get a rollup of CVEs grouped by software product, showing number of impacted devices, impacted versions, and highest severity rating. Use client_uuid to scope to a single client. Follow up with cork_get_software_vulnerabilities to drill into specific CVEs for a product.
Inputs: page, sort_by, page_size, sw_vendor, +3 more.
cork_get_warrantiesB
List active cyber warranty packages. To identify which clients lack coverage, check the warranty_status field in cork_get_clients results - clients with 'unwarranted' status have no active warranty.
Inputs: page, page_size, partner_uuid.
cork_who_am_iA
Get information on the authenticated Cork user (identity, role, and partner/distributor scope). Useful for a quick credential sanity check.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 23 tools
Each tool maps to a distinct resource or sub-resource, and descriptions consistently call out the required parent UUIDs (client, integration, invoice) that scope related queries. The only real near-overlap is cork_get_client_devices vs. cork_get_integration_devices, but their client-scoped vs. integration-scoped purposes are clearly explained.
22 of 23 tools follow the same cork_get_<resource> snake_case pattern, making the naming highly predictable. cork_who_am_i is the single outlier and breaks the verb_noun convention, but it is still recognizable and not confusing.
With 23 tools, this server sits at the heavy end of what an agent can comfortably scan. The breadth is defensible because the domain covers clients, compliance, vulnerabilities, integrations, billing, and installers, but several of these areas could have been consolidated.
The read-only surface is well connected: client UUIDs feed devices, inboxes, domains, and compliance; integration UUIDs feed integration subresources; and invoice UUIDs feed line items. Minor gaps exist, such as no claims endpoint despite the score history referencing claims, and no action-oriented tools like software install dispatch, but core query workflows are covered.
Maintenance
Related MCP Connectors
Stop copy-pasting client context into your AI. 48 connectable providers via MCP.
Build and run AI workflows, agents, data tables and 1000+ API integrations from any MCP client.
The Cortex MCP server provides read-only access to real-time engineering context from the Cortex developer portal, allowing AI coding assistants to answer natural language questions about your organization's catalog (microservices, libraries, domains, teams, infrastructure), scorecards (engineering standards and best practices), initiatives (goals and deadlines), and Engineering Intelligence metrics. It includes tools for querying documentation, tracking personal entities, and accessing AI-assisted insights across the entire Cortex ecosystem.
Zero-setup MCP gateway securely connecting AI to your tools with authentication and workflows
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI-powered customer support with real-time access to CRM, ticketing, and communication tools via MCP, supporting context-aware conversations and automated actions.Apache 2.0
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to analyze IT support tickets, categorize urgency, suggest responses, and retrieve statistics via MCP tools.-
- AlicenseAqualityBmaintenanceEnables AI assistants and the WYRE Conduit gateway to access Telivy's security assessment data for MSPs, including external scans, deep-scan risk assessments, device inventory, M365/Google Workspace user exposure, PII summaries, and finding-level details.16Apache 2.0
- AlicenseBqualityBmaintenanceProvides read-only visibility into Gorelo PSA data, enabling AI assistants to query tickets, clients, contacts, contracts, assets, and time entries through MCP tools.90Apache 2.0