Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Aileron Journal

PYPI · AILERON · SCANNED AUG 20

Read-only queries over Aileron audit journals: verify integrity, search recorded tool calls

Available components

pypi · aileron 66
66 Trust /100
Trust breakdown (6 categories)

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 →

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 native-build step with no shell scripting around it. View diagnostics → Pass
  • 0 of 5 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 0 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

pypi · aileron

# add to Claude Code
claude mcp add aileron-sh-aileron -- uvx aileron
# add to Codex CLI
codex mcp add aileron-sh-aileron -- uvx aileron
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "aileron-sh-aileron": {
      "type": "local",
      "command": [
        "uvx",
        "aileron"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add aileron-sh-aileron --command uvx --arg aileron
# ~/.hermes/config.yaml
mcp_servers:
  aileron-sh-aileron:
    command: "uvx"
    args: ["aileron"]
// mcp.json
{
  "mcpServers": {
    "aileron-sh-aileron": {
      "command": "uvx",
      "args": [
        "aileron"
      ]
    }
  }
}
Changelog

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.

  • 20 Aug 26 66

    First indexed and scored.

Diagnostics

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 20 Aug 2026 · Analysed pypi/aileron@0.1.4

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Install scripts 1 script
Hook Tier Command
build_backend allowlisted setuptools.build_meta
Dependencies 5 packages
Packages resolved 5
Tree resolution Complete
MCP tools · 3 exposed · ~255 tokens

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.

Tool Tokens
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.

NameTypeReqDescription
rule_idstring–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.

NameTypeReqDescription
journalstringyesJournal filename, relative to the served root.
limitinteger–Maximum events to return (default 50, max 200).
sincestring–RFC3339 lower bound, inclusive.
statusstring––
tool_namestring–Exact tool name to match.
untilstring–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.

NameTypeReqDescription
journalstringyesJournal filename, relative to the served root.

No output schema declared.

No examples provided.