Aileron Journal
PYPI · AILERON
Read-only queries over Aileron audit journals: verify integrity, search recorded tool calls
Available components
Last scanned (3 hours ago)
Scores higher than 95% of PyPI servers
Category Security
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
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 5 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to aileron-sh/aileron). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 52 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 255 tokens (~85/item across 3 items; 3 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 Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 88% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 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
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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.
- 17 Oct 26 +2
- Stability: 0.80 → pass security
- 16 Oct 26 −2
- Stability: pass → 0.80 functional
- 15 Oct 26 0
- Stability: 0.97 → pass security
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 26 −2
- Stability: pass → 0.80 functional
- 1 Oct 26 0
- Stability: 0.97 → pass security
- 30 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
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 17 Oct 2026 · Analysed pypi/aileron@0.1.5
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 | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | aileron-sh/aileron |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/aileron-sh/aileron/.github/workflows/release.yml@refs/tags/v0.1.5 |
| Rekor log index | 2582502138 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:fd4d78b9881d2354f67051addf5956ebfd23b7bfb94d8d6013aa611fdb6b8994 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 5 packages
| Packages resolved | 5 |
|---|---|
| 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 →
explain_rule ~55
Describe the bundled detection rules: what each one matches, its severity, and whether it blocks or only alerts. Omit rule_id to list all of them.
| Name | Type | Req | Description |
|---|---|---|---|
| rule_id | string | – | For example aileron-130. |
No output schema declared.
No examples provided.
query_events ~137
Search a journal for recorded tool calls. Filter by tool name, status (ok, error, blocked), or a time range. Returns the matching events. Tool arguments appear as digests unless the journal was recorded with content capture enabled.
| Name | Type | Req | Description |
|---|---|---|---|
| journal | string | yes | Journal filename, relative to the served root. |
| limit | integer | – | Maximum events to return (default 50, max 200). |
| since | string | – | RFC3339 lower bound, inclusive. |
| status | string | – | – |
| tool_name | string | – | Exact tool name to match. |
| until | string | – | RFC3339 upper bound, inclusive. |
No output schema declared.
No examples provided.
verify_journal ~63
Check whether an Aileron journal is intact. Returns whether the hash chain verifies, how many events it holds, and the sequence number of the first bad event if it was tampered with.
| Name | Type | Req | Description |
|---|---|---|---|
| journal | string | yes | Journal filename, relative to the served root. |
No output schema declared.
No examples provided.
How do I install the Aileron Journal MCP server?
Aileron Journal runs locally as a PyPI package, launched with uvx aileron. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · aileron
claude mcp add aileron-sh-aileron -- uvx aileron
What is the Aileron Journal MCP server?
Aileron Journal is an MCP server listed in the public MCP registry as io.github.aileron-sh/aileron. Read-only queries over Aileron audit journals: verify integrity, search recorded tool calls. This page covers its PyPI package (aileron).
Is the Aileron Journal MCP server safe to use?
Aileron Journal scores 92 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 2026. 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 Aileron Journal MCP server expose?
Aileron Journal exposes 3 tools: verify_journal, query_events, explain_rule. Their descriptions and schemas cost roughly 255 tokens of context every time the server is loaded.
Is the Aileron Journal MCP server still maintained?
Aileron Journal is still listed as active in the MCP registry. We last reached this channel on 17 October 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 Aileron Journal MCP server under?
Aileron Journal declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.