Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search
Nothing to run from here
Aethis is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
97/100
trust score
12
downloads a day
local
runs on your machine
893
downloads in 30d
What it does
Deterministic eligibility decisions and test-driven rule authoring via the Aethis developer API.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user aethis-mcp '--' npx -y aethis-mcp
# 2 — ask your agent for something these tools do
# aethis_schema, aethis_decide, aethis_next_question and 32 more
Aethis costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
AAAll 1 server
Aethis-ai1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Aethis as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user aethis-mcp '--' npx -y aethis-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add — some of its tools take a key of its publisher’s own, and the rest work without.
What it asks of you
Nothing is required, but it can take AETHIS_API_KEY (API key for rule authoring tools (create/generate/publish). Decision tools (decide/schema/explain on public rulesets) work without a key. Get one via 'aethis login' in aethis-cli.), AETHIS_BASE_URL (API base URL. Defaults to https://api.aethis.ai — override for self-hosted or staging.) if you want to set them. Its publisher says some of its tools need one of them, and the rest work without.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
35 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Get the input fields required for an eligibility check. Returns field names, types, descriptions, and allowed values. Use this before calling aethis_decide.
No parameter schema on file.
Evaluate eligibility against either a single published ruleset (ruleset_id) or a composed rulebook (rulebook_id). Provide exactly one. A rulebook composes multiple rulesets via outcome_logic — use it for the whole-form decision (e.g.
No parameter schema on file.
No parameter schema on file.
Get the ruleset-map graph for a single published ruleset (ruleset_id) or a composed rulebook (rulebook_id) — provide exactly one. Returns {ruleset_id|rulebook_id, slug, name, graph: {nodes, edges, sections, stats}, mermaid}: each node
No parameter schema on file.
Get human-readable descriptions of the rules in a ruleset, including criteria groups, requirements, and exception paths.
No parameter schema on file.
Diagnose why a ruleset produced an unexpected outcome for specific test inputs. Use during rule authoring when a test fails — returns the diagnosis, criteria with DSL metadata (waivable, review_required), and a targeted hint for fixing the rule.
No parameter schema on file.
List all projects in the current tenant. Returns project IDs, names, domains, and latest ruleset information.
No parameter schema on file.
List all rule rulesets for a project, including version history. Shows ruleset ID, human-readable name (the section title the ruleset covers, e.g.
No parameter schema on file.
Check the current generation job for a project without changing it. Returns generation_contract_version, telemetry_availability, server-authoritative worker_lifecycle, retry_readiness, and the active or most recent job
No parameter schema on file.
No parameter schema on file.
List public showcase rulesets across all tenants. No authentication required. Use this for first-time discovery, demos, or whenever the user asks
No parameter schema on file.
List rulebooks (composed wholes that bridge multiple rulesets) in the current tenant. Returns rulebook_id, slug (e.g.
No parameter schema on file.
Show the caller
No parameter schema on file.
Get the composition + aggregated input fields for a rulebook. Returns the outcome_logic Expr AST (how the bridged rulesets compose, e.g.
No parameter schema on file.
Create a new Rulebook — the composed-whole execution unit that bridges multiple rulesets (the parts) via outcome_logic. Created empty: no rulesets, no field vocabulary, no tests, status=
No parameter schema on file.
Update a Rulebook
No parameter schema on file.
Archive a project. Archived projects are preserved but excluded from listing. This is permanent.
No parameter schema on file.
Archive a rule ruleset. Archived rulesets are preserved but excluded from /decide resolution. This is permanent.
No parameter schema on file.
Create a new rule ruleset with source text and test cases (TDD). Test cases are required. After creation, call aethis_generate_and_test.
No parameter schema on file.
List all guidance hints accumulated for a project. Shows the text, source, and active status of each hint. Use before adding new guidance to avoid duplicates.
No parameter schema on file.
Add a guidance hint to a project. Use for domain knowledge not in the source text. Then call aethis_generate_and_test to regenerate.
No parameter schema on file.
Add a guidance hint at domain level — applies to ALL projects in the domain, not just one project.
No parameter schema on file.
List all active guidance hints for a domain. Returns cross-section hints that apply to all projects in the domain.
No parameter schema on file.
Discover the logical sections of source legislation for a domain.
No parameter schema on file.
Add guidance to improve section discovery, then re-discover sections.
No parameter schema on file.
Compare discovered sections against an expected specification.
No parameter schema on file.
Discover input fields from the project
No parameter schema on file.
Add guidance to improve field discovery, then re-discover. Use when fields are missing, misnamed, or enum values are incomplete. Adds a field_extraction guidance hint and re-runs discovery.
No parameter schema on file.
Assert that the discovered fields match an expected field specification.
No parameter schema on file.
Store the expected field specification for a project.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
Publish the latest rule ruleset. Runs tests first and refuses if they fail unless force=true. Auto-deprecates previous active ruleset.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Aethis or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 97 / 100
Release 0.22.0 · scanned 14 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score97
Findings1 threat · 0 capability
Capabilitymoderate
Coveragesource
Verificationsource
Surface digesta51d7dc776e24ee7e0d6cf9f5d6b4914d990d9ab40142bf1b953c4d9547eb0da
Score vectorthreat 100 → client 97
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (35 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| aethis_schema | no tags | |
| aethis_decide | no tags | |
| aethis_next_question | no tags | |
| aethis_graph | no tags | |
| aethis_explain | no tags | |
| aethis_explain_failure | no tags | |
| aethis_list_projects | no tags | |
| aethis_list_rulesets | no tags | |
| aethis_generation_status | no tags | |
| aethis_cancel_generation | no tags | |
| aethis_discover_rulesets | no tags | |
| aethis_list_rulebooks | no tags | |
| aethis_usage | no tags | |
| aethis_rulebook_schema | no tags | |
| aethis_create_rulebook | no tags | |
| aethis_update_rulebook | no tags | |
| aethis_archive_project | no tags | |
| aethis_archive_ruleset | no tags | |
| aethis_create_ruleset | no tags | |
| aethis_set_tests | no tags | |
| aethis_list_guidance | no tags | |
| aethis_add_guidance | no tags | |
| aethis_add_domain_guidance | no tags | |
| aethis_list_domain_guidance | no tags | |
| aethis_discover_sections | no tags | |
| aethis_refine_sections | no tags | |
| aethis_validate_sections | no tags | |
| aethis_discover_fields | no tags | |
| aethis_refine_fields | no tags | |
| aethis_validate_fields | no tags | |
| aethis_set_field_spec | no tags | |
| aethis_generate_and_test | no tags | |
| aethis_refine | no tags | |
| aethis_publish | no tags | |
| aethis_review_project | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digesta51d7dc776e24ee7
Scanned2026-10-14
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.22.0. Pin a release below and the command asks for exactly that one.
0.22.0
30 Sep 2026
latestNo release note was published with this version.
0.20.0
25 Sep 2026
No release note was published with this version.
0.18.0
14 Sep 2026
No release note was published with this version.
0.17.4
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Aethis can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.