Security

Who can call your server

A private server answers only calls that carry a Sokie token. MCP clients get one with OAuth 2.1, as the MCP spec describes, and Sokie asks you to allow each client every time one connects. Nobody copies a token by hand.

• A token lasts 15 minutes and renews itself while the client keeps using it. Disconnect a client in Settings and it's cut off within 15 minutes.
• Calls are rate limited per caller, so one client can't flood your API through Sokie.
• A public server answers anyone with its address. Make one public only for an API that's public anyway.

Your API’s credentials

• Secrets a server needs, like an API key, are encrypted with AES-256-GCM before they're stored. Each is bound to its server and its name, so a copy can't be opened anywhere else. A value never appears in git, a deploy or a log, and neither the CLI nor the app shows it again.
• When each caller brings their own key, it's encrypted the same way, sent only on that person's own calls, and never shown again.
• For an API that uses OAuth, each person can sign in to it themselves, and their tokens are encrypted the same way.

What Sokie keeps about calls

For each call, a log line: its time, the tool, how it ended, its status code and duration, the kind of error if any, and the client that made it. Never the call's arguments or results.

Logs are kept 7 days on Hobby and pay as you go, 30 days on Pro and a year on Scale. Usage is counted per server, per day and per month for billing, and the count is all billing keeps.

What tools may do

Every tool declares its risk: read, write, delete, or an effect outside the API, like sending an email. MCP clients use it to decide when to ask you before a call, and Sokie's own Test tab asks before anything that writes or acts on the world.

The audit trail

Sign-ins, deploys, changes to servers, secrets and billing are recorded for a year, and the record outlives a deleted server. A secret's entry says it changed, never what it is. On a paid plan you can also record the IP address and browser each event came from.

GitHub

• The Sokie App sees only the repositories an account's owner gives it, and the GitHub tokens it works with last an hour.
• Sokie keeps no GitHub token of yours. Linking a repository holds your GitHub sign-in only while the link dialog is open.
• GitHub's notifications to Sokie are checked against a shared secret before Sokie acts on them.

Your account and data

• You sign in with GitHub or Google. Sokie never sees or stores a password.
• A CLI sign-in lasts 30 days, or until it goes 7 days unused, and you can shorten both.
• No third-party analytics or tracking, and no ads. Your specs, servers and calls are never used to train AI models.

Who processes data for Sokie, and how long each kind is kept, is in the Privacy policy.

Report a problem

Found a security issue? Write to hello@sokie.sh with what you found and how to reproduce it, and give us the chance to fix it before telling anyone else.