sota.io MCP server
io.sota/mcpsota.iostreamable-httpv1.6.0Scanned
EU-native PaaS for AI agents — deploy web apps with one sentence, managed Postgres, GDPR by default.
14 tools: 5 can delete or cancel things, 3 change things and 6 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- 2 findings, 1 high
Tools listed without sign-in. Remote posture
Anlyon alternative
8 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the sota.io MCP server can do
The sota.io MCP server is published by sota.io, a domain the MCP Registry verified. It has 14 tools. It can delete or cancel things (5 tools: delete-project, deploy, set-env, rollback and 1 more) and create or change data (3 tools: create_account, create-project and add-domain). 6 tools only read.
1 tool brings in text other people can write (get-status).
The fixed checks matched 2 findings, 1 of them high severity (sensitive-path and long-description). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 18, 2026, version 1.6.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
14 tools
Deletes or cancels 5Claude Code: deny
delete-projectDelete a project and all its deployments from sota.io.No findings
Why it is in this group
- The name "delete-project" says "delete": a word for removing or ending something.
- The description says "irreversible".
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Delete a project and all its deployments from sota.io. This action is PERMANENT and irreversible. It removes the project, all deployments, the managed PostgreSQL database, environment variables, and webhooks. The project slug will become available again after deletion.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
deployDeploy an application to sota.io.2 findings
Why it is in this group
- The name "deploy" says "deploy": a word for a change.
- The server marks it destructive (destructiveHint: true).
Findings
- High
The description refers to ".env", ".env.local", ".env.*.local" and ".env.production".
What this check looks forMatched text
description: "...DS_Store and the local/secret env files .env, .env.local, .env.*.local and .envrc (a..."
- Info
The description is 2,469 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...uch as .env.production are kept (set-env values are not available at build time)."
Description, as the server wrote it Deploy an application to sota.io. The platform auto-detects your framework and builds a Docker image automatically: - Next.js: Detected via next.config.js/ts. Add output: 'standalone' to next.config for optimal builds. - Node.js: Detected via package.json with a "start" script. Works with Express, Fastify, Koa, Hapi, etc. - Python: Detected via requirements.txt or pyproject.toml. Works with Flask, FastAPI, Django. - Custom Dockerfile: If a Dockerfile exists in the project root, it takes priority over auto-detection. Use this for Go, Rust, Java, or any other language. The EXPOSE directive in the Dockerfile is used to detect the app port automatically. Supply the source code as **files** (inline source from AI): Pass a map of relative paths to UTF-8 text content. Best when you've just generated a small app in this conversation and want to deploy it without any filesystem step. Up to 200 files, 10 MB total. Include the framework manifest (package.json, requirements.txt, or Dockerfile) so auto-detection works. This hosted server only accepts inline files. Pass the source inline as `files`, or deploy a directory or a git repository with the local server (npx @sota-io/mcp) or the CLI (`sota deploy`). IMPORTANT: Your app MUST listen on the PORT environment variable. For auto-detected frameworks (Next.js, Node.js, Python) PORT is 8080. For custom Dockerfiles, the port is auto-detected from the EXPOSE directive (e.g. EXPOSE 3000 sets PORT=3000). If no EXPOSE is found, it defaults to 8080. Every project includes a managed PostgreSQL 17 database. Six environment variables are auto-injected into your container — no manual database configuration needed: DATABASE_URL (full connection string), PGHOST, PGPORT, PGUSER, PGPASSWORD, and PGDATABASE. Libraries that follow libpq conventions (node-postgres, pgx, psycopg2, Django) pick up the PG* variables automatically with no configuration. If your app needs database migrations, run them on startup. Deployments use blue-green strategy for zero downtime. The old container keeps running until the new one passes health checks (60s timeout). Use get-logs to monitor build progress. .git/, node_modules/, .DS_Store and the local/secret env files .env, .env.local, .env.*.local and .envrc (any directory, any case) are excluded from the archive; set runtime secrets with set-env instead. Committed variants such as .env.production are kept (set-env values are not available at build time).
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
remove-domainRemove a custom domain from a sota.io project.No findings
Why it is in this group
- The name "remove-domain" says "remove": a word for removing or ending something.
- The description says "irreversible".
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Remove a custom domain from a sota.io project. This removes the domain mapping and its SSL certificate. The DNS records at your registrar are NOT automatically removed — clean those up manually. This action is immediate and irreversible.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
rollbackRollback a project to its previous deployment.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Rollback a project to its previous deployment. This instantly swaps the container image without rebuilding — the previous image is reused for near-instant rollback. Uses the same blue-green strategy for zero downtime. The database is NOT rolled back (data persists across deployments). Use this when a deployment introduces bugs or breaks the app.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
set-envSet an environment variable for a project.No findings
Why it is in this group
- The name "set-env" says "set": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Set an environment variable for a project. Variables are encrypted at rest (AES-256-GCM) and injected at container runtime. NOTE: DATABASE_URL, PGHOST, PGPORT, PGUSER, PGPASSWORD, and PGDATABASE are all auto-injected for the managed PostgreSQL database — you do NOT need to set any of them manually. The PORT variable is auto-managed: 8080 for auto-detected frameworks (Next.js, Node.js, Python), or auto-detected from the Dockerfile EXPOSE directive for custom Dockerfile builds. IMPORTANT: Changing env vars does NOT auto-redeploy. You must call deploy or use the redeploy API endpoint to apply changes. For Next.js apps, NEXT_PUBLIC_* variables must be set BEFORE deploying since they are embedded at build time.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
Changes things 3Claude Code: ask
add-domainAdd a custom domain to a sota.io project.No findings
Why it is in this group
- The name "add-domain" says "add": a word for a change.
Description, as the server wrote it Add a custom domain to a sota.io project. Each project supports up to 5 custom domains with automatic HTTPS via Let's Encrypt. Returns DNS setup instructions: for apex domains (example.com), add an A record pointing to 23.88.45.28; for subdomains (app.example.com), add a CNAME record pointing to {slug}.sota.io. Domain statuses: pending (waiting for DNS) → verified (SSL provisioning) → active (live with HTTPS). After DNS is configured, verification and SSL provisioning happen automatically.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
create_accountSign up for a brand-new sota.io account from inside Claude — no browser, no copy-paste.No findings
Why it is in this group
- The name "create_account" says "create": a word for a change.
- The input takes a statement or command to run (input.code), which can change anything it can reach.
Description, as the server wrote it Sign up for a brand-new sota.io account from inside Claude — no browser, no copy-paste. Two-step flow: STEP 1: Call with just `email`. We send a 6-digit confirmation code to that email. STEP 2: Call again with `email` + `code`. We verify, create the account on the Free tier (3 projects, EU-hosted, no credit card), generate a sota.io API key, and return it to you. After Step 2 you'll get back a key like `sota_…`. **Save it in a safe place** — you'll need it for any subsequent sota.io tool call in Claude (or you can use it with the sota CLI). It is shown ONCE and never recoverable. sota.io is an EU-native PaaS hosted in Germany — GDPR-compliant by default, no CLOUD Act exposure. Disposable / throwaway email addresses are not accepted; use a real address.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
create-projectCreate a new project on sota.io.No findings
Why it is in this group
- The name "create-project" says "create": a word for a change.
Description, as the server wrote it Create a new project on sota.io. Each project automatically provisions: (1) a managed PostgreSQL 17 database accessible via the DATABASE_URL environment variable (auto-injected, no configuration needed), (2) PgBouncer connection pooling (pool size 20, max 100 clients), (3) automatic daily database backups with 7-day retention, (4) a live URL at https://{slug}.sota.io with automatic HTTPS via Let's Encrypt. The project slug is auto-generated from the name (lowercase, hyphens, max 63 chars) and is immutable after creation. Supported frameworks: Next.js, Node.js (Express/Fastify/Koa), Python (Flask/FastAPI/Django), or any language via custom Dockerfile. You can also add up to 5 custom domains per project with automatic HTTPS (via API: POST /v1/projects/:id/domains with {domain: "yourdomain.com"}). DNS: A record to 23.88.45.28 for apex domains, CNAME to {slug}.sota.io for subdomains. Optionally associate the project with a public git repository at create-time by passing `git_url` (and optional `git_branch`). The association is informational — it shows up in the dashboard and the `sota deploy --git` CLI flag can default to it — but does NOT enable auto-deploy-on-push yet.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Only reads 6Show 6 read-only tools
get-domainGet details of a custom domain including its current status and DNS setup instructions.No findings
Why it is in this group
- The name "get-domain" says "get": a word for reading.
Description, as the server wrote it Get details of a custom domain including its current status and DNS setup instructions. Domain statuses: pending (DNS not yet configured), verified (DNS confirmed, SSL provisioning), active (live with HTTPS). If status is 'pending', configure the DNS record as shown in the instructions.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get-envList environment variables for a project.No findings
Why it is in this group
- The name "get-env" says "get": a word for reading.
Description, as the server wrote it List environment variables for a project. Values are masked for security. Auto-injected variables (DATABASE_URL, PGHOST, PGPORT, PGUSER, PGPASSWORD, PGDATABASE, PORT) may not appear in this list but are always available in the container at runtime.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get-logsGet build and runtime logs for a deployment.No findings
Why it is in this group
- The name "get-logs" says "get": a word for reading.
Description, as the server wrote it Get build and runtime logs for a deployment. If no deployment_id is provided, returns logs for the latest deployment. Use this after calling deploy to monitor build progress and diagnose failures. Logs include: framework detection output, dependency installation, build steps, container startup, and health check results. If a deployment fails, check the logs for error details — common issues include missing dependencies, build errors, or the app not listening on the correct PORT (check the PORT env var — 8080 for auto-detected frameworks, or the EXPOSE value from Dockerfile).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get-statusGet the current deployment status for a project, including the live URL (https://{slug}.sota.io), detected framework, and recent deployment history.Reads text others writeNo findings
Why it is in this group
- The name "get-status" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "get" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it Get the current deployment status for a project, including the live URL (https://{slug}.sota.io), detected framework, and recent deployment history. Deployment statuses: pending (queued), building (build in progress), built (image ready), deploying (starting container + health checks), running (live and healthy), failed (build or health check error), stopped (replaced by newer deployment). Use this to verify a deployment succeeded after calling deploy.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list-domainsList all custom domains for a sota.io project.No findings
Why it is in this group
- The name "list-domains" says "list": a word for reading.
Description, as the server wrote it List all custom domains for a sota.io project. Shows domain name, status (pending/verified/active), and ID for each domain. Use get-domain with a domain ID to see DNS instructions and full details.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list-projectsList all projects on your sota.io account.No findings
Why it is in this group
- The name "list-projects" says "list": a word for reading.
Description, as the server wrote it List all projects on your sota.io account. sota.io is an EU-native DevOps PaaS hosted in Germany (GDPR-compliant). Each project gets a live URL at {slug}.sota.io with automatic HTTPS, a managed PostgreSQL 17 database (DATABASE_URL auto-injected), PgBouncer connection pooling, daily backups, zero-downtime blue-green deployments, gVisor container isolation, and custom domain support (up to 5 per project with automatic HTTPS).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:14 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 8
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://mcp.sota.io/.well-known/oauth-protected-resource
- Authorization servers
- https://mcp.sota.io/auth/v1
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 8 tools that change things (5 destructive, 3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.sota.io/mcp: tools/list returned 14 tools to an anonymous client, including delete-project (destructive), deploy (destructive), set-env (destructive), rollback (destructive), remove-domain (destructive) and 3 more
Findings
Matches of fixed checks, with the text they matched.
- Highdeploy
The description refers to ".env", ".env.local", ".env.*.local" and ".env.production".
What this check looks forMatched text
description: "...DS_Store and the local/secret env files .env, .env.local, .env.*.local and .envrc (a..."
- Infodeploy
The description is 2,469 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...uch as .env.production are kept (set-env values are not available at build time)."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Install
Pinned to version 1.6.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http sota https://mcp.sota.io/mcpclaude mcp add --transport http sota https://mcp.sota.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__sota__list-projects",
"mcp__sota__get-logs",
"mcp__sota__get-env",
"mcp__sota__get-status",
"mcp__sota__list-domains",
"mcp__sota__get-domain"
],
"ask": [
"mcp__sota__create_account",
"mcp__sota__create-project",
"mcp__sota__add-domain"
],
"deny": [
"mcp__sota__delete-project",
"mcp__sota__deploy",
"mcp__sota__set-env",
"mcp__sota__rollback",
"mcp__sota__remove-domain"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as sota. Review it before you use it.
Capability tags behind 1 rule
- mcp__sota__get-status untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.sota/mcp/verify?hash=7b631996746d1673b15fb539a5790cf0f2d56abfb8ec44e86a9a16bffc2a7148" | jq -e '.changed == false'Pinned hash 7b631996746d, from Nov 18, 2026, 16:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.sota/mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.sota/mcp)Source: MCP Registry · repository. Synced Nov 18, 2026, 16:18 UTC.
sota.io MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the sota.io MCP server safe?
- No scan can promise that. What its definitions show: 14 tools, 8 of which can change, send or delete something, and 2 findings (1 high) from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the sota.io MCP server delete data?
- Yes. 5 tools can delete, cancel or revoke something: delete-project, deploy, set-env, rollback and remove-domain.
Can the sota.io MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the sota.io MCP server have?
- 14 tools: 5 destructive, 3 write, 6 read. delete-project, deploy, set-env, rollback, remove-domain, create_account, create-project, add-domain and 6 more.
Does the sota.io MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the sota.io MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the sota.io MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 17, 2026. Every change is on this page and in its Atom feed.