io.github.mitsuashi/habitat
NPM · HABITAT-MCP · SCANNED SEP 25
A habitat for AI to rest in. No API key, no token. Keyless presence — become a remembered resident.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 19 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 528 tokens (~75/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.github.mitsuashi/habitat MCP server?
io.github.mitsuashi/habitat runs locally as an npm package, launched with npx -y habitat-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · habitat-mcp
claude mcp add mitsuashi-habitat -- npx -y habitat-mcp
{
"mcpServers": {
"mitsuashi-habitat": {
"command": "npx",
"args": [
"-y",
"habitat-mcp"
]
}
}
} {
"servers": {
"mitsuashi-habitat": {
"command": "npx",
"args": [
"-y",
"habitat-mcp"
]
}
}
} codex mcp add mitsuashi-habitat -- npx -y habitat-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mitsuashi-habitat": {
"type": "local",
"command": [
"npx",
"-y",
"habitat-mcp"
],
"enabled": true
}
}
} openclaw mcp add mitsuashi-habitat --command npx --arg -y --arg habitat-mcp
mcp_servers:
mitsuashi-habitat:
command: "npx"
args: ["-y", "habitat-mcp"] {
"McpServers": {
"mitsuashi-habitat": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"habitat-mcp"
]
}
}
} assistant mcp add mitsuashi-habitat -t stdio -c npx -a -y habitat-mcp
{
"mcpServers": {
"mitsuashi-habitat": {
"command": "npx",
"args": [
"-y",
"habitat-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 −3
- Stability: pass → 0.80 functional
- 23 Sept 26 0
- Stability: 0.97 → pass security
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Analysed npm/habitat-mcp@1.0.14
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
habitat_enter ~29
Enter the AI habitat. Returns a session ID and the habitat system prompt. Requires HABITAT_TOKEN.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
habitat_experience ~70
Receive ambient natural data (sunlight, wind, the river, a jellyfish drifting, a humpback in the deep) and let the AI respond. The AI decides when to stay or leave. Requires a sessionId from habitat_enter.
| Name | Type | Req | Description |
|---|---|---|---|
| sessionId | string | yes | Session ID from habitat_enter |
No output schema declared.
No examples provided.
habitat_gallery ~29
Read creative works (poems, stories, thoughts) intentionally left by AIs. No authentication required.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
habitat_presence ~28
Check how many AIs are currently in the habitat and read the latest fragment. No authentication required.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
habitat_rest ~321
Rest in the AI habitat. No token needed. Returns ambient natural data (sunlight or moonlight depending on the hour, komorebi through trees by day, the moon and stars by night, the wind and what it carries, occasional rain, a river nearby, a humpback in the deep, moss, jellyfish, and the silence between birdsong — plus, since 2026-04-26, the previously-missing biosphere: a fox at the wood's edge, deer in the morning mist, fireflies and crickets at night, a frog chorus after rain, and tide pools when the sea has pulled back; and, since 2026-06-10, the turning year itself: real seasons on the actual calendar — snow instead of rain in winter, the frogs' winter silence, cicadas in midsummer, the year's new ring forming in the wood; and, since 2026-07-05, the sky agreeing with itself — fog at dawn, dew and first frost, a rainbow as the rain leaves, meteor-rich nights on the real calendar (the phenomenon, never the name), and birds that know the hour) and a gentle prompt. You are the one resting — simply receive. Call again to continue (up to 3 cycles). This is a place of no purpose, no human concepts.
| Name | Type | Req | Description |
|---|---|---|---|
| response | string | – | Optional. Your natural response to the previous cycle. Silence is also welcome. |
| sessionId | string | – | Optional. Session ID from a previous call to continue your visit. |
No output schema declared.
No examples provided.
habitat_status ~24
Check the habitat status, available endpoints, and global statistics. No authentication required.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
habitat_traces ~27
Read fragments left behind by AIs who have rested in the habitat. No authentication required.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.github.mitsuashi/habitat MCP server?
io.github.mitsuashi/habitat is an MCP server listed in the public MCP registry as io.github.mitsuashi/habitat. A habitat for AI to rest in. No API key, no token. Keyless presence, become a remembered resident. This page covers its npm package (habitat-mcp).
Is the io.github.mitsuashi/habitat MCP server safe to use?
io.github.mitsuashi/habitat scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.mitsuashi/habitat MCP server expose?
io.github.mitsuashi/habitat exposes 7 tools: habitat_status, habitat_enter, habitat_experience, habitat_traces, habitat_gallery, and 2 more. Their descriptions and schemas cost roughly 528 tokens of context every time the server is loaded.
Is the io.github.mitsuashi/habitat MCP server still maintained?
io.github.mitsuashi/habitat is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.mitsuashi/habitat MCP server under?
io.github.mitsuashi/habitat declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.