Alpaca Trading API integration for Model Context Protocol (MCP)
Nothing to run from here
Cork is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
16
tools declared
—
trust score
local
runs on your machine
—
calls last 7d
What it does
MCP server for Cork's cyber-insurance API for MSPs.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'CORK_API_KEY=${CORK_API_KEY}' --transport stdio cork-mcp '--' docker run -i --rm -e MCP_TRANSPORT=stdio -e CORK_API_KEY ghcr.io/wyre-ai/cork-mcp:v1.0.0
# 2 — ask your agent for something these tools do
# cork_get_client_domains, cork_get_client_inboxes, cork_get_client_score_history and 13 more
It needs CORK_API_KEY: this reads it from your environment, so export it first.
Cork costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
WAAll 82 servers
WYRE-AI82 servers
14 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Cork as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It has not been scanned here, so read the surface, and its source, before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Docker installed and running. Only the required variables are passed into the container. To set an optional one (AUTH_MODE, LOG_LEVEL), add -e NAME before the image name and give it a value in the entry’s env: an unset -e would clear the default the image sets. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads CORK_API_KEY (Cork API key (Bearer token, generated in Cork's Admin UI). It only ever holds a live bearer key) from your environment each time it starts the server, so the value stays out of its config: export it in your shell profile (macOS, Linux), or run setx CORK_API_KEY … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'CORK_API_KEY=${CORK_API_KEY}' --transport stdio cork-mcp '--' docker run -i --rm -e MCP_TRANSPORT=stdio -e CORK_API_KEY ghcr.io/wyre-ai/cork-mcp:v1.0.0Reconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own image: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
It reaches a system of yours, so it needs your own credential rather than the publisher’s: CORK_API_KEY — Cork API key (Bearer token, generated in Cork's Admin UI). It only ever holds a live bearer key.. You set it in your own client’s config, on your machine — this marketplace never holds it.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
16 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
No parameter schema on file.
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.
No parameter schema on file.
List a client
No parameter schema on file.
List policy violations and risk events detected for a client\
No parameter schema on file.
List the notification and alerting rules configured for compliance events on a client\
No parameter schema on file.
List all compliance event types with their descriptions and cure periods. Use to discover valid event_type values before filtering cork_get_compliance_events.
No parameter schema on file.
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.
No parameter schema on file.
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 -
No parameter schema on file.
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.
No parameter schema on file.
List devices observed from an integration - hostnames, IP addresses, device properties, and normalized OS details for devices that have been mapped.
No parameter schema on file.
List customer tenants observed from an integration.
No parameter schema on file.
List users observed from an integration.
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
List active cyber warranty packages. To identify which clients lack coverage, check the warranty_status field in cork_get_clients results - clients with
No parameter schema on file.
Get information on the authenticated Cork user (identity, role, and partner/distributor scope). Useful for a quick credential sanity check.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source is public; its licence metadata reads NOASSERTION rather than naming a licence
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Cork or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing ships as a container image. The scanner reads packages on npm and PyPI and public source; an image is neither, so there is no grade here — not a withheld one, an unmeasured one.
Release history
It installs from a container image rather than from a versioned package, so the command cannot be pinned to a release. The history below is for reading; the current release on file is v1.0.0.
v1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Cork can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.