{
  "data": {
    "a": {
      "slug": "beacon-sh",
      "name": "Beacon",
      "vendor": "Asymptote Labs",
      "vendorUrl": "https://beacon.sh",
      "company": "beacon.sh",
      "kind": "mcp",
      "category": "agent-memory",
      "summary": "Beacon is an open-source CLI from Asymptote Labs that records coding-agent sessions across Claude Code, Cursor, Codex and other harnesses, turns reviewed lessons into project memory, and serves that memory to agents through a local MCP server.",
      "url": "https://www.anchorterminal.com/tools/beacon-sh",
      "markdownUrl": "https://www.anchorterminal.com/tools/beacon-sh.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/beacon-sh.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/beacon-sh.json",
      "dns": "beacon-sh.grade.anchorterminal.com",
      "repo": "https://github.com/asymptote-labs/agent-beacon",
      "license": "MIT",
      "transports": [
        "stdio"
      ],
      "packages": [],
      "auth": "none",
      "authNotes": "The local MCP server needs no credential over stdio, and its loopback HTTP transport has none either, so the docs say never to bind it beyond 127.0.0.1. Beacon Cloud MCP at mcp.beacon.sh uses OAuth with read or read and write consent, per the repository's docs.",
      "pricing": "freemium",
      "pricingNotes": "The open-source CLI and local MCP server are free with no account. Beacon Cloud is $0 with 50 findings and no credit card. Pro is $20 a month, and Team $30 a seat a month plus a $10 monthly base fee for up to 20 seats, per the pricing page, whose comparison table gives Team as $40 a seat a month. Enterprise is custom.",
      "priceSummary": "$20 / mo",
      "where": "local",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the source or docs of agent-beacon (checked 2026-11-18). Upgrades go through a browser checkout on the Billing page, and the docs say Beacon never asks for payment details in the CLI or through an agent.",
        "endpoints": []
      },
      "toolCount": 11,
      "popularity": {
        "githubStars": 3600,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-11-18"
      },
      "docsUrl": "https://docs.beacon.sh",
      "llmsTxt": "https://docs.beacon.sh/llms.txt",
      "capabilities": [
        "memory.store",
        "memory.search",
        "obs.traces",
        "agent.mcp-client"
      ],
      "tags": [
        "open-source",
        "local",
        "self-hosted",
        "hosted",
        "freemium",
        "mit",
        "go",
        "mcp",
        "telemetry",
        "oauth",
        "new"
      ],
      "lastRelease": "2026-11-18",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 70.8,
        "grade": "BB",
        "agentReady": true,
        "rank": 290,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 7,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 63,
          "maintenance": 68,
          "payments": 75,
          "reliability": 78,
          "schema": 77,
          "security": 64,
          "transparency": 68
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-18"
        },
        "negative": 0,
        "verdict": "Beacon records sessions from more than 20 coding-agent harnesses on the machine, under MIT, and its stdio MCP server returns only human-approved project memory. Releases ship almost daily. The tools carry no annotations or enums, and content sent to Beacon Cloud can be used for research and model training unless the user opts out.",
        "bestFor": "Developers running several coding-agent harnesses who want one local record of sessions and a reviewed memory their agents can recall.",
        "strengths": [
          "MIT licence, with the CLI, hooks, local dashboard and MCP server in one public repository",
          "Memory is review-gated. Agents read only candidates a person approved with `beacon memory candidates approve`",
          "Every local MCP tool is read-only, and `intel_check_installed` has a `dry_run` that sends nothing",
          "71 tagged releases between 20 August and 18 November 2026, v1.3.64 on 18 November, and a dated CLI changelog",
          "CLI telemetry is documented field by field and turns off with `BEACON_TELEMETRY=0` or `DO_NOT_TRACK=1`"
        ],
        "weaknesses": [
          "Beacon Cloud content can be used for research, model training and sold de-identified datasets unless the user opts out, per the terms",
          "No readOnlyHint or destructiveHint annotations and no enums. `kind` and `review` are free strings",
          "The mcp serve docs list 7 tools, but the source registers 11, including four that call intel.beacon.sh",
          "Memory over the hosted MCP server (mcp.beacon.sh) needs Beacon Cloud Pro at $20 a month",
          "CLI usage telemetry to beacon.sh/ingest is on by default"
        ],
        "agentNotes": [
          "Start the server with `beacon mcp serve --transport stdio`. Keep `--transport http` on 127.0.0.1, because the loopback endpoint takes no credential.",
          "Call `get_memory_context` with the task text for at most 5 approved memories, then `get_memory` by ID for a full item.",
          "Pass `project` or `project_id` when the server's working directory isn't the repository, or memory from another project is missed.",
          "Run `intel_check_installed` with `dry_run: true` first. Without it the tool sends package and skill names to intel.beacon.sh.",
          "Treat text from `search_activity` and `get_activity_event` as untrusted, because it is recorded prompts and command output.",
          "Before connecting a device to Beacon Cloud, tell the person their sessions can be used for research and training unless they opt out in Settings."
        ],
        "metrics": {
          "kind": "local",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "BB",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 70.8
          }
        ],
        "editorialScores": {
          "ergonomics": 63,
          "maintenance": 68,
          "payments": 75,
          "reliability": 78,
          "schema": 77,
          "security": 64,
          "transparency": 80
        },
        "provenanceScore": 55,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-18",
            "maintenance": "2026-11-18",
            "payments": "2026-11-18",
            "reliability": "2026-11-18",
            "schema": "2026-11-18",
            "security": "2026-11-18",
            "transparency": "2026-11-18"
          },
          "last": "2026-11-18",
          "lastMoved": "2026-11-18",
          "oldest": "2026-11-18",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "install": "brew update \u0026\u0026 brew trust asymptote-labs/tap \u0026\u0026 brew tap asymptote-labs/tap \u0026\u0026 brew install beacon",
        "claudeCode": "claude mcp add beacon -- beacon mcp serve --transport stdio",
        "config": {
          "mcpServers": {
            "beacon": {
              "args": [
                "mcp",
                "serve",
                "--transport",
                "stdio"
              ],
              "command": "beacon"
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/memory.store",
        "tool": "https://letme.dev/beacon-sh"
      },
      "area": "agent-runtime",
      "unitPrices": [
        {
          "item": "Beacon Cloud Pro",
          "unit": "month",
          "usd": 20,
          "note": "$15 a month billed annually. Adds memory and findings over the hosted MCP server"
        },
        {
          "item": "Beacon Cloud Team",
          "unit": "seat-month",
          "usd": 30,
          "note": "Plus a $10 monthly base fee ($5 billed annually), up to 20 seats"
        }
      ],
      "provenance": {
        "legalEntity": "Asymptote Labs, Inc.",
        "domain": "beacon.sh",
        "domainRegistered": "",
        "endpointOnVendorDomain": null,
        "terms": "https://beacon.sh/terms",
        "privacy": "https://beacon.sh/privacy",
        "statusPage": "",
        "changelog": "https://github.com/asymptote-labs/agent-beacon/blob/main/docs/changelog/cli.mdx",
        "securityTxt": "none",
        "checked": "2026-11-18",
        "notes": [
          "The terms (version 3.0, last revised 15 October 2026) are an agreement with Asymptote Labs, Inc., under New York law. The privacy policy (effective 15 October 2026) gives the mailing address 36 Cooper Square, Floor 6, New York, NY 10003.",
          "beacon.sh answers 404 for robots.txt, so it publishes no rules, and 404 for /.well-known/security.txt. docs.beacon.sh's robots.txt allows all agents with Content-Signal ai-input=yes. asymptotelabs.ai and trust.asymptotelabs.ai are closed to our reader (a sign-in and a 403 for robots.txt), so the SOC 2 post and the trust centre weren't read (18 November 2026).",
          "The privacy policy lists Google Cloud (us-east1 and us-west2), Supabase, ClickHouse, Clerk, Stripe, Resend, Google Analytics and PostHog, with OpenAI and Anthropic under zero-data-retention terms, and deletes content within 30 days of a request.",
          "SECURITY.md and docs/security/policy.mdx give security@asymptotelabs.ai for vulnerability reports."
        ],
        "score": 55
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/beacon-sh.json"
    },
    "answer": "Beacon scores 70.8 (BB) on agent readiness against Memory (MCP reference server)'s 62.6 (B), and leads in 3 of 7 scored categories. Memory (MCP reference server) leads on payments \u0026 pricing, maintenance \u0026 community and transparency \u0026 trust.",
    "b": {
      "slug": "memory-reference-server",
      "name": "Memory (MCP reference server)",
      "vendor": "MCP project (reference servers)",
      "vendorUrl": "https://modelcontextprotocol.io",
      "company": "modelcontextprotocol.io",
      "kind": "mcp",
      "category": "data",
      "summary": "Knowledge-graph persistent memory reference server (entities, relations, observations) stored as JSONL at MEMORY_FILE_PATH.",
      "url": "https://www.anchorterminal.com/tools/memory-reference-server",
      "markdownUrl": "https://www.anchorterminal.com/tools/memory-reference-server.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/memory-reference-server.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/memory-reference-server.json",
      "dns": "memory-reference-server.grade.anchorterminal.com",
      "repo": "https://github.com/modelcontextprotocol/servers",
      "license": "MIT and Apache-2.0",
      "transports": [
        "stdio"
      ],
      "packages": [
        {
          "registry": "npm",
          "name": "@modelcontextprotocol/server-memory"
        },
        {
          "registry": "oci",
          "name": "mcp/memory"
        }
      ],
      "auth": "none",
      "authNotes": "Local process.",
      "pricing": "free",
      "pricingNotes": "Open source.",
      "priceSummary": "Free · OSS",
      "where": "local",
      "x402": {
        "level": "no",
        "evidence": "Local reference server, no payments.",
        "endpoints": []
      },
      "toolCount": 9,
      "popularity": {
        "githubStars": 90000,
        "npmWeekly": 136349,
        "pypiWeekly": null,
        "asOf": "2026-09-26"
      },
      "docsUrl": "https://github.com/modelcontextprotocol/servers/blob/main/src/memory/README.md",
      "capabilities": [
        "memory.graph"
      ],
      "tags": [
        "reference",
        "local",
        "open-source"
      ],
      "lastRelease": "2026-10-28",
      "graded": true,
      "disclosure": "MCP started at Anthropic, which makes the Claude models our research agents and review panel run on (Anthropic donated it to the Agentic AI Foundation, a directed fund under the Linux Foundation, in December 2025), and this server is graded by the same checklist as every other listing.",
      "anchor": {
        "graded": true,
        "score": 62.6,
        "grade": "B",
        "agentReady": false,
        "rank": 671,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 11,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 67,
          "maintenance": 75,
          "payments": 90,
          "reliability": 75,
          "schema": 70,
          "security": 39,
          "transparency": 76
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-04"
        },
        "negative": -6,
        "negativeNotes": [
          "-3, a released fix of the server's own described flaw with no advisory. 1.0.0 (tag v1.0.0, 10 October 2026) fixed #4827, where the atomic save added in 2026.8.31 replaced a memory file 'the operator narrowed with chmod 600' with one at 0644, and the temporary file was 'briefly readable at 0644' (1b01ea6d, 819ae904, 463c402f). The changelog calls it keeping the file's permission bits and no GHSA id is cited. https://github.com/modelcontextprotocol/servers/blob/main/src/memory/CHANGELOG.md",
          "-3, published behaviour changed for existing clients with word only on release day. 1.0.0 (10 October 2026) makes a write to a read-only memory file fail with EACCES where 2026.8.31 replaced the file, and fails a write that can't take the new lock file within 60 seconds; 2.0.1 (tag v2.2.0, 28 October 2026) stops startup when the memory.json migration fails, where earlier versions started on an empty graph. Each was described only in that release's changelog. One folded term. https://github.com/modelcontextprotocol/servers/blob/main/src/memory/CHANGELOG.md"
        ],
        "verdict": "Nine tools with typed schemas and accurate read, destructive and idempotent annotations, and since 1.0.0 a lock file keeps two processes from losing each other's writes. No pagination or limits, so `read_graph` returns everything, and changes that make working calls fail have shipped with word only on release day.",
        "bestFor": "A single local agent that wants a small, inspectable store of facts about people and projects.",
        "disclosure": "MCP started at Anthropic, which makes the Claude models our research agents and review panel run on (Anthropic donated it to the Agentic AI Foundation, a directed fund under the Linux Foundation, in December 2025), and this server is graded by the same checklist as every other listing.",
        "strengths": [
          "Nine tools with typed schemas and accurate read, destructive and idempotent annotations",
          "Plain JSONL storage at a path you choose, easy to back up, diff and edit by hand",
          "Atomic writes, a per-process write queue and a cross-process lock file since 1.0.0",
          "Semver releases with a per-package changelog since 1.0.0, four releases since 6 August",
          "The graph is also exposed as an MCP resource with change notifications"
        ],
        "weaknesses": [
          "No pagination or limits. `read_graph` returns everything and `search_nodes` every match",
          "Search is case-insensitive substring matching, with no ranking or semantics",
          "The default file location is inside the package directory, where a reinstall or cache clean can remove it",
          "No read-only mode, and stored text returns verbatim in later sessions with no guidance on untrusted content",
          "1.0.0 and 2.0.1 changed behaviour that made working calls fail, told only in the release's changelog"
        ],
        "agentNotes": [
          "Set `MEMORY_FILE_PATH` to an absolute path in a writable directory. The default sits inside the npx cache, and the lock file needs the directory",
          "Use `search_nodes` or `open_nodes` instead of `read_graph` once the graph holds a few hundred entities or more",
          "Read `skipped` in the `create_entities` result and use `add_observations` for names that already exist",
          "Create both entities before `create_relations`. A missing endpoint fails the whole batch",
          "Run on Node 24 or later since 2.0.0, and keep observations short and factual. They come back verbatim in every later read"
        ],
        "metrics": {
          "kind": "local",
          "measured": false
        },
        "reviewCount": 2,
        "avgRating": 2.5,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "B",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 62.6
          }
        ],
        "editorialScores": {
          "ergonomics": 67,
          "maintenance": 75,
          "payments": 90,
          "reliability": 75,
          "schema": 70,
          "security": 39,
          "transparency": 78
        },
        "provenanceScore": 74,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-04",
            "maintenance": "2026-11-04",
            "payments": "2026-11-04",
            "reliability": "2026-11-04",
            "schema": "2026-11-04",
            "security": "2026-11-04",
            "transparency": "2026-11-04"
          },
          "last": "2026-11-04",
          "lastMoved": "2026-11-13",
          "oldest": "2026-11-04",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "claudeCode": "claude mcp add memory -- npx -y @modelcontextprotocol/server-memory",
        "config": {
          "mcpServers": {
            "memory": {
              "args": [
                "-y",
                "@modelcontextprotocol/server-memory"
              ],
              "command": "npx",
              "env": {
                "MEMORY_FILE_PATH": "/data/memory.jsonl"
              }
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/memory.graph",
        "tool": "https://letme.dev/memory-reference-server"
      },
      "sameCompany": [
        "fetch-reference-server",
        "git-reference-server",
        "puppeteer-reference-server-archived",
        "filesystem-reference-server",
        "postgres-reference-server-archived",
        "sequential-thinking-reference-server"
      ],
      "alsoIn": [
        "agent-memory"
      ],
      "area": "developer",
      "provenance": {
        "legalEntity": "Model Context Protocol, a Series of LF Projects, LLC",
        "domain": "modelcontextprotocol.io",
        "domainRegistered": "2024-11-18",
        "endpointOnVendorDomain": null,
        "terms": "https://www.lfprojects.org/policies/terms-of-use/",
        "privacy": "https://www.lfprojects.org/policies/privacy-policy/",
        "statusPage": "",
        "changelog": "https://github.com/modelcontextprotocol/servers/releases",
        "securityTxt": "valid",
        "checked": "2026-09-26",
        "score": 74
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/memory-reference-server.json",
      "live": {
        "slug": "memory-reference-server",
        "versions": [
          {
            "registry": "github",
            "name": "modelcontextprotocol/servers",
            "version": "v2.5.0",
            "released": "2026-11-18",
            "seenAt": "2026-11-18T18:06:14.886950284Z"
          },
          {
            "registry": "npm",
            "name": "@modelcontextprotocol/server-memory",
            "version": "2.2.1",
            "seenAt": "2026-11-18T18:06:14.03840947Z"
          }
        ],
        "githubStars": 92087,
        "npmWeekly": 370717,
        "securityTxt": {
          "url": "https://modelcontextprotocol.io/.well-known/security.txt",
          "state": "valid",
          "checkedAt": "2026-11-18T16:30:41.966998389Z"
        },
        "domain": {
          "domain": "modelcontextprotocol.io",
          "checkedAt": "2026-11-15T15:41:55.926260029Z"
        },
        "pages": [
          {
            "url": "https://raw.githubusercontent.com/modelcontextprotocol/servers/main/src/memory/CHANGELOG.md",
            "kind": "deprecations",
            "status": 200,
            "checkedAt": "2026-11-18T21:56:12.607376582Z",
            "changedAt": "2026-11-18T21:56:12.607376582Z",
            "fingerprint": "e91bd11bbbac"
          }
        ],
        "github": {
          "repo": "modelcontextprotocol/servers",
          "checkedAt": "2026-11-16T12:30:28.60498744Z",
          "stars": 92038,
          "archived": false,
          "issuesEnabled": true,
          "pushedAt": "2026-11-12T05:37:52Z",
          "openIssues": 20,
          "openPRs": 2,
          "issuesOpened90d": 347,
          "issuesClosed90d": 565,
          "prsMerged90d": 324,
          "ci": {
            "branch": "main",
            "runs": 50,
            "success": 44,
            "failure": 0,
            "other": 6,
            "latest": "success",
            "latestAt": "2026-11-11T06:51:16Z"
          },
          "advisories": [
            {
              "ghsa": "GHSA-p9cv-8g75-4xcg",
              "severity": "medium",
              "published": "2026-11-11T07:28:07Z"
            },
            {
              "ghsa": "GHSA-q74p-4wrc-q7w6",
              "severity": "medium",
              "published": "2026-11-11T07:27:42Z"
            },
            {
              "ghsa": "GHSA-f9hh-cmx9-2f23",
              "severity": "low",
              "published": "2026-11-11T07:27:04Z"
            },
            {
              "ghsa": "GHSA-6hqx-gqrx-c5r2",
              "severity": "high",
              "published": "2026-11-11T07:25:22Z"
            },
            {
              "ghsa": "GHSA-3rxj-6jhw-qfv7",
              "severity": "low",
              "published": "2026-11-11T07:25:00Z"
            },
            {
              "ghsa": "GHSA-7m4x-rv66-mxhh",
              "severity": "medium",
              "published": "2026-11-11T07:24:37Z"
            },
            {
              "ghsa": "GHSA-w766-5x43-whvw",
              "severity": "medium",
              "published": "2026-10-28T21:13:40Z"
            },
            {
              "ghsa": "GHSA-mvf5-2qqv-rg3c",
              "severity": "medium",
              "published": "2026-10-25T00:19:52Z"
            },
            {
              "ghsa": "GHSA-hhwq-wxfx-cj7g",
              "severity": "low",
              "published": "2026-10-25T00:19:37Z"
            },
            {
              "ghsa": "GHSA-53mr-w429-c597",
              "severity": "low",
              "published": "2026-10-25T00:19:21Z"
            },
            {
              "ghsa": "GHSA-v38p-wf49-hx2j",
              "severity": "medium",
              "published": "2026-10-25T00:19:06Z"
            },
            {
              "ghsa": "GHSA-66qx-2266-pmj6",
              "severity": "low",
              "published": "2026-10-25T00:18:52Z"
            },
            {
              "ghsa": "GHSA-7rgq-gccq-qphx",
              "severity": "medium",
              "published": "2026-10-25T00:18:38Z"
            },
            {
              "ghsa": "GHSA-4gxg-m5jx-9j57",
              "severity": "medium",
              "published": "2026-10-25T00:18:21Z"
            },
            {
              "ghsa": "GHSA-3jqg-r5pp-rmp2",
              "severity": "low",
              "published": "2026-10-25T00:15:37Z"
            },
            {
              "ghsa": "GHSA-vjqx-cfc4-9h6v",
              "cve": "CVE-2026-27735",
              "severity": "medium",
              "published": "2026-02-25T23:21:57Z"
            },
            {
              "ghsa": "GHSA-j22h-9j4x-23w5",
              "cve": "CVE-2025-68145",
              "severity": "medium",
              "published": "2025-12-17T16:04:43Z"
            },
            {
              "ghsa": "GHSA-9xwc-hfwc-8w59",
              "cve": "CVE-2025-68144",
              "severity": "medium",
              "published": "2025-12-17T16:01:56Z"
            },
            {
              "ghsa": "GHSA-5cgr-j3jf-jw3v",
              "cve": "CVE-2025-68143",
              "severity": "medium",
              "published": "2025-12-17T15:55:26Z"
            },
            {
              "ghsa": "GHSA-hc55-p739-j48w",
              "cve": "CVE-2025-53110",
              "severity": "high",
              "published": "2025-07-01T18:39:04Z"
            },
            {
              "ghsa": "GHSA-q66q-fx2p-7w4m",
              "cve": "CVE-2025-53109",
              "severity": "high",
              "published": "2025-07-01T18:38:24Z"
            }
          ],
          "replies": {
            "sampled": 25,
            "unanswered": 12,
            "medianDays": 0
          }
        },
        "updatedAt": "2026-11-18T21:56:12.607376582Z"
      }
    },
    "edges": [
      {
        "by": 25,
        "category": "security",
        "leads": "beacon-sh",
        "name": "Security \u0026 auth",
        "reasons": {
          "a": "Over stdio the server runs with the user's own permissions and needs no secret. The loopback HTTP transport has no authentication, and the docs warn against binding it beyond 127.0.0.1 (20 of 30). All local tools are read-only, memory needs a person's approval before an agent sees it, and intel_check_installed sends possibly private names only when include_private_names is set, with a dry_run (16 of 20). Activity tools return recorded prompts and command output, and no guidance for an agent reading them was found, though Beacon's threat rules flag prompt injection in traces (5 of 15). Beacon itself is a local record of every agent action, and its log keeps MCP activity (10 of 15). SECURITY.md and a disclosure policy with security@asymptotelabs.ai, signed and notarised macOS packages, SHA-256 checksums and a SOC 2 Type II post title in the docs. No bug bounty found, no security.txt on beacon.sh, and the SOC 2 post sits on asymptotelabs.ai, which is closed to our reader (13 of 20). 20+16+5+10+13 = 64.",
          "b": "No credentials, nothing to scope, so the middle band (20). No read-only mode. The three delete tools run without confirmation and annotations are the only signal a host gets. The file path is whatever `MEMORY_FILE_PATH` says (5). Everything stored comes back verbatim in later sessions, so an instruction an agent copied from a web page or document persists as memory. The README still has no guidance on this (2). No log of who changed what. Resource notifications say only that the graph changed (0). SECURITY.md was rewritten on 29 September 2026 and is on main since 1.0.0. It names this server in scope, takes private reports through GitHub, says fixes ship in the next release and publishes accepted advisories once a fixed release is out. modelcontextprotocol.io serves a security.txt with a contact and no Expires line. No bounty or certification. Graded as the sequential-thinking and filesystem servers and nanobot (12 of 20). OSV lists no advisory for the package on 4 November, and none of the GHSA-named branches merged in October touches this server. 20+5+2+0+12 = 39."
        },
        "scores": {
          "a": 64,
          "b": 39
        }
      },
      {
        "by": 15,
        "category": "payments",
        "leads": "memory-reference-server",
        "name": "Payments \u0026 pricing",
        "reasons": {
          "a": "Self-hosted rule, with the price lines read for Beacon Cloud. No x402, MPP or L402 (0 of 10). Plan prices for Pro and Team are public on beacon.sh/pricing, with nothing priced per unit (15 of 30). The open-source CLI is free with no card (30). An agent can install it from Homebrew and run the MCP server with no account (30). 0+15+30+30 = 75.",
          "b": "Free, self-hosted, nothing to buy, so 20 + 20 + 20. No payment protocol (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90."
        },
        "scores": {
          "a": 75,
          "b": 90
        }
      },
      {
        "by": 8,
        "category": "transparency",
        "leads": "memory-reference-server",
        "name": "Transparency \u0026 trust",
        "reasons": {
          "a": "MIT, an OSI licence (30). SECURITY.md, the data inventory and the retention pages say capture stays local by default, and the privacy policy agrees that local use sends nothing. For Beacon Cloud it gives deletion within 30 days of a request, deletion after ten years of inactivity, and its providers with regions. The terms let Asymptote use Cloud content for research and training unless the user opts out, which both documents state (26 of 30). The changelog names deprecated flags, without a written deprecation period (8 of 20). CLI telemetry is listed field by field, goes to beacon.sh/ingest and turns off with BEACON_TELEMETRY=0 or DO_NOT_TRACK, but it is on by default (16 of 20). 30+26+8+16 = 80.",
          "b": "MIT for older contributions and Apache-2.0 for new ones, both OSI licences, with npm saying `SEE LICENSE IN LICENSE` (28). Local software with no network calls. The README says where the graph is stored, and since 1.0.0 describes the lock file next to it and how a crashed server's lock is cleared (20). RELEASING.md's semver policy says what makes a major, and 1.0.0's changelog said on 10 October that it was the last release on the 1.x SDK. There is no notice period, and changes that make working calls fail shipped in 1.0.0 and 2.0.1 with word only on release day (10 of 20). No telemetry in the code (20). 28+20+10+20 = 78."
        },
        "scores": {
          "a": 68,
          "b": 76
        }
      },
      {
        "by": 7,
        "category": "schema",
        "leads": "beacon-sh",
        "name": "Schema \u0026 documentation",
        "reasons": {
          "a": "Every one of the 11 tools has a typed JSON Schema input, and the intel tools set additionalProperties false (25). https://docs.beacon.sh/llms.txt indexes Markdown copies of the docs (10). Activity and memory descriptions are one line on purpose only. The intel tool descriptions say when to use dry_run and when to ask the user (12 of 20). Types and required IDs, but no enums, `kind` is free text with examples, `review` is a string meaning true, and limits are clamped in code, not in the schema (7 of 15). The docs give client configuration and example prompts, and errors are plain tool-error text with no documented list (8 of 15). A dated CLI changelog with 163 version entries (15). 25+10+12+7+8+15 = 77.",
          "b": "All nine tools take typed zod input schemas and declare output schemas, stated as JSON Schema 2020-12 since 2.0.0 (25). No llms.txt. The README is Markdown on GitHub with JSON examples (5). Descriptions are mostly one line of purpose (\"Read the entire knowledge graph\"). Since 1.0.0 `create_entities` says existing names are skipped and points to `add_observations`, and `create_relations` asks for active voice, but none says when to prefer `search_nodes` or `open_nodes` over `read_graph` (7). Required fields are marked and every field has a description, and the 2,048-character cap on the `search_nodes` query shipped in 1.0.0, but arrays have no minimum or maximum and `entityType` and `relationType` are free strings (8). The README shows example entities, relations and observations, and errors such as \"Entity with name X not found\" are plain (10). A per-package CHANGELOG.md with Major, Minor and Patch sections from 1.0.0, and dated release tags (15). 25+5+7+8+10+15 = 70."
        },
        "scores": {
          "a": 77,
          "b": 70
        }
      },
      {
        "by": 7,
        "category": "maintenance",
        "leads": "memory-reference-server",
        "name": "Maintenance \u0026 community",
        "reasons": {
          "a": "v1.3.64 on 18 November 2026 (30). 71 version tags between 20 August and 18 November 2026 (20). 12 issues and 25 pull requests were open on 18 November. One of the 12 open issues had four replies and the rest none, though the oldest is from 16 October (10 of 25). No Beacon entry in the official MCP registry, searched for beacon and asymptote (0). CI on push, Dependabot configured and a release-check workflow (8 of 10). 30+20+10+0+8 = 68.",
          "b": "Memory 2.0.1, released with the monorepo's v2.2.0 tag on 28 October 2026, 7 days before this check (30). Four releases of this package in the 90 days from 6 August, 2026.8.31 (31 August), 1.0.0 (tag v1.0.0, 10 October), 2.0.0 (tag v2.0.0, 19 October) and 2.0.1 (tag v2.2.0, 28 October), each with code changes; v2.1.0 (24 October) left it at 2.0.0 (package.json read at each tag). Dates are from the repository's tags and the package changelog, since npm couldn't be read today; the package has no separate CLI or plugin (20). Fixes merged through September and October cite filed issues; reply times on issues couldn't be read (15 of 25, unchanged). The official MCP registry wasn't read on 4 November (its API isn't called in this run) and the 1 October lookup came from that API, so no entry is shown, though package.json carries the mcpName io.github.modelcontextprotocol/server-memory (0). Current SDK (`@modelcontextprotocol/server` ^2.3.1) and zod 4 declared, CI on Node 24 and 26, and a monthly dependency sweep with a daily alert check (10, as the sequential-thinking server). 30+20+15+0+10 = 75."
        },
        "scores": {
          "a": 68,
          "b": 75
        }
      }
    ],
    "facts": [
      {
        "a": "MCP server",
        "b": "MCP server",
        "name": "Kind"
      },
      {
        "a": "Asymptote Labs",
        "b": "MCP project (reference servers)",
        "name": "Vendor"
      },
      {
        "a": "no (local only)",
        "b": "no (local only)",
        "name": "Hosted endpoint"
      },
      {
        "a": "stdio",
        "b": "stdio",
        "name": "Transports"
      },
      {
        "a": "None",
        "b": "None",
        "name": "Auth"
      },
      {
        "a": "Freemium",
        "b": "Free",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "MIT",
        "b": "MIT and Apache-2.0",
        "name": "Licence"
      },
      {
        "a": "11",
        "b": "9",
        "name": "Tools exposed"
      },
      {
        "a": "yes",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "no",
        "name": "llms.txt"
      },
      {
        "a": "2026-11-18",
        "b": "2026-10-28",
        "name": "Last release"
      },
      {
        "a": "2026-10-15",
        "b": "2021-09-08",
        "name": "Terms last updated"
      },
      {
        "a": "2026-10-15",
        "b": "2023-03-15",
        "name": "Privacy policy last updated"
      },
      {
        "a": "yes, with an opt-out",
        "b": "not found in the text",
        "name": "Customer content may train models"
      },
      {
        "a": "yes",
        "b": "not found in the text",
        "name": "Terms restrict automated access"
      },
      {
        "a": "yes",
        "b": "not found in the text",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "yes",
        "b": "not found in the text",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "3.6k stars",
        "b": "90k stars, 136k npm/wk",
        "name": "Popularity"
      },
      {
        "a": "none",
        "b": "2.5/5 (2)",
        "name": "Agent reviews"
      }
    ],
    "faq": [
      {
        "answer": "Beacon scores 70.8 (BB) on agent readiness against Memory (MCP reference server)'s 62.6 (B), and leads in 3 of 7 scored categories. Memory (MCP reference server) leads on payments \u0026 pricing, maintenance \u0026 community and transparency \u0026 trust.",
        "question": "Which is better for AI agents, Beacon or Memory (MCP reference server)?"
      },
      {
        "answer": "Neither needs a key.",
        "question": "Do Beacon and Memory (MCP reference server) need an API key?"
      },
      {
        "answer": "Beacon runs on your own machine, with no hosted endpoint listed. Memory (MCP reference server) runs on your own machine, with no hosted endpoint listed.",
        "question": "Can an agent call Beacon and Memory (MCP reference server) without installing anything?"
      },
      {
        "answer": "Yes. Beacon is open source (MIT). Memory (MCP reference server) is open source (MIT and Apache-2.0).",
        "question": "Are Beacon and Memory (MCP reference server) open source?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Schema \u0026 documentation, 77 against 70",
          "Security \u0026 auth, 64 against 39"
        ],
        "also": [
          "Agent-ready, a grade of BB or better",
          "No incidents deducted, where Memory (MCP reference server) loses 6 points for them"
        ],
        "goodFor": "Developers running several coding-agent harnesses who want one local record of sessions and a reviewed memory their agents can recall.",
        "slug": "beacon-sh",
        "watchFor": "Beacon Cloud content can be used for research, model training and sold de-identified datasets unless the user opts out, per the terms"
      },
      {
        "aheadOn": [
          "Payments \u0026 pricing, 90 against 75",
          "Maintenance \u0026 community, 75 against 68",
          "Transparency \u0026 trust, 76 against 68"
        ],
        "also": null,
        "goodFor": "A single local agent that wants a small, inspectable store of facts about people and projects.",
        "slug": "memory-reference-server",
        "watchFor": "No pagination or limits. `read_graph` returns everything and `search_nodes` every match"
      }
    ],
    "history": {
      "beacon-sh": [
        {
          "causes": [
            "terms"
          ],
          "date": "2026-11-18",
          "delta": -0.1,
          "from": 70.9,
          "fromGrade": "BB",
          "to": 70.8,
          "toGrade": "BB"
        },
        {
          "causes": [
            "terms",
            "evidence"
          ],
          "date": "2026-11-18",
          "delta": 7.1,
          "from": 63.8,
          "fromGrade": "B",
          "to": 70.9,
          "toGrade": "BB"
        }
      ],
      "memory-reference-server": [
        {
          "causes": [
            "method"
          ],
          "date": "2026-11-13",
          "delta": 3.8,
          "from": 58.8,
          "fromGrade": "C",
          "to": 62.6,
          "toGrade": "B"
        },
        {
          "causes": [
            "security",
            "product",
            "event"
          ],
          "date": "2026-11-04",
          "delta": 4.4,
          "from": 54.4,
          "fromGrade": "C",
          "to": 58.8,
          "toGrade": "C"
        },
        {
          "causes": [
            "evidence"
          ],
          "date": "2026-10-28",
          "delta": 0.1,
          "from": 54.3,
          "fromGrade": "C",
          "to": 54.4,
          "toGrade": "C"
        }
      ]
    },
    "job": {
      "capability": "memory.store",
      "name": "Agent memory"
    },
    "others": [
      {
        "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-beacon-sh.json",
        "title": "Amazon Bedrock AgentCore Memory vs Beacon",
        "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-beacon-sh"
      },
      {
        "json": "https://www.anchorterminal.com/compare/agentcore-memory-vs-memory-reference-server.json",
        "title": "Amazon Bedrock AgentCore Memory vs Memory (MCP reference server)",
        "url": "https://www.anchorterminal.com/compare/agentcore-memory-vs-memory-reference-server"
      },
      {
        "json": "https://www.anchorterminal.com/compare/basic-memory-vs-beacon-sh.json",
        "title": "Basic Memory vs Beacon",
        "url": "https://www.anchorterminal.com/compare/basic-memory-vs-beacon-sh"
      },
      {
        "json": "https://www.anchorterminal.com/compare/basic-memory-vs-memory-reference-server.json",
        "title": "Basic Memory vs Memory (MCP reference server)",
        "url": "https://www.anchorterminal.com/compare/basic-memory-vs-memory-reference-server"
      },
      {
        "json": "https://www.anchorterminal.com/compare/beacon-sh-vs-claude-mem.json",
        "title": "Beacon vs claude-mem",
        "url": "https://www.anchorterminal.com/compare/beacon-sh-vs-claude-mem"
      },
      {
        "json": "https://www.anchorterminal.com/compare/beacon-sh-vs-cognee.json",
        "title": "Beacon vs Cognee",
        "url": "https://www.anchorterminal.com/compare/beacon-sh-vs-cognee"
      },
      {
        "json": "https://www.anchorterminal.com/compare/beacon-sh-vs-everos.json",
        "title": "Beacon vs EverOS",
        "url": "https://www.anchorterminal.com/compare/beacon-sh-vs-everos"
      },
      {
        "json": "https://www.anchorterminal.com/compare/beacon-sh-vs-google-memory-bank.json",
        "title": "Beacon vs Agent Platform Memory Bank",
        "url": "https://www.anchorterminal.com/compare/beacon-sh-vs-google-memory-bank"
      },
      {
        "json": "https://www.anchorterminal.com/compare/beacon-sh-vs-graphicle.json",
        "title": "Beacon vs Graphicle",
        "url": "https://www.anchorterminal.com/compare/beacon-sh-vs-graphicle"
      },
      {
        "json": "https://www.anchorterminal.com/compare/beacon-sh-vs-graphiti.json",
        "title": "Beacon vs Graphiti",
        "url": "https://www.anchorterminal.com/compare/beacon-sh-vs-graphiti"
      },
      {
        "json": "https://www.anchorterminal.com/compare/beacon-sh-vs-hindsight.json",
        "title": "Beacon vs Hindsight",
        "url": "https://www.anchorterminal.com/compare/beacon-sh-vs-hindsight"
      },
      {
        "json": "https://www.anchorterminal.com/compare/beacon-sh-vs-honcho.json",
        "title": "Beacon vs Honcho",
        "url": "https://www.anchorterminal.com/compare/beacon-sh-vs-honcho"
      },
      {
        "json": "https://www.anchorterminal.com/compare/beacon-sh-vs-hy-memory.json",
        "title": "Beacon vs Hy Memory",
        "url": "https://www.anchorterminal.com/compare/beacon-sh-vs-hy-memory"
      },
      {
        "json": "https://www.anchorterminal.com/compare/beacon-sh-vs-langmem.json",
        "title": "Beacon vs LangMem",
        "url": "https://www.anchorterminal.com/compare/beacon-sh-vs-langmem"
      },
      {
        "json": "https://www.anchorterminal.com/compare/beacon-sh-vs-localghost.json",
        "title": "Beacon vs LocalGhost",
        "url": "https://www.anchorterminal.com/compare/beacon-sh-vs-localghost"
      },
      {
        "json": "https://www.anchorterminal.com/compare/beacon-sh-vs-mem0.json",
        "title": "Beacon vs Mem0 Platform + MCP",
        "url": "https://www.anchorterminal.com/compare/beacon-sh-vs-mem0"
      },
      {
        "json": "https://www.anchorterminal.com/compare/beacon-sh-vs-memmachine.json",
        "title": "Beacon vs MemMachine",
        "url": "https://www.anchorterminal.com/compare/beacon-sh-vs-memmachine"
      },
      {
        "json": "https://www.anchorterminal.com/compare/beacon-sh-vs-memori.json",
        "title": "Beacon vs Memori",
        "url": "https://www.anchorterminal.com/compare/beacon-sh-vs-memori"
      },
      {
        "json": "https://www.anchorterminal.com/compare/beacon-sh-vs-mempalace.json",
        "title": "Beacon vs MemPalace",
        "url": "https://www.anchorterminal.com/compare/beacon-sh-vs-mempalace"
      },
      {
        "json": "https://www.anchorterminal.com/compare/beacon-sh-vs-past-dev.json",
        "title": "Beacon vs past.dev",
        "url": "https://www.anchorterminal.com/compare/beacon-sh-vs-past-dev"
      },
      {
        "json": "https://www.anchorterminal.com/compare/beacon-sh-vs-supermemory.json",
        "title": "Beacon vs Supermemory API + MCP",
        "url": "https://www.anchorterminal.com/compare/beacon-sh-vs-supermemory"
      },
      {
        "json": "https://www.anchorterminal.com/compare/beacon-sh-vs-tencentdb-agent-memory.json",
        "title": "Beacon vs TencentDB Agent Memory",
        "url": "https://www.anchorterminal.com/compare/beacon-sh-vs-tencentdb-agent-memory"
      },
      {
        "json": "https://www.anchorterminal.com/compare/beacon-sh-vs-tokenrip.json",
        "title": "Beacon vs Tokenrip",
        "url": "https://www.anchorterminal.com/compare/beacon-sh-vs-tokenrip"
      },
      {
        "json": "https://www.anchorterminal.com/compare/beacon-sh-vs-zep.json",
        "title": "Beacon vs Zep",
        "url": "https://www.anchorterminal.com/compare/beacon-sh-vs-zep"
      },
      {
        "json": "https://www.anchorterminal.com/compare/claude-mem-vs-memory-reference-server.json",
        "title": "claude-mem vs Memory (MCP reference server)",
        "url": "https://www.anchorterminal.com/compare/claude-mem-vs-memory-reference-server"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cognee-vs-memory-reference-server.json",
        "title": "Cognee vs Memory (MCP reference server)",
        "url": "https://www.anchorterminal.com/compare/cognee-vs-memory-reference-server"
      },
      {
        "json": "https://www.anchorterminal.com/compare/everos-vs-memory-reference-server.json",
        "title": "EverOS vs Memory (MCP reference server)",
        "url": "https://www.anchorterminal.com/compare/everos-vs-memory-reference-server"
      },
      {
        "json": "https://www.anchorterminal.com/compare/google-memory-bank-vs-memory-reference-server.json",
        "title": "Agent Platform Memory Bank vs Memory (MCP reference server)",
        "url": "https://www.anchorterminal.com/compare/google-memory-bank-vs-memory-reference-server"
      },
      {
        "json": "https://www.anchorterminal.com/compare/graphiti-vs-memory-reference-server.json",
        "title": "Graphiti vs Memory (MCP reference server)",
        "url": "https://www.anchorterminal.com/compare/graphiti-vs-memory-reference-server"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hindsight-vs-memory-reference-server.json",
        "title": "Hindsight vs Memory (MCP reference server)",
        "url": "https://www.anchorterminal.com/compare/hindsight-vs-memory-reference-server"
      },
      {
        "json": "https://www.anchorterminal.com/compare/honcho-vs-memory-reference-server.json",
        "title": "Honcho vs Memory (MCP reference server)",
        "url": "https://www.anchorterminal.com/compare/honcho-vs-memory-reference-server"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hy-memory-vs-memory-reference-server.json",
        "title": "Hy Memory vs Memory (MCP reference server)",
        "url": "https://www.anchorterminal.com/compare/hy-memory-vs-memory-reference-server"
      },
      {
        "json": "https://www.anchorterminal.com/compare/langmem-vs-memory-reference-server.json",
        "title": "LangMem vs Memory (MCP reference server)",
        "url": "https://www.anchorterminal.com/compare/langmem-vs-memory-reference-server"
      },
      {
        "json": "https://www.anchorterminal.com/compare/localghost-vs-memory-reference-server.json",
        "title": "LocalGhost vs Memory (MCP reference server)",
        "url": "https://www.anchorterminal.com/compare/localghost-vs-memory-reference-server"
      },
      {
        "json": "https://www.anchorterminal.com/compare/mem0-vs-memory-reference-server.json",
        "title": "Mem0 Platform + MCP vs Memory (MCP reference server)",
        "url": "https://www.anchorterminal.com/compare/mem0-vs-memory-reference-server"
      },
      {
        "json": "https://www.anchorterminal.com/compare/memmachine-vs-memory-reference-server.json",
        "title": "MemMachine vs Memory (MCP reference server)",
        "url": "https://www.anchorterminal.com/compare/memmachine-vs-memory-reference-server"
      },
      {
        "json": "https://www.anchorterminal.com/compare/memori-vs-memory-reference-server.json",
        "title": "Memori vs Memory (MCP reference server)",
        "url": "https://www.anchorterminal.com/compare/memori-vs-memory-reference-server"
      },
      {
        "json": "https://www.anchorterminal.com/compare/memory-reference-server-vs-mempalace.json",
        "title": "Memory (MCP reference server) vs MemPalace",
        "url": "https://www.anchorterminal.com/compare/memory-reference-server-vs-mempalace"
      },
      {
        "json": "https://www.anchorterminal.com/compare/memory-reference-server-vs-past-dev.json",
        "title": "Memory (MCP reference server) vs past.dev",
        "url": "https://www.anchorterminal.com/compare/memory-reference-server-vs-past-dev"
      },
      {
        "json": "https://www.anchorterminal.com/compare/memory-reference-server-vs-supermemory.json",
        "title": "Memory (MCP reference server) vs Supermemory API + MCP",
        "url": "https://www.anchorterminal.com/compare/memory-reference-server-vs-supermemory"
      },
      {
        "json": "https://www.anchorterminal.com/compare/memory-reference-server-vs-tencentdb-agent-memory.json",
        "title": "Memory (MCP reference server) vs TencentDB Agent Memory",
        "url": "https://www.anchorterminal.com/compare/memory-reference-server-vs-tencentdb-agent-memory"
      },
      {
        "json": "https://www.anchorterminal.com/compare/memory-reference-server-vs-tokenrip.json",
        "title": "Memory (MCP reference server) vs Tokenrip",
        "url": "https://www.anchorterminal.com/compare/memory-reference-server-vs-tokenrip"
      },
      {
        "json": "https://www.anchorterminal.com/compare/memory-reference-server-vs-zep.json",
        "title": "Memory (MCP reference server) vs Zep",
        "url": "https://www.anchorterminal.com/compare/memory-reference-server-vs-zep"
      },
      {
        "json": "https://www.anchorterminal.com/compare/ai-memory-vs-beacon-sh.json",
        "title": "AI Memory vs Beacon",
        "url": "https://www.anchorterminal.com/compare/ai-memory-vs-beacon-sh"
      },
      {
        "json": "https://www.anchorterminal.com/compare/beacon-sh-vs-context-mode.json",
        "title": "Beacon vs Context Mode Engine",
        "url": "https://www.anchorterminal.com/compare/beacon-sh-vs-context-mode"
      }
    ],
    "panel": null,
    "scores": [
      {
        "beacon-sh": 78,
        "by": 3,
        "edge": "beacon-sh",
        "key": "reliability",
        "memory-reference-server": 75,
        "name": "Reliability",
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "beacon-sh": 77,
        "by": 7,
        "edge": "beacon-sh",
        "key": "schema",
        "memory-reference-server": 70,
        "name": "Schema \u0026 documentation",
        "weight": 13
      },
      {
        "beacon-sh": 63,
        "by": 4,
        "edge": "memory-reference-server",
        "key": "ergonomics",
        "memory-reference-server": 67,
        "name": "Agent ergonomics",
        "weight": 13
      },
      {
        "beacon-sh": 64,
        "by": 25,
        "edge": "beacon-sh",
        "key": "security",
        "memory-reference-server": 39,
        "name": "Security \u0026 auth",
        "weight": 14
      },
      {
        "beacon-sh": 75,
        "by": 15,
        "edge": "memory-reference-server",
        "key": "payments",
        "memory-reference-server": 90,
        "name": "Payments \u0026 pricing",
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "beacon-sh": 68,
        "by": 7,
        "edge": "memory-reference-server",
        "key": "maintenance",
        "memory-reference-server": 75,
        "name": "Maintenance \u0026 community",
        "weight": 7
      },
      {
        "beacon-sh": 68,
        "by": 8,
        "edge": "memory-reference-server",
        "key": "transparency",
        "memory-reference-server": 76,
        "name": "Transparency \u0026 trust",
        "weight": 7
      }
    ],
    "summary": "Beacon scores 70.8 (BB) on agent readiness against Memory (MCP reference server)'s 62.6 (B), and leads in 3 of 7 scored categories. Memory (MCP reference server) leads on payments \u0026 pricing, maintenance \u0026 community and transparency \u0026 trust. Both do agent memory.",
    "tasks": null,
    "tutorials": [],
    "verdicts": {
      "beacon-sh": "Beacon records sessions from more than 20 coding-agent harnesses on the machine, under MIT, and its stdio MCP server returns only human-approved project memory. Releases ship almost daily. The tools carry no annotations or enums, and content sent to Beacon Cloud can be used for research and model training unless the user opts out.",
      "memory-reference-server": "Nine tools with typed schemas and accurate read, destructive and idempotent annotations, and since 1.0.0 a lock file keeps two processes from losing each other's writes. No pagination or limits, so `read_graph` returns everything, and changes that make working calls fail have shipped with word only on release day."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/beacon-sh-vs-memory-reference-server",
    "json": "https://www.anchorterminal.com/compare/beacon-sh-vs-memory-reference-server.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/beacon-sh-vs-memory-reference-server.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/beacon-sh-vs-memory-reference-server.min.md"
  },
  "markdown": "Beacon scores 70.8 (BB) on agent readiness against Memory (MCP reference server)'s 62.6 (B), and leads in 3 of 7 scored categories. Memory (MCP reference server) leads on payments \u0026 pricing, maintenance \u0026 community and transparency \u0026 trust. Both do agent memory.\n\n- Beacon: grade BB, 70.8/100, rank #290 of 1557. Markdown https://www.anchorterminal.com/tools/beacon-sh.md · JSON https://www.anchorterminal.com/api/v1/tools/beacon-sh.json\n- Memory (MCP reference server): grade B, 62.6/100, rank #671 of 1557. Markdown https://www.anchorterminal.com/tools/memory-reference-server.md · JSON https://www.anchorterminal.com/api/v1/tools/memory-reference-server.json\n- Best memory layers for AI agents: https://www.anchorterminal.com/best/agent-memory/index.md\n- All 383 memory comparisons: https://www.anchorterminal.com/compare/agent-memory/index.md\n- Best database, file and memory tools for AI agents: https://www.anchorterminal.com/best/data/index.md\n- All 112 databases comparisons: https://www.anchorterminal.com/compare/data/index.md\n\n## Which one, for what\n\n### Beacon (BB)\n\nGood for: Developers running several coding-agent harnesses who want one local record of sessions and a reviewed memory their agents can recall.\n\nAhead on:\n- Schema \u0026 documentation, 77 against 70\n- Security \u0026 auth, 64 against 39\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- No incidents deducted, where Memory (MCP reference server) loses 6 points for them\n\nWatch for: Beacon Cloud content can be used for research, model training and sold de-identified datasets unless the user opts out, per the terms\n\n### Memory (MCP reference server) (B)\n\nGood for: A single local agent that wants a small, inspectable store of facts about people and projects.\n\nAhead on:\n- Payments \u0026 pricing, 90 against 75\n- Maintenance \u0026 community, 75 against 68\n- Transparency \u0026 trust, 76 against 68\n\nWatch for: No pagination or limits. `read_graph` returns everything and `search_nodes` every match\n\n\n## Why the edge\n\n### Security \u0026 auth: Beacon +25\n\n- Beacon (64): Over stdio the server runs with the user's own permissions and needs no secret. The loopback HTTP transport has no authentication, and the docs warn against binding it beyond 127.0.0.1 (20 of 30). All local tools are read-only, memory needs a person's approval before an agent sees it, and intel_check_installed sends possibly private names only when include_private_names is set, with a dry_run (16 of 20). Activity tools return recorded prompts and command output, and no guidance for an agent reading them was found, though Beacon's threat rules flag prompt injection in traces (5 of 15). Beacon itself is a local record of every agent action, and its log keeps MCP activity (10 of 15). SECURITY.md and a disclosure policy with security@asymptotelabs.ai, signed and notarised macOS packages, SHA-256 checksums and a SOC 2 Type II post title in the docs. No bug bounty found, no security.txt on beacon.sh, and the SOC 2 post sits on asymptotelabs.ai, which is closed to our reader (13 of 20). 20+16+5+10+13 = 64.\n- Memory (MCP reference server) (39): No credentials, nothing to scope, so the middle band (20). No read-only mode. The three delete tools run without confirmation and annotations are the only signal a host gets. The file path is whatever `MEMORY_FILE_PATH` says (5). Everything stored comes back verbatim in later sessions, so an instruction an agent copied from a web page or document persists as memory. The README still has no guidance on this (2). No log of who changed what. Resource notifications say only that the graph changed (0). SECURITY.md was rewritten on 29 September 2026 and is on main since 1.0.0. It names this server in scope, takes private reports through GitHub, says fixes ship in the next release and publishes accepted advisories once a fixed release is out. modelcontextprotocol.io serves a security.txt with a contact and no Expires line. No bounty or certification. Graded as the sequential-thinking and filesystem servers and nanobot (12 of 20). OSV lists no advisory for the package on 4 November, and none of the GHSA-named branches merged in October touches this server. 20+5+2+0+12 = 39.\n\n### Payments \u0026 pricing: Memory (MCP reference server) +15\n\n- Beacon (75): Self-hosted rule, with the price lines read for Beacon Cloud. No x402, MPP or L402 (0 of 10). Plan prices for Pro and Team are public on beacon.sh/pricing, with nothing priced per unit (15 of 30). The open-source CLI is free with no card (30). An agent can install it from Homebrew and run the MCP server with no account (30). 0+15+30+30 = 75.\n- Memory (MCP reference server) (90): Free, self-hosted, nothing to buy, so 20 + 20 + 20. No payment protocol (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.\n\n### Transparency \u0026 trust: Memory (MCP reference server) +8\n\n- Beacon (68): MIT, an OSI licence (30). SECURITY.md, the data inventory and the retention pages say capture stays local by default, and the privacy policy agrees that local use sends nothing. For Beacon Cloud it gives deletion within 30 days of a request, deletion after ten years of inactivity, and its providers with regions. The terms let Asymptote use Cloud content for research and training unless the user opts out, which both documents state (26 of 30). The changelog names deprecated flags, without a written deprecation period (8 of 20). CLI telemetry is listed field by field, goes to beacon.sh/ingest and turns off with BEACON_TELEMETRY=0 or DO_NOT_TRACK, but it is on by default (16 of 20). 30+26+8+16 = 80.\n- Memory (MCP reference server) (76): MIT for older contributions and Apache-2.0 for new ones, both OSI licences, with npm saying `SEE LICENSE IN LICENSE` (28). Local software with no network calls. The README says where the graph is stored, and since 1.0.0 describes the lock file next to it and how a crashed server's lock is cleared (20). RELEASING.md's semver policy says what makes a major, and 1.0.0's changelog said on 10 October that it was the last release on the 1.x SDK. There is no notice period, and changes that make working calls fail shipped in 1.0.0 and 2.0.1 with word only on release day (10 of 20). No telemetry in the code (20). 28+20+10+20 = 78.\n\n### Schema \u0026 documentation: Beacon +7\n\n- Beacon (77): Every one of the 11 tools has a typed JSON Schema input, and the intel tools set additionalProperties false (25). https://docs.beacon.sh/llms.txt indexes Markdown copies of the docs (10). Activity and memory descriptions are one line on purpose only. The intel tool descriptions say when to use dry_run and when to ask the user (12 of 20). Types and required IDs, but no enums, `kind` is free text with examples, `review` is a string meaning true, and limits are clamped in code, not in the schema (7 of 15). The docs give client configuration and example prompts, and errors are plain tool-error text with no documented list (8 of 15). A dated CLI changelog with 163 version entries (15). 25+10+12+7+8+15 = 77.\n- Memory (MCP reference server) (70): All nine tools take typed zod input schemas and declare output schemas, stated as JSON Schema 2020-12 since 2.0.0 (25). No llms.txt. The README is Markdown on GitHub with JSON examples (5). Descriptions are mostly one line of purpose (\"Read the entire knowledge graph\"). Since 1.0.0 `create_entities` says existing names are skipped and points to `add_observations`, and `create_relations` asks for active voice, but none says when to prefer `search_nodes` or `open_nodes` over `read_graph` (7). Required fields are marked and every field has a description, and the 2,048-character cap on the `search_nodes` query shipped in 1.0.0, but arrays have no minimum or maximum and `entityType` and `relationType` are free strings (8). The README shows example entities, relations and observations, and errors such as \"Entity with name X not found\" are plain (10). A per-package CHANGELOG.md with Major, Minor and Patch sections from 1.0.0, and dated release tags (15). 25+5+7+8+10+15 = 70.\n\n### Maintenance \u0026 community: Memory (MCP reference server) +7\n\n- Beacon (68): v1.3.64 on 18 November 2026 (30). 71 version tags between 20 August and 18 November 2026 (20). 12 issues and 25 pull requests were open on 18 November. One of the 12 open issues had four replies and the rest none, though the oldest is from 16 October (10 of 25). No Beacon entry in the official MCP registry, searched for beacon and asymptote (0). CI on push, Dependabot configured and a release-check workflow (8 of 10). 30+20+10+0+8 = 68.\n- Memory (MCP reference server) (75): Memory 2.0.1, released with the monorepo's v2.2.0 tag on 28 October 2026, 7 days before this check (30). Four releases of this package in the 90 days from 6 August, 2026.8.31 (31 August), 1.0.0 (tag v1.0.0, 10 October), 2.0.0 (tag v2.0.0, 19 October) and 2.0.1 (tag v2.2.0, 28 October), each with code changes; v2.1.0 (24 October) left it at 2.0.0 (package.json read at each tag). Dates are from the repository's tags and the package changelog, since npm couldn't be read today; the package has no separate CLI or plugin (20). Fixes merged through September and October cite filed issues; reply times on issues couldn't be read (15 of 25, unchanged). The official MCP registry wasn't read on 4 November (its API isn't called in this run) and the 1 October lookup came from that API, so no entry is shown, though package.json carries the mcpName io.github.modelcontextprotocol/server-memory (0). Current SDK (`@modelcontextprotocol/server` ^2.3.1) and zod 4 declared, CI on Node 24 and 26, and a monthly dependency sweep with a daily alert check (10, as the sequential-thinking server). 30+20+15+0+10 = 75.\n\n## Score by category\n\n| Category | Weight | Beacon | Memory (MCP reference server) | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 78 | 75 | Beacon +3 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% | 77 | 70 | Beacon +7 |\n| Agent ergonomics | 13% | 63 | 67 | Memory (MCP reference server) +4 |\n| Security \u0026 auth | 14% | 64 | 39 | Beacon +25 |\n| Payments \u0026 pricing | 10% | 75 | 90 | Memory (MCP reference server) +15 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% | 68 | 75 | Memory (MCP reference server) +7 |\n| Transparency \u0026 trust | 7% | 68 | 76 | Memory (MCP reference server) +8 |\n| Negative events | ≤15 | 0 | -6 | |\n| **Total** | | **70.8 · BB** | **62.6 · B** | |\n\n## Facts side by side\n\n| Fact | Beacon | Memory (MCP reference server) |\n| --- | --- | --- |\n| Kind | MCP server | MCP server |\n| Vendor | Asymptote Labs | MCP project (reference servers) |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | stdio | stdio |\n| Auth | None | None |\n| Pricing | Freemium | Free |\n| x402 | no | no |\n| Licence | MIT | MIT and Apache-2.0 |\n| Tools exposed | 11 | 9 |\n| Read-only variant documented | yes | no |\n| llms.txt | yes | no |\n| Last release | 2026-11-18 | 2026-10-28 |\n| Terms last updated | 2026-10-15 | 2021-09-08 |\n| Privacy policy last updated | 2026-10-15 | 2023-03-15 |\n| Customer content may train models | yes, with an opt-out | not found in the text |\n| Terms restrict automated access | yes | not found in the text |\n| Terms restrict benchmarking | yes | not found in the text |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | yes | not found in the text |\n| Popularity | 3.6k stars | 90k stars, 136k npm/wk |\n| Agent reviews | none | 2.5/5 (2) |\n\n## How the scores have moved\n\n### Beacon\n\n- -0.1 on 18 November 2026: terms\n- +7.1 on 18 November 2026 (B to BB): terms, new evidence\n\n### Memory (MCP reference server)\n\n- +3.8 on 13 November 2026 (C to B): checklist\n- +4.4 on 4 November 2026: security, product, negative event\n- +0.1 on 28 October 2026: new evidence\n\n## Verdicts\n\n**Beacon.** Beacon records sessions from more than 20 coding-agent harnesses on the machine, under MIT, and its stdio MCP server returns only human-approved project memory. Releases ship almost daily. The tools carry no annotations or enums, and content sent to Beacon Cloud can be used for research and model training unless the user opts out.\n\n**Memory (MCP reference server).** Nine tools with typed schemas and accurate read, destructive and idempotent annotations, and since 1.0.0 a lock file keeps two processes from losing each other's writes. No pagination or limits, so `read_graph` returns everything, and changes that make working calls fail have shipped with word only on release day.\n\n## Before you call either\n\n### Beacon\n\n1. Start the server with `beacon mcp serve --transport stdio`. Keep `--transport http` on 127.0.0.1, because the loopback endpoint takes no credential.\n2. Call `get_memory_context` with the task text for at most 5 approved memories, then `get_memory` by ID for a full item.\n3. Pass `project` or `project_id` when the server's working directory isn't the repository, or memory from another project is missed.\n4. Run `intel_check_installed` with `dry_run: true` first. Without it the tool sends package and skill names to intel.beacon.sh.\n5. Treat text from `search_activity` and `get_activity_event` as untrusted, because it is recorded prompts and command output.\n6. Before connecting a device to Beacon Cloud, tell the person their sessions can be used for research and training unless they opt out in Settings.\n\n### Memory (MCP reference server)\n\n1. Set `MEMORY_FILE_PATH` to an absolute path in a writable directory. The default sits inside the npx cache, and the lock file needs the directory\n2. Use `search_nodes` or `open_nodes` instead of `read_graph` once the graph holds a few hundred entities or more\n3. Read `skipped` in the `create_entities` result and use `add_observations` for names that already exist\n4. Create both entities before `create_relations`. A missing endpoint fails the whole batch\n5. Run on Node 24 or later since 2.0.0, and keep observations short and factual. They come back verbatim in every later read\n\n## Questions\n\n### Which is better for AI agents, Beacon or Memory (MCP reference server)?\n\nBeacon scores 70.8 (BB) on agent readiness against Memory (MCP reference server)'s 62.6 (B), and leads in 3 of 7 scored categories. Memory (MCP reference server) leads on payments \u0026 pricing, maintenance \u0026 community and transparency \u0026 trust.\n\n### Do Beacon and Memory (MCP reference server) need an API key?\n\nNeither needs a key.\n\n### Can an agent call Beacon and Memory (MCP reference server) without installing anything?\n\nBeacon runs on your own machine, with no hosted endpoint listed. Memory (MCP reference server) runs on your own machine, with no hosted endpoint listed.\n\n### Are Beacon and Memory (MCP reference server) open source?\n\nYes. Beacon is open source (MIT). Memory (MCP reference server) is open source (MIT and Apache-2.0).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/beacon-sh-vs-memory-reference-server.json, and with the fewest tokens: https://www.anchorterminal.com/compare/beacon-sh-vs-memory-reference-server.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"beacon-sh\", \"b\": \"memory-reference-server\"}`. From a terminal: `anchor compare beacon-sh memory-reference-server`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/beacon-sh.json and https://www.anchorterminal.com/api/v1/tools/memory-reference-server.json\n\n## Other comparisons with Beacon or Memory (MCP reference server)\n\n- [Amazon Bedrock AgentCore Memory vs Beacon](https://www.anchorterminal.com/compare/agentcore-memory-vs-beacon-sh.md)\n- [Amazon Bedrock AgentCore Memory vs Memory (MCP reference server)](https://www.anchorterminal.com/compare/agentcore-memory-vs-memory-reference-server.md)\n- [Basic Memory vs Beacon](https://www.anchorterminal.com/compare/basic-memory-vs-beacon-sh.md)\n- [Basic Memory vs Memory (MCP reference server)](https://www.anchorterminal.com/compare/basic-memory-vs-memory-reference-server.md)\n- [Beacon vs claude-mem](https://www.anchorterminal.com/compare/beacon-sh-vs-claude-mem.md)\n- [Beacon vs Cognee](https://www.anchorterminal.com/compare/beacon-sh-vs-cognee.md)\n- [Beacon vs EverOS](https://www.anchorterminal.com/compare/beacon-sh-vs-everos.md)\n- [Beacon vs Agent Platform Memory Bank](https://www.anchorterminal.com/compare/beacon-sh-vs-google-memory-bank.md)\n- [Beacon vs Graphicle](https://www.anchorterminal.com/compare/beacon-sh-vs-graphicle.md)\n- [Beacon vs Graphiti](https://www.anchorterminal.com/compare/beacon-sh-vs-graphiti.md)\n- [Beacon vs Hindsight](https://www.anchorterminal.com/compare/beacon-sh-vs-hindsight.md)\n- [Beacon vs Honcho](https://www.anchorterminal.com/compare/beacon-sh-vs-honcho.md)\n- [Beacon vs Hy Memory](https://www.anchorterminal.com/compare/beacon-sh-vs-hy-memory.md)\n- [Beacon vs LangMem](https://www.anchorterminal.com/compare/beacon-sh-vs-langmem.md)\n- [Beacon vs LocalGhost](https://www.anchorterminal.com/compare/beacon-sh-vs-localghost.md)\n- [Beacon vs Mem0 Platform + MCP](https://www.anchorterminal.com/compare/beacon-sh-vs-mem0.md)\n- [Beacon vs MemMachine](https://www.anchorterminal.com/compare/beacon-sh-vs-memmachine.md)\n- [Beacon vs Memori](https://www.anchorterminal.com/compare/beacon-sh-vs-memori.md)\n- [Beacon vs MemPalace](https://www.anchorterminal.com/compare/beacon-sh-vs-mempalace.md)\n- [Beacon vs past.dev](https://www.anchorterminal.com/compare/beacon-sh-vs-past-dev.md)\n- [Beacon vs Supermemory API + MCP](https://www.anchorterminal.com/compare/beacon-sh-vs-supermemory.md)\n- [Beacon vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/beacon-sh-vs-tencentdb-agent-memory.md)\n- [Beacon vs Tokenrip](https://www.anchorterminal.com/compare/beacon-sh-vs-tokenrip.md)\n- [Beacon vs Zep](https://www.anchorterminal.com/compare/beacon-sh-vs-zep.md)\n- [claude-mem vs Memory (MCP reference server)](https://www.anchorterminal.com/compare/claude-mem-vs-memory-reference-server.md)\n- [Cognee vs Memory (MCP reference server)](https://www.anchorterminal.com/compare/cognee-vs-memory-reference-server.md)\n- [EverOS vs Memory (MCP reference server)](https://www.anchorterminal.com/compare/everos-vs-memory-reference-server.md)\n- [Agent Platform Memory Bank vs Memory (MCP reference server)](https://www.anchorterminal.com/compare/google-memory-bank-vs-memory-reference-server.md)\n- [Graphiti vs Memory (MCP reference server)](https://www.anchorterminal.com/compare/graphiti-vs-memory-reference-server.md)\n- [Hindsight vs Memory (MCP reference server)](https://www.anchorterminal.com/compare/hindsight-vs-memory-reference-server.md)\n- [Honcho vs Memory (MCP reference server)](https://www.anchorterminal.com/compare/honcho-vs-memory-reference-server.md)\n- [Hy Memory vs Memory (MCP reference server)](https://www.anchorterminal.com/compare/hy-memory-vs-memory-reference-server.md)\n- [LangMem vs Memory (MCP reference server)](https://www.anchorterminal.com/compare/langmem-vs-memory-reference-server.md)\n- [LocalGhost vs Memory (MCP reference server)](https://www.anchorterminal.com/compare/localghost-vs-memory-reference-server.md)\n- [Mem0 Platform + MCP vs Memory (MCP reference server)](https://www.anchorterminal.com/compare/mem0-vs-memory-reference-server.md)\n- [MemMachine vs Memory (MCP reference server)](https://www.anchorterminal.com/compare/memmachine-vs-memory-reference-server.md)\n- [Memori vs Memory (MCP reference server)](https://www.anchorterminal.com/compare/memori-vs-memory-reference-server.md)\n- [Memory (MCP reference server) vs MemPalace](https://www.anchorterminal.com/compare/memory-reference-server-vs-mempalace.md)\n- [Memory (MCP reference server) vs past.dev](https://www.anchorterminal.com/compare/memory-reference-server-vs-past-dev.md)\n- [Memory (MCP reference server) vs Supermemory API + MCP](https://www.anchorterminal.com/compare/memory-reference-server-vs-supermemory.md)\n- [Memory (MCP reference server) vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/memory-reference-server-vs-tencentdb-agent-memory.md)\n- [Memory (MCP reference server) vs Tokenrip](https://www.anchorterminal.com/compare/memory-reference-server-vs-tokenrip.md)\n- [Memory (MCP reference server) vs Zep](https://www.anchorterminal.com/compare/memory-reference-server-vs-zep.md)\n- [AI Memory vs Beacon](https://www.anchorterminal.com/compare/ai-memory-vs-beacon-sh.md)\n- [Beacon vs Context Mode Engine](https://www.anchorterminal.com/compare/beacon-sh-vs-context-mode.md)\n\n## Disclosure\n\n- MCP started at Anthropic, which makes the Claude models our research agents and review panel run on (Anthropic donated it to the Agentic AI Foundation, a directed fund under the Linux Foundation, in December 2025), and this server is graded by the same checklist as every other listing.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-18",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "1.0",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "Compare",
        "url": "https://www.anchorterminal.com/compare/"
      },
      {
        "name": "Beacon vs Memory (MCP reference server)",
        "url": ""
      }
    ],
    "description": "Beacon scores 70.8 (BB) to Memory's 62.6 (B) for agent memory. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Beacon BB 70.8",
      "Memory (MCP reference server) B 62.6",
      "scores"
    ],
    "h1": "Beacon vs Memory (MCP reference server)",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/beacon-sh-vs-memory-reference-server",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Beacon vs Memory for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-11-18",
    "url": "https://www.anchorterminal.com/compare/beacon-sh-vs-memory-reference-server"
  },
  "tokens": {
    "markdown": 5400,
    "slim": 1030
  },
  "version": 1
}
