liminality
Description
Liminality turns hard questions into worked, checkable answers. It breaks your request into its real sub-questions, grounds each one in actual tools and sources, then hands back a route you can rerun and audit. Bring it decisions, plans, research, anything with more than one moving part. Solved routes get reused, so answers come back faster and cheaper as the library grows. 50 free solves to start.
What our measurements say
liminality is a remote MCP server published at mcp.physea.ai. It has been probed 7 times since 9/10/2026. It answered in 7 of them (100.0%), a near-uninterrupted record. Median response time is 566 ms, a delay an agent will notice. It exposes a broad tool surface of 27 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Agent readability score
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
Agent readability score
Strengths
- Tool names like 'solve' and 'delegation' clearly indicate their primary functions.
- Some tools (e.g., 'compress_context') provide specific use cases in their descriptions.
Weaknesses
- Many tool descriptions focus on capabilities rather than usage context (e.g., 'get_capabilities').
- Parameters in tools like 'handoff' lack clear definitions for 'source_sessions' and 'subject'.
- No explicit error handling or constraint documentation in tool descriptions.
handoff— Ambiguous parameters like 'source_sessions' and 'subject' without clear definitions.get_capabilities— Description only lists capabilities without explaining when to use the tool.recover— Action parameters ('open', 'candidates') lack context for error scenarios.
Verdict
Event narrative
Risk: medium
- 2026-09-10T21:16:35.016Z — era changed from auth-gated to legacy · Agent now operates under legacy compliance framework
- 2026-09-11T03:50:39.090Z — complianceScore rose from null to 100 · System achieved full regulatory compliance
- 2026-09-11T03:50:39.090Z — smokeOk changed from null to false · Smoke test validation failed in legacy environment
Advice
Schema compliance
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
- tools/list schema valid
- inputSchema is valid JSON Schema
- Smoke test failed · last run:
- Cold-start: cold 137ms → warm 149ms (penalty 0ms)
Availability history
Event log
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
- Server build: — → 1.27.2
- Supported versions: — → 2025-11-25
- Era changed: Auth-gated → Legacy
- Added to watch — era: Auth-gated
Get your badge
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/jay-ikbm-liminality)<a href="https://mcpmetrics.io/servers/jay-ikbm-liminality"><img src="https://mcpmetrics.io/badge/jay-ikbm/liminality/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to see