Brain Protocol

Created By
seritalien3 months ago
Verifiable Memory-as-a-Service for AI agents. Persistent, searchable, graph-connected knowledge with optional Starknet on-chain proofs. Works locally with zero config (SQLite) or in cloud mode.
Overview

Description
Verifiable Memory-as-a-Service for AI agents. Persistent, searchable, graph-connected knowledge with optional Starknet on-chain proofs. Works locally with zero config (SQLite) or in cloud mode.

Tags memory,knowledge-graph,starknet,sqlite,verifiable,ai-agents,mcp

Avatar URL https://brain.api.vauban.tech/favicon.ico (or leave blank if that 404s)

Content (the full description shown on the listing page): Brain Protocol gives any MCP-compatible AI agent persistent, verifiable memory.

25 tools — query, archive, graph traversal, decisions, Starknet proofs, curation.

Two modes:

  • Local SQLite (zero config): npx @brain-protocol/mcp
  • Cloud mode: full knowledge graph, FTS, semantic search, blockchain anchoring

Compatible with: Claude Desktop, Claude Code, Cursor, Windsurf, Continue

Key features:

  • Full-text + semantic search
  • Graph edges: derives_from, extends, validates, conflicts_with
  • SHA-256 content addressing + Starknet proof anchoring
  • Brain Sync (git-style bidirectional sync)
  • MIT licensed, TypeScript, actively maintained

Server Config

{
  "mcpServers": {
    "brain": {
      "command": "npx",
      "args": [
        "-y",
        "@brain-protocol/mcp"
      ],
      "env": {
        "BRAIN_API_URL": "",
        "BRAIN_API_KEY": ""
      }
    }
  }
}
Project Info
Created At
3 months ago
Updated At
3 months ago
Author Name
seritalien
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago