MCP100 IndexMCP Server
WatchlistCommunity implementation

Second Brain

by Rahil P

Reviewed October 5, 2026

MCP Server

Watchlist tracking

Reviewed for relevance and future tracking value.

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow deployment and storage changes because hosted memory handling is central

Reviewed · Documentation review; complete setup workflow not independently tested

Best fit

Self-hosted semantic memory shared across multiple AI tools

What we know

Self-hosted memory layer on Cloudflare Workers/D1/Vectorize that lets multiple MCP-compatible AI tools share persistent personal/team context.

Maintenance / activity evidence

  • Observed (UTC)Merge pull request 383 from rahilp/release/4.0.0

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

Activity source · commits ↗Activity source · releases ↗

Verification gaps / watch-outs

  • Installation and comprehensive security have not been independently audited.
  • Personal/team layer permissions and connected integrations. Writes: Store/update/delete memory depending on tools.
  • Deployment-specific.
  • Sensitive access: Long-lived personal/team memory, Integration credentials
  • Self-hosting improves control, but this is durable centralized memory and should be protected like a knowledge database.
Security source · repository notice ↗

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

Popularity

786 repository stars

Stars observed Sep 25, 2026.

Preserve any already-reviewed adoption metrics in MCP100. Batch 4 did not refresh package downloads because the package-stats provider had insufficient credits.

Preserve any already-reviewed adoption metrics in MCP100. Batch 4 did not refresh package downloads because the package-stats provider had insufficient credits.

All limitations / Review context

What MCP memory operations and data-hosting boundaries are documented?

The bounded assessment reviewed the official README, repository notices, security policy path, and security page for known material public-tracking blockers. No such blocker was identified. This is a public-tracking assessment, not an installation safety certification.

  • Self-hosting improves control, but this is durable centralized memory and should be protected like a knowledge database.
  • Personal/team layer permissions and connected integrations.
  • Deployment-specific.
  • Project states data remains in the user's Cloudflare account and is not visible to maintainers.
  • Reviewed write actions: Store/update/delete memory depending on tools
  • Sensitive access: Long-lived personal/team memory, Integration credentials
  • Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
  • A project-specific SECURITY.md policy was not available at the fetched official path; the review remains limited to published repository notices.
  • No installation, runtime, client matrix, or complete tool-contract audit was performed in this review.
  • The fetched official SECURITY.md path returned HTTP 404; it was not treated as positive evidence.
  • Cloudflare account/infrastructure required for hosted memory.
  • Memories persist in operator-owned Cloudflare resources.

Original activity observations

  • 2026-10-03T13:13:25Z: Merge pull request 383 from rahilp/release/4.0.0
Technical identity
github.com/rahilp/second-brain-cloudflare
Reviewed resource type
MCP Server
Repository identity
rahilp/second-brain-cloudflare

Evidence & Sources

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

Reviewed · Latest source observation