io.github.GeiserX/spinnaker-mcp
OCI · DRUMSERGIO/SPINNAKER-MCP:V0.3.2 · 2 COMPONENTS · SCANNED SEP 20
MCP server exposing Spinnaker CD platform via Gate API for pipeline and deployment management
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- Malware scan not yet available for this package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency35
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 149 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 3267 tokens (~88/item across 37 items; 37 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 37 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the io.github.GeiserX/spinnaker-mcp server?
io.github.GeiserX/spinnaker-mcp runs locally as a container image, launched with docker run --rm -i drumsergio/spinnaker-mcp:v0.3.2. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · drumsergio/spinnaker-mcp:v0.3.2
claude mcp add geiserx-spinnaker-mcp -- docker run --rm -i drumsergio/spinnaker-mcp:v0.3.2
{
"mcpServers": {
"geiserx-spinnaker-mcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"drumsergio/spinnaker-mcp:v0.3.2"
]
}
}
} {
"servers": {
"geiserx-spinnaker-mcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"drumsergio/spinnaker-mcp:v0.3.2"
]
}
}
} codex mcp add geiserx-spinnaker-mcp -- docker run --rm -i drumsergio/spinnaker-mcp:v0.3.2
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"geiserx-spinnaker-mcp": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"drumsergio/spinnaker-mcp:v0.3.2"
],
"enabled": true
}
}
} mcp_servers:
geiserx-spinnaker-mcp:
command: "docker"
args: ["run", "--rm", "-i", "drumsergio/spinnaker-mcp:v0.3.2"] {
"McpServers": {
"geiserx-spinnaker-mcp": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"drumsergio/spinnaker-mcp:v0.3.2"
]
}
}
} {
"mcpServers": {
"geiserx-spinnaker-mcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"drumsergio/spinnaker-mcp:v0.3.2"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 −3
- Stability: pass → 0.77 functional
- 18 Sept 26 +1
- Stability: 0.97 → pass security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 −3
- Stability: pass → 0.80 functional
- 11 Sept 26 +1
- Stability: 0.97 → pass security
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed oci/drumsergio/spinnaker-mcp:v0.3.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
cancel_execution ~78
Cancel a running pipeline execution by its ID, optionally providing a reason. Use this to stop a deployment in progress — for example, when a bad build was triggered. Does not roll back completed stages. Returns a confirmation message.
| Name | Type | Req | Description |
|---|---|---|---|
| execution_id | string | yes | Pipeline execution ID to cancel |
| reason | string | – | Human-readable reason for cancellation |
No output schema declared.
No examples provided.
delete_pipeline ~76
Permanently delete a pipeline configuration from Spinnaker. Use this only when a pipeline is no longer needed — this action cannot be undone. Does not affect past executions. Returns a confirmation message on success.
| Name | Type | Req | Description |
|---|---|---|---|
| application | string | yes | Application name as registered in Spinnaker |
| pipeline_name | string | yes | Pipeline name to delete |
No output schema declared.
No examples provided.
delete_strategy ~71
Permanently delete a deployment strategy configuration from Spinnaker. Use this only when a strategy is no longer needed — this action cannot be undone. Returns a confirmation message on success.
| Name | Type | Req | Description |
|---|---|---|---|
| application | string | yes | Application name as registered in Spinnaker |
| strategy_name | string | yes | Strategy name to delete |
No output schema declared.
No examples provided.
evaluate_expression ~89
Evaluate a Spring Expression Language (SpEL) expression against a pipeline execution context. Use this to inspect pipeline variables, stage outputs, or computed values during debugging. Dangerous patterns (reflection, class instantiation) are blocked for security. Returns the evaluated expression result as JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| execution_id | string | yes | Pipeline execution ID to evaluate against |
| expression | string | yes | SpEL expression string to evaluate |
No output schema declared.
No examples provided.
find_images ~125
Search for machine images (AMIs, GCE images, Docker images) available in Spinnaker for a given cloud provider. Use this to find images for a deployment or verify which image versions are available. Supports filtering by query string, region, and account. Returns JSON array of matching image objects.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Spinnaker account to filter images |
| provider | string | yes | Cloud provider (e.g. aws, gce, docker) |
| query | string | – | Search query to filter images |
| region | string | – | Cloud region to filter images |
No output schema declared.
No examples provided.
get_account ~62
Get details for a specific Spinnaker account by name, including its cloud provider type, permissions, and regions. Use this to verify account configuration or check permissions before deploying. Returns JSON with full account metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Spinnaker account name |
No output schema declared.
No examples provided.
get_application ~71
Get detailed information about a single Spinnaker application including its accounts, clusters, and custom attributes. Use this to inspect an application's configuration before modifying its pipelines or infrastructure. Returns JSON with application metadata, associated cloud accounts, and cluster details.
| Name | Type | Req | Description |
|---|---|---|---|
| application | string | yes | Application name as registered in Spinnaker |
No output schema declared.
No examples provided.
get_cluster ~100
Get details for a specific cluster in a Spinnaker application by account and cluster name. Use this to inspect server groups, load balancers, and instance counts within a cluster. Returns JSON with cluster metadata and its constituent server groups.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Spinnaker account name |
| application | string | yes | Application name as registered in Spinnaker |
| cluster_name | string | yes | Cluster name as shown in the Spinnaker UI |
No output schema declared.
No examples provided.
get_console_output ~128
Get the console output (boot log) for a specific compute instance. Use this to debug instance startup failures or inspect early boot messages. Requires account, region, and instance ID. Returns the raw console output text.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Spinnaker account name |
| instance_id | string | yes | Cloud provider instance ID (e.g., i-0abc1234def56789 for AWS) |
| provider | string | – | Cloud provider (e.g. aws, gce, kubernetes) |
| region | string | yes | Cloud region (e.g. us-east-1) |
No output schema declared.
No examples provided.
get_execution ~94
Get the full details of a single pipeline execution by its ID, including all stage statuses, outputs, variables, and timing. Use this to debug a failed deployment or inspect execution progress. Returns comprehensive JSON with per-stage results. Obtain the execution_id from trigger_pipeline, list_executions, or search_executions.
| Name | Type | Req | Description |
|---|---|---|---|
| execution_id | string | yes | Pipeline execution ID (UUID returned when triggering or from list_executions) |
No output schema declared.
No examples provided.
get_firewall ~91
Get details for a specific firewall rule (security group) by account, region, and name. Use this to inspect inbound/outbound rules and associated resources. Returns JSON with the firewall's full rule set and metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Spinnaker account name |
| name | string | yes | Firewall rule name |
| region | string | yes | Cloud region (e.g. us-east-1) |
No output schema declared.
No examples provided.
get_image_tags ~79
Get available tags for a Docker image repository registered in Spinnaker. Use this to list version tags before triggering a pipeline with a specific image tag. Returns JSON array of tag strings for the specified repository.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Spinnaker account name |
| repository | string | yes | Docker image repository (e.g. library/nginx) |
No output schema declared.
No examples provided.
get_instance ~107
Get details for a specific compute instance by account, region, and instance ID. Use this to inspect instance health, metadata, launch time, and cloud-specific attributes. Returns JSON with full instance details including health indicators.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Spinnaker account name |
| instance_id | string | yes | Cloud provider instance ID (e.g., i-0abc1234def56789 for AWS) |
| region | string | yes | Cloud region (e.g. us-east-1) |
No output schema declared.
No examples provided.
get_pipeline ~83
Get the full configuration of a specific pipeline by application and pipeline name. Use this to inspect pipeline stages, triggers, and parameters before triggering or modifying it. Returns the complete pipeline JSON definition including all stage configurations.
| Name | Type | Req | Description |
|---|---|---|---|
| application | string | yes | Application name as registered in Spinnaker |
| pipeline_name | string | yes | Pipeline name as shown in the Spinnaker UI |
No output schema declared.
No examples provided.
get_pipeline_history ~77
Get the version history of a pipeline configuration showing past revisions. Use this to audit changes to a pipeline or compare previous configurations. Returns JSON array of historical pipeline versions ordered by update time.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of history entries to return (default: 10) |
| pipeline_config_id | string | yes | Pipeline configuration ID |
No output schema declared.
No examples provided.
get_scaling_activities ~146
Get scaling activities for a server group in a Spinnaker cluster. Use this to audit recent auto-scaling events (scale-up, scale-down) and diagnose capacity issues. Returns JSON array of scaling activity records with timestamps, descriptions, and status.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Spinnaker account name |
| application | string | yes | Application name as registered in Spinnaker |
| cluster_name | string | yes | Cluster name as shown in the Spinnaker UI |
| provider | string | – | Cloud provider (e.g. aws, gce, kubernetes) |
| server_group_name | string | yes | Server group name (e.g., myapp-v001) |
No output schema declared.
No examples provided.
get_target_server_group ~177
Get a specific server group in a Spinnaker cluster using a target selection strategy (e.g., newest, oldest, largest, smallest, fail). Use this when you need the most recently deployed or a specific server group without knowing its exact name. Returns JSON with the matched server group details.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Spinnaker account name |
| application | string | yes | Application name as registered in Spinnaker |
| cloud_provider | string | yes | Cloud provider (e.g. aws, gce, kubernetes) |
| cluster_name | string | yes | Cluster name as shown in the Spinnaker UI |
| scope | string | yes | Scope for target lookup (e.g. a region like us-east-1) |
| target | string | yes | Target type: newest, oldest, largest, smallest, or ancestor |
No output schema declared.
No examples provided.
get_task ~89
Get the status and details of a Spinnaker orchestration task (e.g., deploy, resize, rollback, delete). Use this to monitor the progress of a long-running infrastructure operation. Returns JSON with task status, start/end times, retry info, and step-by-step execution details.
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | string | yes | Orchestration task ID returned by Spinnaker when an operation is submitted |
No output schema declared.
No examples provided.
list_accounts ~48
List all configured Spinnaker accounts (cloud provider integrations). Use this to discover available cloud accounts before querying infrastructure or deploying. Returns JSON array of account objects with provider type, environment, and permissions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_applications ~52
List all Spinnaker applications with their metadata. Use this as a starting point to discover available applications before querying pipelines or infrastructure. Returns JSON array of application objects with name, email, accounts, and cloud providers.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_clusters ~65
List all cluster names for a Spinnaker application, grouped by account. Use this to discover clusters before drilling into a specific one with get_cluster. Returns JSON object mapping account names to arrays of cluster names.
| Name | Type | Req | Description |
|---|---|---|---|
| application | string | yes | Application name as registered in Spinnaker |
No output schema declared.
No examples provided.
list_executions ~129
List recent pipeline executions for a Spinnaker application, optionally filtered by status. Use this to monitor deployment activity or find a specific execution ID. Returns JSON array of execution summaries with status, timing, and trigger info. Use get_execution for full details of a specific run.
| Name | Type | Req | Description |
|---|---|---|---|
| application | string | yes | Application name as registered in Spinnaker |
| limit | number | – | Maximum number of executions to return (default: 25) |
| statuses | string | – | Comma-separated execution statuses to filter by (e.g. RUNNING,SUCCEEDED,TERMINAL,CANCELED) |
No output schema declared.
No examples provided.
list_firewalls ~59
List all firewall rules (security groups) across all Spinnaker accounts and regions. Use this to audit network security posture or find a specific security group before inspecting it with get_firewall. Returns JSON array of firewall objects grouped by account and region.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_load_balancers ~76
List all load balancers for a Spinnaker application across all accounts and regions. Use this to inspect network routing and health check configuration for an application. Returns JSON array of load balancer objects with listener, health check, and attached server group details.
| Name | Type | Req | Description |
|---|---|---|---|
| application | string | yes | Application name as registered in Spinnaker |
No output schema declared.
No examples provided.
list_networks ~57
List all networks (VPCs) across all Spinnaker accounts and cloud providers. Use this to discover available networks when configuring deployment targets or security groups. Returns JSON array of network objects with provider, account, and CIDR details.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_pipelines ~66
List all pipeline configurations for a Spinnaker application. Use this to discover available pipelines before triggering or inspecting a specific one. Returns JSON array of pipeline configuration objects with name, stages, triggers, and parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| application | string | yes | Application name as registered in Spinnaker |
No output schema declared.
No examples provided.
list_server_groups ~80
List all server groups (ASGs, instance groups, replica sets) for a Spinnaker application. Use this to view active deployment targets and their instance counts across regions and accounts. Returns JSON array of server group objects with instance counts, cloud provider details, and region info.
| Name | Type | Req | Description |
|---|---|---|---|
| application | string | yes | Application name as registered in Spinnaker |
No output schema declared.
No examples provided.
list_strategies ~70
List all deployment strategy configurations for a Spinnaker application. Use this to discover available strategies (e.g., red/black, rolling, canary) before saving or modifying one. Returns JSON array of strategy configuration objects.
| Name | Type | Req | Description |
|---|---|---|---|
| application | string | yes | Application name as registered in Spinnaker |
No output schema declared.
No examples provided.
list_subnets ~78
List all subnets for a given cloud provider across Spinnaker accounts. Use this to discover available subnets when configuring server groups or deployment targets. Returns JSON array of subnet objects with CIDR, availability zone, and VPC association.
| Name | Type | Req | Description |
|---|---|---|---|
| cloud_provider | string | yes | Cloud provider (e.g. aws, gce, kubernetes) |
No output schema declared.
No examples provided.
pause_execution ~65
Pause a running pipeline execution at the current stage boundary. Use this to temporarily halt a deployment for manual review before it continues to the next stage. The execution can be resumed later with resume_execution. Returns a confirmation message.
| Name | Type | Req | Description |
|---|---|---|---|
| execution_id | string | yes | Pipeline execution ID to pause |
No output schema declared.
No examples provided.
restart_stage ~76
Restart a specific failed or completed stage within a pipeline execution. Use this to retry a stage that failed due to a transient error without re-running the entire pipeline. Requires the execution ID and stage ID. Returns a confirmation message.
| Name | Type | Req | Description |
|---|---|---|---|
| execution_id | string | yes | Pipeline execution ID |
| stage_id | string | yes | Stage ID to restart |
No output schema declared.
No examples provided.
resume_execution ~54
Resume a previously paused pipeline execution, continuing from where it was halted. Use this after pause_execution once the manual review or intervention is complete. Returns a confirmation message.
| Name | Type | Req | Description |
|---|---|---|---|
| execution_id | string | yes | Pipeline execution ID to resume |
No output schema declared.
No examples provided.
save_pipeline ~81
Save a new pipeline configuration to Spinnaker. Use this to create a brand-new pipeline definition — use update_pipeline instead to modify an existing one. Accepts a full pipeline JSON definition and returns a confirmation. This is a mutating operation that creates a new pipeline visible in the Spinnaker UI.
| Name | Type | Req | Description |
|---|---|---|---|
| pipeline_json | string | yes | Full pipeline JSON definition |
No output schema declared.
No examples provided.
save_strategy ~73
Save a new deployment strategy configuration to Spinnaker. Use this to create a reusable deployment strategy (e.g., red/black, rolling push, canary) — use delete_strategy to remove one. Accepts a full strategy JSON definition and returns a confirmation.
| Name | Type | Req | Description |
|---|---|---|---|
| strategy_json | string | yes | Full strategy JSON definition |
No output schema declared.
No examples provided.
search_executions ~170
Search pipeline executions across an application with rich filters such as status, trigger type, and time range. Use this instead of list_executions when you need to find executions matching specific criteria. Returns JSON array of matching execution summaries.
| Name | Type | Req | Description |
|---|---|---|---|
| application | string | yes | Application name as registered in Spinnaker |
| end_time | string | – | Filter executions started before this time (ISO 8601) |
| event_id | string | – | Filter by event ID |
| start_time | string | – | Filter executions started after this time (ISO 8601) |
| statuses | string | – | Comma-separated execution statuses to filter by (e.g. RUNNING,SUCCEEDED,TERMINAL) |
| trigger_type | string | – | Filter by trigger type (e.g. manual, webhook, cron) |
No output schema declared.
No examples provided.
trigger_pipeline ~129
Trigger a new pipeline execution with optional parameters. Use this to start a deployment, build, or any configured pipeline workflow. Returns the execution reference ID that can be passed to get_execution or list_executions to monitor progress. This is a mutating operation that starts a real pipeline run.
| Name | Type | Req | Description |
|---|---|---|---|
| application | string | yes | Application name as registered in Spinnaker |
| parameters | string | – | JSON object of pipeline parameters (e.g. {"tag":"v1.2.3","env":"staging"}) |
| pipeline_name | string | yes | Pipeline name as shown in the Spinnaker UI |
No output schema declared.
No examples provided.
update_pipeline ~96
Update an existing pipeline configuration in Spinnaker. Use this to modify stages, triggers, or parameters of a pipeline that already exists — use save_pipeline instead to create a new one. Accepts a full pipeline JSON definition and returns a confirmation. This is a mutating operation that overwrites the current pipeline config.
| Name | Type | Req | Description |
|---|---|---|---|
| pipeline_id | string | yes | Pipeline configuration ID to update |
| pipeline_json | string | yes | Updated pipeline JSON definition |
No output schema declared.
No examples provided.
What is the io.github.GeiserX/spinnaker-mcp server?
io.github.GeiserX/spinnaker-mcp is listed in the public MCP registry as io.github.GeiserX/spinnaker-mcp. MCP server exposing Spinnaker CD platform via Gate API for pipeline and deployment management. This page covers its container image (drumsergio/spinnaker-mcp:v0.3.2).
Is the io.github.GeiserX/spinnaker-mcp server safe to use?
io.github.GeiserX/spinnaker-mcp scores 51 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.GeiserX/spinnaker-mcp server expose?
io.github.GeiserX/spinnaker-mcp exposes 37 tools: cancel_execution, delete_pipeline, delete_strategy, evaluate_expression, find_images, and 32 more. Their descriptions and schemas cost roughly 3,267 tokens of context every time the server is loaded.
Is the io.github.GeiserX/spinnaker-mcp server still maintained?
io.github.GeiserX/spinnaker-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.