Developer · Remote MCP server
Boundaryai
Deterministic runtime safety for AI agents: scan PII, gate tool actions, verify LLM output.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
ai.boundaryai/boundaryai- Version
- 0.7.31
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-07-25
- Updated
- 2026-07-25
- Publisher
- ai.boundaryai
- Namespace
- Namespace verified by the MCP Registry via the domain boundaryai.ai · how
- Website
- boundaryai.ai
- Repository
- github.com/skvcool-rgb/BoundaryAI
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.boundaryai.ai/mcp | Authorization (required, 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; a Bearer token is asked for
- Checked on
- 2026-10-05
How to connect Boundaryai
Boundaryai is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.boundaryai.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 an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
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
| Server | Runs |
|---|---|
| BorealHostAgent-native web hosting - deploy sites, manage DNS, register domains, scale infrastructure. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| BotLens AI GatewayMCP gateway for getbotlens.com: articles, search and full text. Read-only, no auth. | Remote · HTTPLive check: ✓ handshake |
| Botoi MCP49 developer tools via MCP: DNS, WHOIS, IP lookup, JWT, hashing, QR, and more. | Remote · HTTPLive check: ✓ handshake |
| bouncerStatic compliance-controls checker for UK Online Safety Act & ICO Children's Code. CLI + MCP. | Local · stdio |
| bounty-mcpLive coding-bounty deal-flow from verified-escrow GitHub bounties for AI agents. | Local · stdio |
| BountyVerdict Agent Decision ToolsRead-only GitHub bounty, agent harness, Actions failure, flake, and MCP tool-drift decisions. | Remote · HTTPLive check: ✗ no handshake |
| BountyVerdict Agent Decision ToolsFree selector plus read-only GitHub bounty, agent harness, Actions, flake, and MCP drift decisions. | Remote · HTTPLive check: ✗ no handshake |
| BourdonRecognition-first cross-agent memory federation. One shared memory across all your agents. | Local · stdio |