Liminality MCP server
Breaks a hard question or decision into checkable sub-questions, grounds each to a real tool.
B83/100grade B
Adoption
Growing
0 stars
Reviews
Write oneNobody has reviewed Liminality yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Liminality tools
Tool list not cached yet. `describe` through the gateway fetches it live.
Public scan report
scanner v0.1.9 · 2026-09-20 · same rubric, same numbers if you re-run it
no findings
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 933ms; handshake note: Streamable HTTP error: Error POSTing to endpoint: {"jsonrpc":"2.0","id":1,"error":{"code":-32001,"message":"No API key. 20/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualityAPI key sent as a header8/15
- Maintenancelast push 13 days ago15/15
- Maintainer identitynamespace and repository owner differ; GitHub account older than a year; website matches verified namespace7/10
Overall 83/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Install directly
claude mcp add --transport http liminality https://liminality.physea.ai/mcp
Liminality: common questions
- Is Liminality MCP server safe?
- Mostly: it is graded B (83/100). Read the Liminality safety report
- How do I install Liminality?
- It runs remotely at liminality.physea.ai. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Liminality need an API key?
- Yes. The registry entry asks for
X-API-Key. - Is Liminality maintained?
- The last commit was 13 days ago (2026-09-07). The latest release is v1.0.5.
- Is Liminality up?
- 100% of our last 6 checks got an answer. We check remote servers about four times a day.