Illinois Code
NPM · @PIPEWORX/MCP-ILLINOIS-CODE · 2 COMPONENTS
Illinois Compiled Statutes — state statutes by citation, plus topic search.
Available components
Last scanned (16 hours ago)
Scores higher than 72% of npm servers
Category Education and Research
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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-illinois-code). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability61
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 616 tokens (~308/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.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 3 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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +27
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → pass ▲ functional
- 2 Nov 26 −24
- Known CVEs: pass → unverified ▼ security
- Malware scan: pass → unverified ▼ security
- Dependency health: pass → unverified ▼ functional
- Stability: unverified → 0.13 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 78
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-illinois-code@0.2.1
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 | pipeworx-io/mcp-illinois-code |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-illinois-code/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3637415422 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:ebcc0ddef55ef703c154ee3e8c4619c2ec06e501bd0f2958900a514bc35fc4b631885e4bf0480e6c951a1e7ce62deac7a26afd074eca7725e1b35b24b |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
il_compiled_statute ~279
Get the FULL TEXT of a section of the Illinois Compiled Statutes — Illinois state law — by citation. "720 ILCS 5/9-1" is first degree murder; "625 ILCS 5/11-501" is DUI. Pass the full citation as `citation` ("225 ILCS 155/30") or split it into `chapter`/`act`/`section`. Returns the statutory text with a data_as_of timestamp. Keyless. Use for "what does 720 ILCS 5/9-1 say" or to check an Illinois statute a case relies on.
| Name | Type | Req | Description |
|---|---|---|---|
| act | string | – | Act number within the chapter — the part after ILCS and before the slash, e.g. "5". Omit if passing `citation`. |
| chapter | string | – | ILCS chapter, e.g. "720" (criminal offenses), "625" (vehicles), "750" (families). Omit if passing `citation`. |
| citation | string | – | The full citation in one string, e.g. "225 ILCS 155/30". Alternative to chapter/act/section — either works. |
| section | string | – | Section as cited, e.g. "9-1" or "11-501". Omit if passing `citation`. |
No output schema declared.
No examples provided.
il_statute_search ~282
Search Illinois Compiled Statutes BY TOPIC or keyword rather than citation — "currency exchange license fee", "concealed carry reciprocity", "landlord retaliation". Returns ranked sections with their citations; use il_compiled_statute afterward for the full text of one. Pass `chapter` + `act` (e.g. "225" + "155" for 225 ILCS 155) to scope the search to one act's own sections instead of ranking across all ~72,000 — use this when you already know which act the answer is in, so a term that is common across many acts still finds the right section. Full-text search, so it answers questions no citation lookup can. Keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| act | string | – | Optional: act number within `chapter` to scope the search, e.g. "155" for 225 ILCS 155. Only that act's sections are searched. |
| chapter | string | – | Optional: ILCS chapter to scope the search to one act (pair with `act`), e.g. "225". |
| limit | number | – | Max results, default 10, max 25. |
| query | string | yes | Topic or keywords, e.g. "currency exchange license fee". Can also name an act directly, e.g. "225 ILCS 155 civil penalty". |
No output schema declared.
No examples provided.
How do I install the Illinois Code MCP server?
Illinois Code runs locally as an npm package, launched with npx -y @pipeworx/mcp-illinois-code. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-illinois-code
claude mcp add pipeworx-io-illinois-code -- npx -y @pipeworx/mcp-illinois-code
What is the Illinois Code MCP server?
Illinois Code is an MCP server listed in the public MCP registry as io.github.pipeworx-io/illinois-code. Illinois Compiled Statutes, state statutes by citation, plus topic search. This page covers its npm package (@pipeworx/mcp-illinois-code).
Is the Illinois Code MCP server safe to use?
Illinois Code scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 Illinois Code MCP server expose?
Illinois Code exposes 2 tools: il_compiled_statute, il_statute_search. Their descriptions and schemas cost roughly 561 tokens of context every time the server is loaded.
Is the Illinois Code MCP server still maintained?
Illinois Code is still listed as active in the MCP registry. We last reached this channel on 5 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 Illinois Code MCP server under?
Illinois Code 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 Illinois Code MCP server?
VerifyMCP ran 16 checks on Illinois Code, 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.