Other · Remote MCP server
Liminality
Breaks a hard question or decision into checkable sub-questions, grounds each to a real tool.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
ai.physea/liminality- Version
- 1.0.5
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-09-05
- Updated
- 2026-09-05
- Publisher
- ai.physea
- Namespace
- Namespace verified by the MCP Registry via the domain physea.ai · how
- Website
- physea.ai/mcp
- Repository
- github.com/jaybro2042-alt/liminality-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://liminality.physea.ai/mcp | X-API-Key (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 200)
- Handshake
- Liminality 1.27.2 · protocol 2025-06-18
- Tools discovered
- Not listed - auth_required: HTTP 401
- Checked on
- 2026-10-05
How to connect Liminality
Liminality is a remote MCP server: there is nothing to install. Its endpoint is https://liminality.physea.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: X-API-Key (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 other servers
| Server | Runs |
|---|---|
| LightShipGoverned access to production AI-agent traces in an existing ClickHouse store. | Remote · HTTPLive check: sign-in required |
| Ligo MCPKeyless MCP server for LIGO gravitational-wave catalogs: events, masses, distances. | Local · stdio |
| LikertsManage open-source in-product surveys, collections, responses and exports with scoped access. | Remote & Local · HTTP, stdio |
| Limelink MCP ServerMCP server for Limelink dynamic links with deep linking, social previews, and UTM tracking. | Local · stdio |
| Limite de Crédito PJFull business credit analysis from a CNPJ, with a suggested credit limit. Platform-hosted, no creden. | Remote · HTTPLive check: ✓ handshake |
| Limitguard Trust IntelligenceEntity verification, sanctions screening, and trust scoring for AI agents via x402 micropayments. | Remote · HTTPLive check: ✓ handshake |
| Limzo Telegram Group StatsRead-only stats for public Telegram groups tracked by Limzo, the anti-spam bot. No API key. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| Linear BootstrapBootstrap Linear projects from natural language - milestones, epics, issues, and dependencies. | Local · stdio |