Web pages into decision-ready state: dates, numbers with units, budgeted chunks. No model, no key.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
One-click editor setup isnβt available for this listing yet β we donβt have a confirmed install command, and weβd rather show nothing than point your editor at the wrong package or host. Follow the projectβs own setup instructions, linked above.
Parses a web page into the exact format a decision model needs.
Dates as dates. Numbers with units. Text in chunks that fit the model's window, each pointing back to where it came from.
One call β and the token bill, before and after.
Measured, not promised. A live run over random pages picked the same day β fresh news from RSS feeds in several languages, random Wikipedia articles, docs, blogs, government sites, recipes, shops. Every row is in bench/analytics/, and npm run analytics reruns the whole thing. The output was then put in front of a decision model: see Checked by a judge.
An agent that needs a web page fetches the whole thing: navigation, cookie banner, footer, ad slots, a megabyte of framework markup. Then a model paid per token digs through the pile for one paragraph.
codearia-sieve does the digging before the model sees anything β and returns the page as state, not prose:
|
Dates become dates
|
Numbers become facts
|
Text becomes chunks that fit Each chunk knows its size in tokens and characters, the blocks it was built from, and the |
Everything else β menus, footers, banners, tag rows, "read more" β is removed, and with trace: true you get the list of what was removed and why.
People who build agents and have seen the bill. Every fetched page costs tens of thousands of tokens before the agent has read a word of it. Median page in the sample: 53 718 tokens in, 1 106 out.
People who run cheap decision models. Classifiers, rankers, System One models like Jev that judge instead of write. They are nearly free and very fast, and they have hard edges: they cannot count, they read dates as text, and their accuracy drops as irrelevant material fills the context. Every "page to markdown" tool prepares input for a reader. This one prepares input for a judge.
People who need answers they can check. A verdict from scraped text is unprovable unless each piece points back to its source. Here every fact names its block and every chunk carries an anchor.
Eight steps of ordinary code. No model runs unless you plug one in. The same HTML gives the same JSON, byte for byte.
robots.txt first; a refusal is reported, not bypassed. Plain HTTP, honest user agent.linkedom. No browser.<head>, bylines and attributes, so both are read before it runs.<span>20 Sept</span><span>10 min</span> never becomes 202610 min.<br><br> become paragraphs too; table rows keep their column headers.state, markdown, usage, warnings, and the trace on request.Expected outcomes never throw. They come back as warnings, each named:
| Warning | Meaning |
|---|---|
robots-disallowed | the site asks crawlers to stay out; we did not fetch |
blocked | a bot challenge or a refusal (403, 405, 429, "Just a momentβ¦"), with the status |
http-error | a 404 or a 500 that still rendered an error page; not the page you asked for |
paywall | the page marks its article as not free; you got the teaser |
empty-without-js | the article container is empty and a script would fill it |
thin-content | a big page that yielded little prose β a front page, a listing |
block-split | one block exceeded the budget and was cut on sentence boundaries |
facts-capped | the page has more facts than the 500 listed β a long fee schedule, say |
You say what you want in plain words. The agent finds the pages, calls sieve_page for each, hands the state to a decision model with a typed question, and writes up the result. Sieve prepares. The judge judges. The agent writes.
Listed in the official MCP Registry as io.github.AntonG87/codearia-sieve; clients that read the registry can install it by name.
|
Returns typed |
The text of one chunk from the last result for that URL, no refetch. Overview first, then only what is needed β the tool applies its own idea to itself. |
Pairs with jev-mcp: chunks are sized to fit its fields, so state goes straight into a typed question.
The claim is that a decision model gets better input from Sieve than from raw text. So the output was handed to one. examples/jev.ts drives both MCP servers with the official client β codearia-sieve prepares six pages (API docs, a release note, two Wikipedia articles in two languages, two pricing pages), Jev judges them through jev-mcp. Same run, 21 September 2026:
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/codearia-sieve)<a href="https://allmcps.com/mcp/codearia-sieve"><img src="https://allmcps.com/api/badge/codearia-sieve?style=directory" alt="Codearia Sieve on AllMCPs" /></a>