ai.nocturnus/logic-server — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Monitor identity continuity, MCP tool inventory, permissions and adoption.

Reviewed Oct 10, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Nocturnus reasoning and memory context via a stdio MCP bridge

What we know

Nocturnus reasoning and memory context via a stdio MCP bridge. Published by the owner of npm package nocturnusai-mcp. Agent reasoning, memory, and token-optimized context for AI applications.

Maintenance / activity evidence

241 npm downloads, 2026-09-09 to 2026-10-08

Tracking evidence observed Oct 10, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high_for_identity_and_metrics_medium_for_verified_package_description.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Agent context and memory sent through a stdio bridge to the configured NocturnusAI backend; determine where memory is retained before submitting private data. Reported action classes: Create/update agent memory or context. Complete write authority is not verified.
NocturnusAI server endpoint configuration; credentials unspecified
Sensitive access: Service account information and data accessible by supplied credentials

Agent context and memory sent through a stdio bridge to the configured NocturnusAI backend; determine where memory is retained before submitting private data.
Public listing suitability does not imply safe installation or entitlement to access third-party accounts.

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

· 241 package downloads / 30 days

Downloads observed Oct 10, 2026.

Exact npm package nocturnusai-mcp; provider interval 2026-09-09–2026-10-08 (inclusive); observed 2026-10-10T04:43:53Z.

All limitations / Review context

Has nocturnusai-mcp changed publishing identity, permissions, install requirements, or risk exposure?

Published package documentation reviewed; public listing with prominently disclosed risks: Agent context and memory sent through a stdio bridge to the configured NocturnusAI backend; determine where memory is retained before submitting private data.

Agent context and memory sent through a stdio bridge to the configured NocturnusAI backend; determine where memory is retained before submitting private data.
Public listing suitability does not imply safe installation or entitlement to access third-party accounts.
NocturnusAI server endpoint configuration; credentials unspecified
Reviewed write actions: Create/update agent memory or context
Sensitive access: Service account information and data accessible by supplied credentials
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Respect upstream entitlements, version constraints and least-privilege setup.
Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
Publicly documented capabilities are not a guarantee of a safe deployment; review third-party data processing and access scopes.
Public exact-package npm downloads observed for recent 30-day window.

Original activity observations

241 npm downloads, 2026-09-09 to 2026-10-08

Technical identity

npm/nocturnusai-mcp

Exact implementation source: https://www.npmjs.com/package/nocturnusai-mcp ↗
Reviewed resource type: MCP Server
Package identity: npm:nocturnusai-mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 10, 2026 · Latest source observation Oct 10, 2026

Registry source ↗
registry.modelcontextprotocol.io/v0/servers
Source material retained for this review.
Package registry ↗
nocturnusai-mcp
Recorded package identity, distribution or download evidence.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Warning

No runtime server process, Docker setup, OAuth or credentials were executed during this research.
Backend startup and Docker access are required; exposing port 9300 beyond localhost requires authentication and network isolation.
Install documentation is not a guarantee of current package/runtime compatibility.
Official npm package is a stdio shim to a SEPARATELY RUNNING NocturnusAI backend; docs provide local Docker backend and stdio client JSON.
2026-10-13 targeted publisher npm README plus official repository/docs where specified; static research, not runtime test.
Normalized from the publisher-described client registration; not runtime tested and not a Codex TOML config.
The upstream separately supports SSE /mcp/sse; do not confuse upstream transport with shim.
Never paste real credentials into a documentation example.
No live install, OAuth, paid calls, third-party mutation or credential revocation executed.
Some host removal commands are MCP100-composed based on chosen registration name, not publisher-authored.

Install / connect
Publisher instructions
Publisher-documented package/connection route; replace placeholders and verify host-specific syntax.
Publisher setup example · Publisher instructions
npx -y nocturnusai-mcp
Previously reviewed optional local backend / sample deployment; review side effects · Publisher instructions
docker run -d --name nocturnusai -p 9300:9300 -v nocturnusai-data:/data ghcr.io/auctalis/nocturnusai:latest
Configure / authenticate
MCP100 setup guide
Connect stdio client with NocturnusAI instance URL per package README; set NOCTURNUSAI_API_KEY if instance requires authentication.
Use correct transport and published host config. Never paste secrets in chat; server registration is separate from software installation.
Previously reviewed configuration / prerequisites: Start and secure NocturnusAI server first. For the npm shim use client command npx args ["-y","nocturnusai-mcp"] with env NOCTURNUSAI_URL=http://localhost:9300; NOCTURNUSAI_API_KEY only if upstream requires it. The upstream separately supports SSE /mcp/sse; do not confuse upstream transport with shim.
{ "mcpServers": { "nocturnusai": { "args": [ "-y", "nocturnusai-mcp" ], "command": "npx", "env": { "NOCTURNUSAI_URL": "http://localhost:9300" } } } }
Check connection
Suggested check
Check publisher instance /health and client tool listing; failed health should show stderr warning.
Remove / uninstall / revoke
MCP100 setup guide
If registered as `nocturnusai-mcp` in Claude Code, remove its exact client entry with `claude mcp remove nocturnusai-mcp`; for Cursor/Claude Desktop/Codex, remove the matching MCP entry in that host settings. This client removal is MCP100-composed, not a vendor uninstall instruction. Npx does not imply a global install; do not delete user data or revoke credentials implicitly.
Conditional host / package cleanup · Claude Code only · MCP100 composed guide
claude mcp remove nocturnusai-mcp

Official Documentation & Sources

What it does

Nocturnus reasoning and memory context via a stdio MCP bridge. Published by the owner of npm package nocturnusai-mcp. Agent reasoning, memory, and token-optimized context for AI applications.

Capability: AI & Reasoning
Resource type: MCP Server
Best fit: Nocturnus reasoning and memory context via a stdio MCP bridge

Representative uses

Nocturnus reasoning and memory context via a stdio MCP bridge

Limitations

Agent context and memory sent through a stdio bridge to the configured NocturnusAI backend; determine where memory is retained before submitting private data.
Publicly documented capabilities are not a guarantee of a safe deployment; review third-party data processing and access scopes.
Public exact-package npm downloads observed for recent 30-day window.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: NocturnusAI server endpoint configuration; credentials unspecified
Permissions: Agent context and memory sent through a stdio bridge to the configured NocturnusAI backend; determine where memory is retained before submitting private data.
Data handling: Agent context and memory sent through a stdio bridge to the configured NocturnusAI backend; determine where memory is retained before submitting private data.
Cost: Credit/subscription costs may apply; inspect provider docs
Risk and cautions: Agent context and memory sent through a stdio bridge to the configured NocturnusAI backend; determine where memory is retained before submitting private data.

Access scope and cautions

Write actions: Not verified Create/update agent memory or context
Sensitive access: Service account information and data accessible by supplied credentials
Risk level: medium
Security notes: Agent context and memory sent through a stdio bridge to the configured NocturnusAI backend; determine where memory is retained before submitting private data. Public listing suitability does not imply safe installation or entitlement to access third-party accounts.

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-10T04:43:53Z. Watchlist tracking is not a recommendation or a security certification.

What setup and authentication are documented?

A complete connection procedure is not verified. Client notes: Do not infer shell entrypoint or automated credential setup if a command is not explicitly verified. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: NocturnusAI server endpoint configuration; credentials unspecified

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. The partial inventory lists: Create/update agent memory or context. Recorded permission context: Agent context and memory sent through a stdio bridge to the configured NocturnusAI backend; determine where memory is retained before submitting private data.

What data-handling boundary should I consider?

Agent context and memory sent through a stdio bridge to the configured NocturnusAI backend; determine where memory is retained before submitting private data. Recorded sensitive-access context: Service account information and data accessible by supplied credentials.

What limitations and risks should I check before use?

Agent context and memory sent through a stdio bridge to the configured NocturnusAI backend; determine where memory is retained before submitting private data. Publicly documented capabilities are not a guarantee of a safe deployment; review third-party data processing and access scopes. Public exact-package npm downloads observed for recent 30-day window. Public listing suitability does not imply safe installation or entitlement to access third-party accounts. Respect upstream entitlements, version constraints and least-privilege setup.

What cost model is recorded?

The reviewed cost model is Credit/subscription costs may apply; inspect provider docs. This classification does not establish current prices, quotas or the cost of every downstream operation. Check the applicable service terms before authorizing paid actions.