Suggest a Tool

Email us a link and we'll review it for inclusion.

Every listing on Neighbourhood Claw is hand-reviewed by an operator. We don't accept automated submissions yet — but we read every suggestion sent to:

mail hello@nbhdclaw.com

Include the URL, a one-line pitch, and (optionally) a category. We aim to respond within a week.

Neighbourhood Claw
Browse Tools Suggest a Tool
OpenStinger Memory tool screenshot — openclaw.ai

OpenStinger

OpenStinger is an open-source MCP-native memory, reasoning, and alignment harness — 30 MCP tools across three tiers that add persistent temporal memory, structured vault knowledge (identity, domain, p

Added
1 month ago

About

OpenStinger is an open-source MCP-native memory, reasoning, and alignment harness — 30 MCP tools across three tiers that add persistent temporal memory, structured vault knowledge (identity, domain, preferences, constraints), and real-time response alignment scoring to any agent runtime. State lives in two Docker volumes, making it fully portable across runtimes and hosts. Works with OpenClaw, NanoClaw, ZeroClaw, PicoClaw, Claude Code, Cursor, LangGraph, and any MCP-compatible runtime.

person_check
Best For

Agent developers who need persistent, portable memory and behavioral grounding across multiple sessions and potentially multiple runtimes — particularly teams who want an auditable alignment layer alongside standard memory retrieval.

Pros & Cons

check_circle

Pros

  • check Runtime-agnostic via MCP — 30 tools available to any agent that speaks MCP, no vendor lock-in
  • check Bi-temporal episodic memory with 3-stage deduplication — more sophisticated than simple vector store approaches
  • check Portable memory: state lives in Docker volumes, not a cloud service — move between hosts without data loss
  • check Three-tier coverage: memory + reasoning vault + alignment checks in one system
  • check MIT licensed, open source, with 36+ tests and 12 audit tables for production confidence
cancel

Cons

  • close Docker required — adds infrastructure complexity for teams not already containerized
  • close v0.8 is pre-1.0 — API surface may still change significantly
  • close 30 MCP tools is a large surface area to configure and understand; steep initial learning curve
  • close "Alignment checks" and "drift detection" claims need real-world validation — these are hard problems
  • close Small community at this stage; limited production war stories

More Memory

Other tools in the same category.

View All arrow_forward