Other · Remote MCP server
Sealgate
Sealgate gateway proxy: list governed MCP servers and review agent session and audit status.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.Edison-Watch/sealgate-mcp- Version
- 0.1.2
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-08-19
- Updated
- 2026-08-19
- Publisher
- Edison-Watch (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/Edison-Watch) · how
- Website
- sealgate.ai
- Repository
- github.com/Edison-Watch/sealgate-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.sealgate.ai/mcp/{api_key}/?client={label} | None |
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.
- Checked
- Not requested: URL template placeholder
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: npx | @sealgate/mcp | 0.1.2 | stdio |
How to connect Sealgate
Sealgate is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.sealgate.ai/mcp/{api_key}/?client={label}, 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 URL contains placeholders to fill in before connecting: {api_key} and {label}.
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: @sealgate/mcp version 0.1.2. 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 @sealgate/mcp@0.1.2. It reads these environment variables: SEALGATE_GATEWAY_URL (required) and SEALGATE_API_KEY (required, secret); 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": {
"sealgate-mcp": {
"command": "npx",
"args": [
"-y",
"@sealgate/mcp@0.1.2"
],
"env": {
"SEALGATE_GATEWAY_URL": "<value>",
"SEALGATE_API_KEY": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. 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 other servers
| Server | Runs |
|---|---|
| SealVerify Seal AI decision receipts: signed evidence anyone can check, no account needed. | Remote · HTTPLive check: ✓ handshake |
| SealStops agents double-charging across processes: exactly one execution, confirmed by the provider. | Local · stdio |
| SEALLarge files and secrets between people and agents, never through the chat or the model. | Local · stdio |
| SealedPer-call paid skills for AI agents, run server-side: inputs in, outputs back. The body never ships. | Local · stdio |
| Seam RuntimeSEAM: local-first memory runtime for AI agents, with retrieval and glassbox provenance over MCP. | Local · stdio |
| SeamgrinFind alterations, free tailor training, and paid work opportunities for experienced tailors. | Remote · HTTPLive check: ✓ handshake |
| SeaOtter DispatchSeaOtter dispatches work to a Superteam and checks the delivered outcome before money moves. | Remote · HTTPLive check: sign-in required |
| SearchHubAggregate Serper, Tavily, Exa and AnySearch behind one MCP-ready API with key rotation and quotas. | Local · stdio |