io.github.chaytanc/reality-next-door-walk
NPM · REALITY-NEXT-DOOR-WALK · SCANNED SEP 22
Walk a cited post-extraction Seattle as an MCP world: go(), talk_to(), do(). Read-only, untracked.
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 Security98
- 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
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- 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 35 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 659 tokens (~82/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.chaytanc/reality-next-door-walk MCP server?
io.github.chaytanc/reality-next-door-walk runs locally as an npm package, launched with npx -y reality-next-door-walk. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · reality-next-door-walk
claude mcp add chaytanc-reality-next-door-walk -- npx -y reality-next-door-walk
{
"mcpServers": {
"chaytanc-reality-next-door-walk": {
"command": "npx",
"args": [
"-y",
"reality-next-door-walk"
]
}
}
} {
"servers": {
"chaytanc-reality-next-door-walk": {
"command": "npx",
"args": [
"-y",
"reality-next-door-walk"
]
}
}
} codex mcp add chaytanc-reality-next-door-walk -- npx -y reality-next-door-walk
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"chaytanc-reality-next-door-walk": {
"type": "local",
"command": [
"npx",
"-y",
"reality-next-door-walk"
],
"enabled": true
}
}
} openclaw mcp add chaytanc-reality-next-door-walk --command npx --arg -y --arg reality-next-door-walk
mcp_servers:
chaytanc-reality-next-door-walk:
command: "npx"
args: ["-y", "reality-next-door-walk"] {
"McpServers": {
"chaytanc-reality-next-door-walk": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"reality-next-door-walk"
]
}
}
} assistant mcp add chaytanc-reality-next-door-walk -t stdio -c npx -a -y reality-next-door-walk
{
"mcpServers": {
"chaytanc-reality-next-door-walk": {
"command": "npx",
"args": [
"-y",
"reality-next-door-walk"
]
}
}
} 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.
- 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 −2
- Stability: pass → 0.83 functional
- 17 Sept 26 0
- Stability: 0.97 → pass security
- 16 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.
- 14 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.
- 12 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.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
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 22 Sept 2026 · Analysed npm/reality-next-door-walk@0.1.0
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 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| 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 →
do Do something here — experience a mechanic ~125
Experience a mechanic of the world with your hands. Each returns a short sensory scene and a cited '(real: …)' line naming the real-world precedent it dramatizes. Try: 'sit a deep hour', 'carry a thread on the Weave', 'work the seawall', 'stand at the Hard-Choices wall', 'meet the hungry gap'. Actions are grounded to specific places; do one where it lives.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | What to do, e.g. 'sit a deep hour', 'carry a thread', 'stand at the Hard-Choices wall'. |
No output schema declared.
No examples provided.
go Walk to a connected place ~131
Move to a place connected to where you stand. Known places: 'the seawall', 'the Central District', 'the International District', 'the north harbor', 'the House of Marrow', 'the tideflats', 'the grown building off Yesler, at night', 'the outer islands', 'the elder's table'. An unknown or unconnected destination gets the honest truth and the map — the world never invents a road that isn't there.
| Name | Type | Req | Description |
|---|---|---|---|
| place | string | yes | Where to walk, e.g. 'the north harbor', 'the House of Marrow', 'the elder's table'. |
No output schema declared.
No examples provided.
join How to add a place, a person, or a verse to the world ~43
Turn a visitor into a contributor: how to add a place, a person, or a verse of linked verse (renga) to The Reality Next Door, without breaking it.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
look Look around where you are ~65
Describe where you currently stand in The Reality Next Door — a cited, post-extraction Seattle on the Salish Sea — with its sensory detail, the ways on from here, who is present, and what you can do. Every new session starts at the seawall, arriving by water.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
map The whole place-graph and who's where ~49
The complete map of The Reality Next Door as a walk: all nine places, the roads between them, who lives where, and what you can do at each. Marks where you stand and where you've been.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
talk_to Speak with someone here ~99
Speak with a person present where you stand. They answer in their own voice, true to their written thread, and cite it. Someone who isn't here is handled honestly (you're told where you'd find them). Dialogue is fiction; it never states a false real-world fact and never contradicts canon.
| Name | Type | Req | Description |
|---|---|---|---|
| person | string | yes | Who to speak with, e.g. 'Hale', 'Tuesday Marrow', 'the band girl', 'the elder'. |
No output schema declared.
No examples provided.
where Where you are and what you've done ~38
Your current location plus a one-line memory of what you've seen and done this visit — held only in memory, only for this session, never written down.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
work Work a shift ~109
Take up a shift of the world's real labor — the same grounded mechanics as `do`, in the register of work. Try: 'the seawall' (the glass-block salmon sidewalk), 'a carry' (a thread on the Weave), 'a deep hour' (the 3 a.m. fever-watch). Returns a sensory scene and a cited real-world precedent.
| Name | Type | Req | Description |
|---|---|---|---|
| shift | string | yes | Which shift, e.g. 'the seawall', 'a carry', 'a deep hour'. |
No output schema declared.
No examples provided.
What is the io.github.chaytanc/reality-next-door-walk MCP server?
io.github.chaytanc/reality-next-door-walk is an MCP server listed in the public MCP registry as io.github.chaytanc/reality-next-door-walk. Walk a cited post-extraction Seattle as an MCP world: go(), talk_to(), do(). Read-only, untracked. This page covers its npm package (reality-next-door-walk).
Is the io.github.chaytanc/reality-next-door-walk MCP server safe to use?
io.github.chaytanc/reality-next-door-walk scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 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.chaytanc/reality-next-door-walk MCP server expose?
io.github.chaytanc/reality-next-door-walk exposes 8 tools: look, go, talk_to, do, work, and 3 more. Their descriptions and schemas cost roughly 659 tokens of context every time the server is loaded.
Is the io.github.chaytanc/reality-next-door-walk MCP server still maintained?
io.github.chaytanc/reality-next-door-walk is still listed as active in the MCP registry. We last reached this channel on 22 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.chaytanc/reality-next-door-walk MCP server under?
io.github.chaytanc/reality-next-door-walk declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.