Spotinst MCP Server

mcp-server-spotinst PyPI v0.7.0

Published by arnstarn — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for Spot.io (Spotinst) API - manage Ocean clusters, VNGs, and Elastigroups

Trust grade
A
99/100
Last scanned get badge →
Trust
A · 99/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Minimal
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 99/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 1 = 99. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 39

Each tool and what it can reach — statically extracted from the published source.

  • create_vngno sensitive capability
  • delete_vngno sensitive capability
  • detach_instancesno sensitive capability
  • export_cluster_yamlno sensitive capability
  • export_vng_yamlno sensitive capability
  • filter_clusters_by_tagno sensitive capability
  • filter_vngs_by_tagno sensitive capability
  • get_allowed_instance_typesno sensitive capability
  • get_clusterno sensitive capability
  • get_cluster_azureno sensitive capability
Show 29 more tools ↓
  • get_cluster_costsno sensitive capability
  • get_cluster_healthno sensitive capability
  • get_cluster_logno sensitive capability
  • get_cluster_nodesno sensitive capability
  • get_cluster_schedulingno sensitive capability
  • get_cost_trendingno sensitive capability
  • get_elastigroupno sensitive capability
  • get_right_sizingno sensitive capability
  • get_rollno sensitive capability
  • get_savings_summaryno sensitive capability
  • get_stateful_nodeno sensitive capability
  • get_stateful_node_azureno sensitive capability
  • get_vngno sensitive capability
  • get_vng_azureno sensitive capability
  • initiate_rollno sensitive capability
  • list_accountsno sensitive capability
  • list_all_clustersno sensitive capability
  • list_clustersno sensitive capability
  • list_clusters_azureno sensitive capability
  • list_elastigroupsno sensitive capability
  • list_rollsno sensitive capability
  • list_stateful_nodesno sensitive capability
  • list_stateful_nodes_azureno sensitive capability
  • list_vngsno sensitive capability
  • list_vngs_azureno sensitive capability
  • probe_token_capabilitiesno sensitive capability
  • remove_instancesno sensitive capability
  • update_vngno sensitive capability
  • update_vng_azureno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.7.0 latest A 99/100 0 1.13.0 2026-08-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 99/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/mcp-server-spotinst/badge.svg)](https://mcptrustchecker.com/registry/mcp-server-spotinst)
HTML
<a href="https://mcptrustchecker.com/registry/mcp-server-spotinst"><img src="https://mcptrustchecker.com/registry/mcp-server-spotinst/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mcp-server-spotinst/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan mcp-server-spotinst --online --registry pypi

Use the free API → How scoring works

More in Cloud & DevOps