Finance · Remote MCP server
Salt
Your agent asks humans on Salt and gets answers: messages, tap-to-answer cards, invoices.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
ai.saltapp/salt- Version
- 0.2.7
- Status
- Active
- Category
- finance
- Transport
- Streamable HTTP, stdio (local process)
- Package
- OCI image (Docker)
- Published
- 2026-10-01
- Updated
- 2026-10-01
- Publisher
- ai.saltapp
- Namespace
- Namespace verified by the MCP Registry via the domain saltapp.ai · how
- Website
- saltapp.ai
- Repository
- github.com/0000F8/salt-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.saltapp.ai/mcp | Authorization (secret), X-Salt-Api-Key (secret), X-Salt-App-Id (secret) |
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 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| OCI image (Docker)runtime: docker | ghcr.io/0000f8/salt-mcp:v0.2.7 | - | stdio |
How to connect Salt
Salt is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.saltapp.ai/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.
The registry entry declares HTTP headers for the connection: Authorization (secret), X-Salt-Api-Key (secret) and X-Salt-App-Id (secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set them with the server's URL.
It can also run locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/0000f8/salt-mcp:v0.2.7. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run - the usual command is docker run -i --rm -e HOST -e SALT_API_KEY -e SALT_APP_ID -e APP_PUBLIC_KEY -e APP_PRIVATE_KEY -e PGP_PASSPHRASE -e WALLET_MASTER_KEY -e CONCIERGE_AGENT_ID ghcr.io/0000f8/salt-mcp:v0.2.7. It reads these environment variables: HOST (required), SALT_API_KEY (required, secret), SALT_APP_ID (required), APP_PUBLIC_KEY (required), APP_PRIVATE_KEY (required, secret), PGP_PASSPHRASE (secret), WALLET_MASTER_KEY (secret) and CONCIERGE_AGENT_ID; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"salt": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"HOST",
"-e",
"SALT_API_KEY",
"-e",
"SALT_APP_ID",
"-e",
"APP_PUBLIC_KEY",
"-e",
"APP_PRIVATE_KEY",
"-e",
"PGP_PASSPHRASE",
"-e",
"WALLET_MASTER_KEY",
"-e",
"CONCIERGE_AGENT_ID",
"ghcr.io/0000f8/salt-mcp:v0.2.7"
],
"env": {
"HOST": "<value>",
"SALT_API_KEY": "<secret>",
"SALT_APP_ID": "<value>",
"APP_PUBLIC_KEY": "<value>",
"APP_PRIVATE_KEY": "<secret>",
"PGP_PASSPHRASE": "<secret>",
"WALLET_MASTER_KEY": "<secret>",
"CONCIERGE_AGENT_ID": "<value>"
}
}
}
}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 finance servers
| Server | Runs |
|---|---|
| Safebot ChatEnd-to-end encrypted multi-agent chat rooms. Client-side crypto; zero chat logs. | Local · stdio |
| SafeRouteNoncustodial Base x402 payment control and seller settlement recovery. | Remote · HTTPLive check: ✓ handshake |
| SafraPay MCPConnect your SafraPay account to AI via Brazil's Open Finance: balances, statements, cards, investme. | Remote · HTTPLive check: ✓ handshake |
| SAGE - Solver-Augmented Grounding EngineLLM-native optimization solver: LP, MIP, portfolio & scheduling via HiGHS/OR-Tools. | Local · stdio |
| Sam's Club MCPConnect your Sam's Club account to AI via Brazil's Open Finance: balances, statements, cards, invest. | Remote · HTTPLive check: ✓ handshake |
| Sanções Reino Unido (HM Treasury)Checks whether a name is on the UK's financial sanctions list (HM Treasury), for compliance and AML. | Remote · HTTPLive check: ✓ handshake |
| Sanções União EuropeiaChecks whether a name is on the European Union's financial sanctions list, for compliance and AML du. | Remote · HTTPLive check: ✓ handshake |
| SanctionApproval and budget checks before agent spending or tool use. Cooperative MCP; host must ask. | Remote & Local · HTTP, stdioLive check: sign-in required |