microscope vs Foam Observability
microscope is a plugin bundle for AI coding tools published by Petr Bouda. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Foam Observability is an MCP server published by foam-ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Foam Observability | |
|---|---|---|
| Community marketplace petrbouda/jeffrey | Listed Version: 1.0.32 Forks (GitHub): 7 Stars (GitHub): 81 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | microscope | Foam Observability |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 81 | No figure on GitHub |
| Forks (GitHub) (differs) | 7 | No figure on GitHub |
| Last release (differs) | 2026-11-06 | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (sdk.api.foam.ai/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 1 | Not published |
| Parts of the bundle (differs) | 17 | Not a bundle |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/petrbouda/jeffrey | Not stated |
| Changes in the last 7 days (differs) | 5 | 0 |
| First seen (differs) | 2026-11-01 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: no HTTP response at the last check 47 h ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
microscope
Analyze JVM recordings with a running Jeffrey Microscope — point it at a JFR file or heap dump to build a profile, then list analysed recordings, query their DuckDB tables, and pull flamegraph, trace and heap-dump exports without leaving the terminal.
Foam Observability
Query application logs, traces, and metrics from your AI coding assistant via Foam's MCP server.
How to run each
microscope As a Claude Code plugin
/plugin marketplace add petrbouda/jeffrey
/plugin install microscope@jeffreyFoam Observability As a remote MCP server
claude mcp add --transport http observability https://sdk.api.foam.ai/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Foam Observability has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: microscope · What it can do: Foam Observability · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.