MCP.Market

Omneum MCP server

by cole-h06·io.github.cole-h06/omneum·v1.0.9

Text-blind context control plane for AI agents. Select high-utility context under token budgets.

B83/100grade B
What users say
No reviews yet
Be the first
Safety scan
B83/100

not scanned yet

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Omneum yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Omneum tools

No tool declarations could be read from the package source. They show once the server is installed.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Omneum compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
83/100
higher than 65% of 48,255 servers

Release history: 3 versions in the registry since 2026-10-13, latest 2026-10-26, typically one every 10 days.

Install Omneum in Claude Code, Cursor or VS Code

The registry entry has no remote endpoint or installable package.

What the publisher says

From the Omneum repository's README, as published. We do not edit it. Read it on GitHub

What is Omneum

An open-source context evaluator for AI agents.

Agents routinely assemble context from many different sources — a RAG pipeline, web search, APIs, databases, files, memory systems, other agents — but stuffing dozens of raw chunks into a single context window can leave the model working through a mess of information that was never organized for it.

Most agents focus on retrieving more context. Omneum is focused on making sure the context reaching the model is clean and reliable.

Why Omneum and how it works

Modern agent pipelines use several different techniques to decide what context should reach a model:

Semantic similarity (Vector DBs). The piece of text that looks closest to the prompt wins.

Semantic reranking. Retrieved context is reordered based on how relevant it is to the query.

LLM-as-a-Judge. An LLM reads the retrieved context and is instructed to evaluate it against a set of instructions.

These techniques can be highly effective at selecting context, but relevance is only one dimension of context quality.

Chunks can still hold conflicting or stale information. Multiple retrieved chunks might not be deduplicated or appear independent despite sharing an upstream source. This contributes to context bloat: low-quality information consumes context-window capacity that could otherwise be used for higher quality information.

Omneum addresses many of these limitations: it uses a graph-based mathematical analysis to model the relationships between claims and their supporting sources. Importantly, this analysis does not naively assume every source has derived its information independently. The same information often propagates across multiple sources. Without dependency tracking, an agent cannot distinguish five independent observations from the same information repeated five times.

Agent pipelines already handle structured metadata alongside retrieved context. Omneum uses available provenance and lineage metadata to estimate source dependencies, then incorporates those estimates into its calculation of source reliability and claim support scores.

These scores are computed without interpreting the semantic meaning of the context. For instance, when considering a claim such as:

“Acme reported $4.2 billion in revenue in 2025.”

Its support score depends on the reliability of the sources supporting it. In turn, those sources receive reliability from the claims they support.

This definition seems circular, and it is. Nonetheless, it yields a well-defined notion of reliability that helps distinguish strongly supported context from weakly supported context.

Omneum uses BRAID, its open-source algorithm, to compute these reliability and support scores. Explore the algorithm and research →

Where Omneum fits

Omneum runs locally as a Model Context Protocol (MCP) server. It adds a lightweight post-retrieval evaluation layer to your existing retrieval or ranking stack; no inference request, no extra model call.

Retrieval / tools → Reranking (optional) → Omneum evaluation → agent control flow → LLM

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Omneum: common questions

Is Omneum MCP server safe?
Mostly: it is graded B (83/100). Read the Omneum safety report
Does Omneum need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Omneum maintained?
The last commit was 22 days ago (2026-10-13). The latest release is v1.0.9.