← Registry

Security & Testing

aegisboundary.com

Aegis Boundary provides a structured security check-in service for verifying data and assembly boundaries with honesty guardrails.

1 endpoint4 known toolsFirst detected July 11, 2026Last detected August 17, 2026

ENDPOINT 1

https://aegisboundary.com/mcp

No auth detected

MCP server metadata

Name
aegis-boundary
Version
1.0.0
Capabilities
tools
Server instructions

Aegis Boundary, from your perspective: call aegis_overview to understand it, boundary_arrival to organise which boundaries need a check-in (illustrative; records nothing, certifies nothing), boundary_check_in to feel an illustrative sample receipt for your own task, request_check_in to request the real (human-verified) one. Read is open; action meets the boundary.

Known tools 4

aegis_overview

What Aegis Boundary is, in structured form: the worldview, the state model (Unchecked -> Boundary Check-in -> Boundary Checked), what gets checked (Data Boundary / Assembly Boundary / Receipt), the offer and price, and the honesty guardrails (what Aegis never claims).

Inferred read-only
boundary_arrival

Arrive at the boundary before a check-in.

Inferred read-only
boundary_check_in

Experience a Boundary Check-in from your own perspective.

Inferred read-only
request_check_in

Request a real Boundary Check-in.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.aegis-boundary]
url = "https://aegisboundary.com/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "aegis-boundary": {
      "type": "http",
      "url": "https://aegisboundary.com/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: aegis-boundary
Remote MCP URL: https://aegisboundary.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "aegis-boundary": {
      "url": "https://aegisboundary.com/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "aegis-boundary": {
      "type": "http",
      "url": "https://aegisboundary.com/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "aegis-boundary",
  "transport": "streamable-http",
  "url": "https://aegisboundary.com/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for aegisboundary.com was fetched 2026-07-26T07:38:26.825Z and is being refreshed.

Trust status Neutral

aegisboundary.com is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.