Developer · Remote MCP server

sota.io

EU-native PaaS for AI agents - deploy web apps with one sentence, managed Postgres, GDPR by default.

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
io.sota/mcp
Version
1.5.0
Status
Active
Category
developer
Transport
Streamable HTTP, stdio (local process)
Package
npm
Published
2026-05-19
Updated
2026-05-19
Publisher
io.sota
Namespace
Namespace verified by the MCP Registry via the domain sota.io · how
Listed under
PostgreSQL MCP servers
Repository
github.com/sota-deploy/mcp-server
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://mcp.sota.io/mcpNone

Live check

This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.

Reachable
Yes (HTTP 200)
Handshake
sota 1.4.0-pre · protocol 2025-06-18
Tools discovered
14 - show namescreate_account, list-projects, create-project, delete-project, deploy, get-logs, set-env, get-env, rollback, get-status, add-domain, list-domains, get-domain, remove-domain
Checked on
2026-10-05

How the live check works

Packages

RegistryPackageVersionTransportEnvironment variables
npm@sota-io/mcp1.5.0stdioNone declared

How to connect sota.io

sota.io is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.sota.io/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.

It can also run locally from a Node.js package published to the npm registry: @sota-io/mcp version 1.5.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @sota-io/mcp@1.5.0.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@sota-io/mcp@1.5.0"
      ]
    }
  }
}

Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More developer servers

All 5,152 →
ServerRunsEndpoint or package
SondeLocal code graph for TypeScript, Python and Swift: who calls this, what breaks if I change it.Local · stdionpm: @cheppulabs/sonde
SooverynAI personas with a lasting, encrypted memory per project, for Claude Code. Hosted in France.Remote · HTTPLive check: sign-in requiredmcp.sooveryn.com
SophonHonest token economics for MCP agents. 68% tokens saved, zero-ML Rust binary.Local · stdionpm: mcp-sophon
Sophos Central MCPMCP server for Sophos Central - endpoint security, XDR/MDR, and MSSP multi-tenant ops.Local · stdionpm: @rijul170/sophos-mcp
Sounio CompilerCheck, compile, run, and test Sounio programs locally.Local · stdioPyPI: sounio-mcp-server
Soup List LintReads your SOUP register the way an auditor does: 16 rules over clauses 8.1.2, 5.3.3, 5.3.4, 4.3 and.Local · stdionpm: @readystack/soup-list-lint
Source Map Parser MCPParse JavaScript error stack traces back to original source code using source maps.Local · stdionpm: source-map-parser-mcp
SourcedSource code search for every package on PyPI and npm.Remote · HTTPLive check: ✗ no handshakemcp.sourced.dev