Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search
Nothing to run from here
Axiom Foundation 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.
100/100
trust score
7
downloads a day
local
runs on your machine
92
downloads in 30d
What it does
MCP server adapter for the Axiom Rule API.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user axiom-foundation-mcp '--' npx -y @axiom-foundation/mcp
# 2 — ask your agent for something these tools do
# get_capabilities, get_version, list_certified_nodes and 20 more
Axiom Foundation costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
THAll 1 server
theaxiomfoundation1 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 Axiom Foundation 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 axiom-foundation-mcp '--' npx -y @axiom-foundation/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.
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
23 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 API version, environment, endpoints, repository status, runtime packages, and sample calculation requests.
No parameter schema on file.
Read the API version, environment, and deployment identity.
No parameter schema on file.
Page through the certified node ledger: every rule node the deployment certifies as servable.
No parameter schema on file.
Read one certified rule node by legal id, with its certificate and ledger metadata.
No parameter schema on file.
List every rulespec subtree in the live corpus mirror that can be executed on demand via calculate_household with
No parameter schema on file.
Build the dependency graph for any encoded rule or file legal id by walking RuleSpec imports across the live corpus mirror.
No parameter schema on file.
Read the certified closure from up to 20 root node legal ids, in program-graph shape.
No parameter schema on file.
Read the typed input catalog for any rulespec root (file legal id, optionally with #rule) before calling calculate_household with
No parameter schema on file.
List every compiled artifact this deployment pins: release tag, corpus sha, and file sha256, for pinning and replay.
No parameter schema on file.
List programs discoverable in the configured Axiom rule index, including those without an executable runtime package.
No parameter schema on file.
Search encoded and source-linked rules. Use jurisdiction/program filters when the user names a location or benefit program.
No parameter schema on file.
Read one rule by stable rule id or citation path, including summary, symbols, provenance, dependencies, and dependents.
No parameter schema on file.
Read source and provenance references for one rule.
No parameter schema on file.
Read upstream dependencies and downstream dependents for one rule.
No parameter schema on file.
List programs executable by the configured Axiom calculation runtime.
No parameter schema on file.
Read executable package inputs, outputs, aliases, and sample request for a program.
No parameter schema on file.
List canonical Axiom runtime parity cases, expected outputs, trace variables, notes, external comparison metadata, and calculation requests.
No parameter schema on file.
Run canonical Axiom runtime parity cases and return variable-level differences, trace outputs, and calculation trace.
No parameter schema on file.
Run a calculation. Address a registered package with program_id + jurisdiction (discover inputs with get_runtime_package), or run any corpus subtree on demand with root (discover inputs with get_root_inputs). The two modes are mutually exclusive.
No parameter schema on file.
PolicyEngine household-API compatible calculation: accepts the PE v1 household body for a country_id and mirrors PE
No parameter schema on file.
Run up to 25 calculations in one synchronous request. Results return positionally: results[i] corresponds to requests[i], each independently ok or error.
No parameter schema on file.
Submit up to 50 calculations as a detached async job. Returns a job id to poll with get_calculation_job; results are retained for 24 hours and visible only to the submitting API key.
No parameter schema on file.
Read the status, progress, and results of a calculation job submitted with submit_calculation_job.
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 Axiom Foundation 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 100 / 100
Release 0.2.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 score100
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationsource
Surface digestd6c32d39993176e432d71319414428bba9c4fe55227a5b63e7e9aae42cea1ac0
Score vectorthreat 100 → client 100
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| 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 (23 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. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_capabilities | no tags | |
| get_version | no tags | |
| list_certified_nodes | no tags | |
| get_node | no tags | |
| list_corpus_subtrees | no tags | |
| compose_graph | no tags | |
| get_subgraph | no tags | |
| get_root_inputs | no tags | |
| list_runtime_artifacts | no tags | |
| list_programs | no tags | |
| search_rules | no tags | |
| get_rule | no tags | |
| get_rule_sources | no tags | |
| get_rule_dependencies | no tags | |
| list_runtime_packages | no tags | |
| get_runtime_package | no tags | |
| list_parity_cases | no tags | |
| run_parity_cases | no tags | |
| calculate_household | no tags | |
| calculate_household_compat | no tags | |
| calculate_batch | no tags | |
| submit_calculation_job | no tags | |
| get_calculation_job | 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 digestd6c32d39993176e4
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.2.0. Pin a release below and the command asks for exactly that one.
0.2.0
undated
latestNo release note was published with this version.
—
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 Axiom Foundation 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.