Ext Ops Panel
Open dashboard
Comparison

Lumin vs Foam Observability

Lumin is an MCP server published by getlumin.dev. Marketplaces we read that list it: 1 (Official MCP Registry). 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-10-17. 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

Where each is published
MarketplaceLuminFoam Observability
Official MCP Registry Listed
Version: 0.1.0
No figure published
Not marked · First seen
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

Lumin vs Foam Observability
FactLuminFoam Observability
Marketplaces that list it11
Last releaseNot publishedNot published
Where it runs (differs)Remote server (api.getlumin.dev/v1/mcp)Remote server (sdk.api.foam.ai/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
RepositoryNot statedNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 3 days ago, requires a keyNot responding since 2026-10-12

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

Lumin

In its own words, on Official MCP Registry:

Read-only access to a Lumin project's logs, metrics, uptime checks, alerts and infrastructure.

Foam Observability

In its own words, on Official MCP Registry:

Query application logs, traces, and metrics from your AI coding assistant via Foam's MCP server.

How to run each

Lumin As a remote MCP server

Claude Code
claude mcp add --transport http lumin https://api.getlumin.dev/v1/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

Foam Observability As a remote MCP server

Claude Code
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 the endpoint of Lumin responded at the last daily 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: Lumin · What it can do: Foam Observability · Compare two other plugins

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.

Where the data comes from: how the catalog is built