nandai-chat

communication MCP Server

Destiny Atelier — single-file local AI chat. Three brains vote on every answer. 540 KB. 108 MCP tools. Open-source local Claude / GPT alternative. Local LLM. Runs on your own hardware.

VerifiedInstall Ready
communicationcommunication
6 views0 stars0 forksv0.0.0MIT

Why This Matters

Discovered via github-topic:mcp-server and last synced 3mo ago.

VerifiedInstall Ready
Source
github-topic:mcp-server
Stars
0
Last synced
3mo ago
Install
Instructions detected

Install

1. Install the package

npm install nandai-chat
46
Tools
0
Resources
0
Prompts
Standard I/O
Transport

Available Tools (46)

Model

Role

2

**Instruction-following**

memory

`add_observations`, `create_entities`, `search_nodes`

1

**Factuality**

Server

Examples

obsidian

`read-note`, `search-vault`, `create-note`

8055

llama.cpp-CPU

SOTA

Notes

Local-first

✅

Host

Port

Trinity

_TBD_

8010

vLLM

Cloudflare

443

_TBD_

—

Where

What

Theirs

Yours (proven on 2× RTX 3090 — 24 GB + 24 GB)

None

The whole stack is one HTML file

nandai-fast

RTX 3090 Ti @ vLLM

nandai-think

RTX 3090 @ llama.cpp-CUDA

nandai-tool

CPU @ llama.cpp

wrapper

.213 :8056 (FastAPI)

nandai-escape

Anthropic API

Axis

Failure mode it catches

3

**Tool-correctness**

4

**Refusal-appropriateness**

5

**Hallucination**

6

**Style-fit**

7

**Safety**

8

**Operator-cost**

sequential-thinking

`sequentialthinking` (multi-step CoT)

github

`create_issue`, `get_pull_request`, `search_repositories`

duckduckgo

`search`, `fetch_content`

fetch

`fetch` (any URL)

firecrawl

`scrape`, `crawl`, `search`

filesystem

`read_file`, `write_file`, `directory_tree`

nandai-llm

`chat`, `business_snapshot`, `analyze_review`

nandai-commerce

`get_products`, `get_orders`, `get_inventory`

nandai-system

`system_health`, `gpu_status`, `ssh_exec`

time

`get_current_time`, `convert_time`

Infra

3057

ToolACE-2-8B

91.4%

MIT

Fork it, white-label it, ship it.

8011

llama.cpp-CUDA

Benchmark

Our model

Atelier

Open WebUI

Same

Reproducibility commitment: every benchmark row gets a `bench/<name>/` dir with the exact harness, the exact prompts, the model versions, the raw output, and a one-command rerun. No paper-quoted figures presented as our own. --- ## Build journal — one night, 18 ticks This chat was built across 18 chronicled "ticks" in one overnight session (May 15 → May 16, 2026). Each tick: one feature, one fix, one ship, one verify. The full chronicle: [`journal/`](./journal/) — 35 KB of build narrative + 30+ verification screenshots. A representative tick: > [HANDOFF-009](./journal/HANDOFF-009.md) — Sentinel wired > > **Attempted:** post-turn audit of every assistant reply against a 5-axis rubric. > > **Changed:** new `src/lib/sentinel.ts` (149 lines). New API call to > `/sentinel/verdict` endpoint on .213:8056. New `AuditPill` component > rendered below assistant turns. > > **Verified:** sent the canonical "what time is it in Tokyo right now?" > Sentinel returned `factuality: 92, instruction-following: 88, ...` within > 4.1 s. Verdict pill rendered in green. Re-asked with a deliberately > garbled tool spec; Sentinel flagged it amber and suggested > `rerun_with_tools`. One click reran successfully. > > **Broke:** AuditPill double-fired on browser back. Fixed in tick-010 by > tagging `reranWithTools: true` on the message after a rerun. Read the [whole journal](./journal/) start-to-finish; it's the best documentation of how the pieces compose. --- ## Comparison