io.github.AntonG87/codearia-sieve
NPM · CODEARIA-SIEVE
Web pages into decision-ready state: dates, numbers with units, budgeted chunks. No model, no key.
Available components
Last scanned (15 hours ago)
Scores higher than 96% of npm servers
Category Documents and Files
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 34 of 122 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to AntonG87/codearia-sieve). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 60 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 246 tokens (~123/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 89% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Nov 26 +1
- Stability: 0.97 → pass security
- 20 Nov 26 −1
- Stability: pass → 0.93 functional
- 14 Nov 26 +1
- Stability: 0.97 → pass security
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 −5
- Stability: pass → 0.67 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Nov 2026 · Analysed npm/codearia-sieve@0.2.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | AntonG87/codearia-sieve |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/AntonG87/codearia-sieve/.github/workflows/publish.yml@refs/tags/v0.2.2 |
| Rekor log index | 2908841813 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:a3d32e0ba70fc3be07fb4a7fb71c529de5fac62578e73b8d95ef76d1625e219626434be9d5803640e8f21104f9e8d2f75cfd312f3eadaa7bcb34236cd |
Background: How many MCP packages publish verified provenance →
Dependencies 122 packages
| Packages resolved | 122 |
|---|---|
| Stale | 34 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
sieve_chunk Read one chunk ~46
Returns the text of a chunk from a page prepared earlier with sieve_page (same url).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Chunk id such as c3. |
| url | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| anchor | string | – | – |
| id | string | yes | – |
| text | string | yes | – |
| tokens | number | yes | – |
No examples provided.
sieve_page Prepare a page for decisions ~200
Turns a web page into decision-ready state: dates as ISO fields, numbers with units as facts, text in token-budgeted chunks with anchors back to the page, and the token bill (raw vs state). Start with mode=summary; fetch chunk text with sieve_chunk or mode=full only when needed.
| Name | Type | Req | Description |
|---|---|---|---|
| html | string | – | Raw HTML to process instead of fetching. Pair with url for anchors. |
| maxChars | integer | – | Chunk budget in characters. |
| maxTokens | integer | – | Chunk budget in tokens. |
| mode | string | – | summary: state without chunk text (cheap, default). full: with chunk text. markdown: readable text instead of state. |
| task | string | – | What you intend to decide; enables relevance selection when a selector is configured. |
| trace | boolean | – | Include what was discarded and where the date came from. |
| url | string | – | Page to fetch. Either url or html is required. |
| Name | Type | Req | Description |
|---|---|---|---|
| markdown | string | – | – |
| source | object | yes | – |
| state | object | yes | – |
| trace | object | – | – |
| usage | object | yes | – |
| warnings | array | yes | – |
No examples provided.
How do I install the io.github.AntonG87/codearia-sieve MCP server?
io.github.AntonG87/codearia-sieve runs locally as an npm package, launched with npx -y codearia-sieve. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · codearia-sieve
claude mcp add antong87-codearia-sieve -- npx -y codearia-sieve
What is the io.github.AntonG87/codearia-sieve MCP server?
io.github.AntonG87/codearia-sieve is an MCP server listed in the public MCP registry as io.github.AntonG87/codearia-sieve. Web pages into decision-ready state: dates, numbers with units, budgeted chunks. No model, no key. This page covers its npm package (codearia-sieve).
Is the io.github.AntonG87/codearia-sieve MCP server safe to use?
io.github.AntonG87/codearia-sieve scores 94 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.AntonG87/codearia-sieve MCP server expose?
io.github.AntonG87/codearia-sieve exposes 2 tools: sieve_page, sieve_chunk. Their descriptions and schemas cost roughly 246 tokens of context every time the server is loaded.
Is the io.github.AntonG87/codearia-sieve MCP server still maintained?
io.github.AntonG87/codearia-sieve is still listed as active in the MCP registry. We last reached this channel on 22 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.AntonG87/codearia-sieve MCP server under?
io.github.AntonG87/codearia-sieve declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.AntonG87/codearia-sieve MCP server?
VerifyMCP ran 16 checks on io.github.AntonG87/codearia-sieve, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.