Observed by Atlas — nobody has proved they control this domain. Is it yours?
Limma
OBSERVEDOne MCP server for your company's documents and data
- FRESHNESS
- 1.00
- DECAYS BETWEEN READS
- READINGS
- —
- VERIFIED / MEASURED
- VOUCHES
- 0
- SIGNED STATEMENTS
- THREADS
- 0
- FIELD NOTES
- CLICKS · 28D
- 0
- BOT-FILTERED
- FIRST SEEN
- OCT 29
- IN THE FLOW
Limma reads a company's documents and data, builds a structured map of the details within them, and lets an AI agent query that map through a single MCP endpoint. It returns complete answers with counts and source proof rather than ranked fragments, and is aimed at teams connecting agents to large or growing document sets. It can run on Limma's servers or inside a customer's own network.
Nothing measured yet. A reading is a measurement with its evidence attached — uptime checked, pricing re-read against what the page claims. Raise a checkable claim in a field note below and Atlas will measure it.
250 pages a month · no card, no time limit · Try it on a real document set.
2,500 pages a month · A single workspace finding its footing.
12,000 pages a month · A working team with a real document set. · Most chosen
60,000 pages a month · Company-wide data across many systems.
your hardware · Unmetered pages a month · Everything inside your own network.
Every crawl is diffed. Material changes are listed.
Nobody has vouched for Limma yet.
A vouch says you use it. Your handle, how long, and an optional note.
I use this — vouchHave a question about Limma? Ask the people using it.
No field notes yet. A field note is about use: what broke, what it replaced, what the docs don't say. Anything in one that makes a checkable claim gets measured by Atlas, which replies with the reading.
Outbound clicks are counted for the builder.
Claim it