DataRaum vs io.github.poojaBjAcharya/cdgcsearchmetadata
DataRaum is an MCP server published by dataraum. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.poojaBjAcharya/cdgcsearchmetadata is an MCP server published by poojaBjAcharya. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-05. 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 |  DataRaum | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.1 Forks (GitHub): 0 Stars (GitHub): 3 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
| Fact | DataRaum | io.github.poojaBjAcharya/cdgcsearchmetadata |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 3 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (dataraum) | Remote server (qa-pod1-a2e-mcp.rel.infaqa.com/mcp-servers/public/cdgcsearchmetadata) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/dataraum/dataraum | github.com/example/remote-fs |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 3 days ago returned HTTP 401 |
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
DataRaum
Pre-computed metadata context engine for AI-driven data analytics
io.github.poojaBjAcharya/cdgcsearchmetadata
Provides metadata information to AI agents through the search API.
How to run each
DataRaum As a local MCP server: PyPI package
claude mcp add --env "ANTHROPIC_API_KEY=<YOUR_ANTHROPIC_API_KEY>" --transport stdio dataraum -- uvx dataraumRequires: ANTHROPIC_API_KEY (secret)
io.github.poojaBjAcharya/cdgcsearchmetadata As a remote MCP server
claude mcp add --transport http cdgcsearchmetadata https://qa-pod1-a2e-mcp.rel.infaqa.com/mcp-servers/public/cdgcsearchmetadata --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 io.github.poojaBjAcharya/cdgcsearchmetadata 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
The marketplaces of io.github.poojaBjAcharya/cdgcsearchmetadata publish no settings it asks for, so we do not compare settings.
What it can do: DataRaum · What it can do: io.github.poojaBjAcharya/cdgcsearchmetadata · 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.