Skip to content

MemBrowse MCP server

com.membrowse/membrowsemembrowse.comstreamable-httpv1.0.0Scanned

Firmware FLASH/RAM history, build diffs, symbol sizes and benchmarks for embedded projects

8 tools: 8 only read.

Tools: 0 delete, 0 irreversible, 0 write, 8 read.
  • Reads private data · 6
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the MemBrowse MCP server can do

The MemBrowse MCP server is published by membrowse.com, a domain the MCP Registry verified. It has 8 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

6 tools read private data (list_targets, get_commit_summary, get_memory_history and 3 more); 1 tool brings in text other people can write (list_projects).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 20, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

8 tools

Only reads 8Show 8 read-only tools
  • compare_buildsCompare two builds of a target.No findings

    Why it is in this group

    • The name "compare_builds" says "compare": a word for reading.
    Description, as the server wrote it
    Compare two builds of a target. Always returns each region's old and new size; 'level' adds the changed sections, source files or symbols, sorted by size of change. Without 'base', the head is compared with the build it was compared with when it was uploaded: for a pull request's head commit that is the tip of the PR's base branch, so the result is the whole PR; for a pushed commit it is the branch's previous build, so the result is what that one commit did. With 'base_target', the base is a build of another target instead, to see which target already does without a symbol.

    Annotations the server declares

    • title: Compare builds
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • export_symbolsGet one build's whole symbol table as a file, to analyse with code (Python, pandas, DuckDB, jq) when the other tools cannot answer the question.Reads private dataNo findings

    Why it is in this group

    • The description's first verb is "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "get" and "table": it reads databases.
    Description, as the server wrote it
    Get one build's whole symbol table as a file, to analyse with code (Python, pandas, DuckDB, jq) when the other tools cannot answer the question. Returns a one-time download, not the symbols: run the returned 'command' in a shell to save the file, then work on the file, so the table never enters the conversation. Needs a shell that can reach the MemBrowse server.

    Annotations the server declares

    • title: Export symbol table
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_commit_summaryFor one commit, show every target's memory change against its base build: per region, the largest section and source-file changes, budget alerts, and, for targets with benchmark me…Reads private dataNo findings

    Why it is in this group

    • The name "get_commit_summary" says "get": a word for reading.

    What it can reach

    • private-dataThe name "get_commit_summary" says "get" and "commit": it reads repositories.
    • private-dataThe description's first sentence says "commit": it reads repositories.
    Description, as the server wrote it
    For one commit, show every target's memory change against its base build: per region, the largest section and source-file changes, budget alerts, and, for targets with benchmark metrics, each metric's change. For a pull request, pass the PR's head commit SHA: its base is the tip of the PR's base branch, so the result is the whole PR's change. Use it to review a pull request or check whether a commit grew memory or moved a benchmark.

    Annotations the server declares

    • title: Commit memory summary
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_memory_historyList a target's commits, newest first, with each memory region's used size and the change that commit made.Reads private dataNo findings

    Why it is in this group

    • The name "get_memory_history" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "commit": it reads repositories.
    Description, as the server wrote it
    List a target's commits, newest first, with each memory region's used size and the change that commit made. Use it to see how memory evolved and to find the commits that grew it (the largest positive 'delta'); page back with 'offset'.

    Annotations the server declares

    • title: Memory history
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_metric_historyList a target's benchmarked commits, newest first, with each benchmark metric's value (cycle counts, timings, scores that CI attached) and its change from the previous commit that …Reads private dataNo findings

    Why it is in this group

    • The name "get_metric_history" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "commit": it reads repositories.
    Description, as the server wrote it
    List a target's benchmarked commits, newest first, with each benchmark metric's value (cycle counts, timings, scores that CI attached) and its change from the previous commit that had the metric. Use it to see how a benchmark evolved and to find the commit that moved it; page back with 'offset'.

    Annotations the server declares

    • title: Benchmark metric history
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_projectsList the MemBrowse projects this API key's account owns or is a member of.Reads text others writeNo findings

    Why it is in this group

    • The name "list_projects" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "browse": it reads web pages, which anyone can write.
    Description, as the server wrote it
    List the MemBrowse projects this API key's account owns or is a member of. Needs an account API key. For a public project, skip this tool and call list_targets with its GitHub 'owner/repo'.

    Annotations the server declares

    • title: List projects
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_symbolsList the largest symbols in one build of a target, optionally filtered by region, section, source file, object or name, or totalled per section, library, object, file or directory …Reads private dataNo findings

    Why it is in this group

    • The name "list_symbols" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "file": it reads files.
    • private-dataThe input names a file (input.file_contains), and the tool reads: it reads files.
    Description, as the server wrote it
    List the largest symbols in one build of a target, optionally filtered by region, section, source file, object or name, or totalled per section, library, object, file or directory with 'group_by'. Use it to see what takes the space.

    Annotations the server declares

    • title: List symbols
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_targetsList a project's build targets (firmware binaries) with the current used and limit size of each memory region at the head of the default branch.Reads private dataNo findings

    Why it is in this group

    • The name "list_targets" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "branch": it reads repositories.
    Description, as the server wrote it
    List a project's build targets (firmware binaries) with the current used and limit size of each memory region at the head of the default branch.

    Annotations the server declares

    • title: List targets
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data6
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:19 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http membrowse https://api.membrowse.com/mcp
claude mcp add --transport http membrowse https://api.membrowse.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__membrowse__list_projects",
      "mcp__membrowse__list_targets",
      "mcp__membrowse__get_commit_summary",
      "mcp__membrowse__get_memory_history",
      "mcp__membrowse__get_metric_history",
      "mcp__membrowse__compare_builds",
      "mcp__membrowse__list_symbols",
      "mcp__membrowse__export_symbols"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as membrowse. Review it before you use it.

Capability tags behind 7 rules
  • mcp__membrowse__list_projects untrusted-input
  • mcp__membrowse__list_targets private-data
  • mcp__membrowse__get_commit_summary private-data
  • mcp__membrowse__get_memory_history private-data
  • mcp__membrowse__get_metric_history private-data
  • mcp__membrowse__list_symbols private-data
  • mcp__membrowse__export_symbols private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.membrowse/membrowse/verify?hash=05018efb9ce35c6f61300803deb84716c3f1f8593083bbf5cf9c093063565955" | jq -e '.changed == false'

Pinned hash 05018efb9ce3, from Nov 20, 2026, 14:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.membrowse/membrowse/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.membrowse/membrowse
[![Anlyon Radar](https://radar.anlyon.com/badge/com.membrowse/membrowse.svg)](https://radar.anlyon.com/servers/com.membrowse/membrowse)

Source: MCP Registry. Synced Nov 20, 2026, 14:17 UTC.

MemBrowse MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the MemBrowse MCP server safe?

No scan can promise that. What its definitions show: 8 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the MemBrowse MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the MemBrowse MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the MemBrowse MCP server have?

8 tools: 8 read. list_projects, list_targets, get_commit_summary, get_memory_history, get_metric_history, compare_builds, list_symbols and export_symbols.

Does the MemBrowse MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the MemBrowse MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the MemBrowse MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.