@neitherai/mcp-server

MCPcommunity
v0.1.2UnknownMITUpdated 3d agonpmGitHub

Neither decision-memory MCP server for Cursor and agent IDEs

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
73Downloads/wk
3d agoLast update
Needs 1 credential before it runs
  • NEITHER_API_KEYAPI keyrequired

    Workspace API key from https://www.neither.online/developers/quickstart

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
AuthorUnknown
LicenseMIT
Version0.1.2
Sourcenpm+mcp-registry
Trust Status
B
60/100Good
Listed in Forge index+10/10
Publisher identity verified+0/20
Publisher: run `forge publish` from the package repo to claim ownership
Ed25519 publish signature+0/5
Included automatically when the publisher runs `forge publish`
Domain verification+0/5
Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
npm Trusted Publishing (Sigstore)+0/5
Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
npm maintainer match+0/5
Earned once your identity is verified above and that login is an npm maintainer of this package
CVE scan · clean+30/30
Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain
Provenance
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface5 tools · none privileged
Security scan✓ Cleanv0.1.2 · todayHow well does this scan work?
EvalsNone
IndexedSep 7, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

5 tools · none privileged
Statically extracted from the published packagev0.1.2 · 2h ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

memory_searchAt a delivery fork or planning write, search workspace decision memory (NL query). Returns Decision/Citation prose — use top hits to answer; fetch at most 1–2 snippets with node_id=hit.id. Do not fall back to DB/repo archaeology for decisions.

At a delivery fork or planning write, search workspace decision memory (NL query). Returns Decision/Citation prose — use top hits to answer; fetch at most 1–2 snippets with node_id=hit.id. Do not fall back to DB/repo archaeology for decisions.

No input schema was published for this tool.

memory_for_fileHero tool at delivery forks when a repo path is in play — cited Decision/Rejected/Constraint/Citation. Prefer this over memory_search when editing or planning a specific file. Honest empty if uncovered.

Hero tool at delivery forks when a repo path is in play — cited Decision/Rejected/Constraint/Citation. Prefer this over memory_search when editing or planning a specific file. Honest empty if uncovered.

No input schema was published for this tool.

memory_snippet_fetchFetch verbatim quote by provenance source_document_id. ALWAYS pass node_id = memory_search hit id so content matches that Decision title (same document can have unrelated nodes). At most 1–2 fetches per fork; then answer or abstain.

Fetch verbatim quote by provenance source_document_id. ALWAYS pass node_id = memory_search hit id so content matches that Decision title (same document can have unrelated nodes). At most 1–2 fetches per fork; then answer or abstain.

No input schema was published for this tool.

memory_timelineTime-ordered decision memory for a topic after a fork. Prefer memory_search prose first; use timeline only when sequence matters. Do not use as a substitute for answering.

Time-ordered decision memory for a topic after a fork. Prefer memory_search prose first; use timeline only when sequence matters. Do not use as a substitute for answering.

No input schema was published for this tool.

memory_pushClose a decision or seed an ADR snippet with provenance metadata (source id, occurred_at, participants, thread id).

Close a decision or seed an ADR snippet with provenance metadata (source id, occurred_at, participants, thread id).

No input schema was published for this tool.

5 of 5 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Neither decision-memory MCP server for Cursor and agent IDEs

Keywords
mcp
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-07 — observed resolution, not a publisher declaration.

60 packages resolved · 1 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

53 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+41 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.