Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search
Nothing to run from here
Exeris AI Bridge 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.
94/100
trust score
17
downloads a day
local
runs on your machine
113
downloads in 30d
What it does
Read-only Exeris context for AI agents: ADRs, SDK contract, build output, kernel diagnostics.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user exeris-ai-bridge-mcp '--' npx -y @exeris/ai-bridge
# 2 — ask your agent for something these tools do
# build-list_domains, build-get_domain_metadata, build-explain_artefacts and 20 more
Exeris AI Bridge costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
ESAll 1 server
exeris-systems1 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 Exeris AI Bridge 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 exeris-ai-bridge-mcp '--' npx -y @exeris/ai-bridgeReconnect, 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 asks of you
Nothing is required, but it can take EXERIS_PROJECT_ROOT (Root of your own project, for build-* and caps-*. Defaults to the nearest pom.xml at or above the working directory.), EXERIS_DOCS_ROOT (An exeris-docs checkout. Without one, docs-* answers from the registry snapshot bundled in the package.) if you want to set them.
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 from its source code. A server that builds its tool list when it starts can list more tools than this.
List what this project's last build emitted into target/classes/exeris-metadata: every @ExerisDomain entity, plus the enums, capabilities and views the processor wrote alongside them, each with its kind. Use it to discover names before calling build-get_domain_metadata. A project that has not been…
No parameter schema on file.
Fetch the DomainMetadata JSON the annotation processor emitted for one declaration of this project — the authoritative AST the code generators consume, including fields, actions, events, relationships and the system-field flags. name is the Java simple name (e.g. 'Station'), as listed by…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Java simple name of the entity, enum, capability or view. |
| kind | string | no | Which kind of declaration to read. Defaults to 'domain'. |
List the files Exeris codegen has generated into this project, each with the generator that produced it and when that generator emits — handlers, services, repositories, domain errors, event publishers, graph projections, sagas, Flyway migrations, OpenAPI specs, and the project-wide bootstrap. Ask…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity | string | no | Optional Java simple name (e.g. 'Station'). Narrows to the artefacts whose filename carries that name; project-wide artefacts are always included. |
Report whether this project's generated code is still pipeline-owned (L1, src/main/generated/java — regenerated on every build, so edits are lost) or has been detached into the developer's own sources (L2, src/main/java — owned, safe to edit). Ask this before editing anything under a generated…
No parameter schema on file.
Decode an error, warning or note exeris-tooling printed — an annotation-processor message, a codegen plugin goal failure or warning, a capability-graph or cap-tier Wall refusal, a missing runtime driver, a code-generation pipeline or CodegenMain line, or an exeris-initializr error. Paste the…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | The diagnostic, pasted verbatim. A whole build log is fine — every recognised diagnostic in it is returned. |
List what this project's last build emitted into target/classes/exeris-metadata: every @ExerisDomain entity, plus the enums, capabilities and views the processor wrote alongside them, each with its kind. Use it to discover names before calling build-get_domain_metadata. A project that has not been…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Java simple name of the entity, enum, capability or view. |
| kind | string | no | Which kind of declaration to read. Defaults to 'domain'. |
Identify this MCP server: package name and version, the Node runtime it is running on, which persona mode it resolved to, and what bundled reference data it carries. Use it to confirm which bridge build an answer came from, and which upstream release that data reflects.
No parameter schema on file.
Report which tool families can serve requests and why the others cannot. Each family carries its state and, when unavailable, the reason and the remedy. Families backed by a child process also report that process's current state — without starting it. Call this first when a tool returns…
No parameter schema on file.
List the capability modules composed into this project, from the build-time cap-manifest.json: each module's qualified name, the services it provides with their versions, and which module owns the lifecycle. Also returns initOrder exactly as the manifest states it. A project with no capabilities…
No parameter schema on file.
Report the composition stamp from cap-manifest.json: whether the capability graph validated, the composition version, and the content binding digest, alongside the manifest schema version, the module count and initOrder. Answers 'is this build's composition trustworthy, and which build is it'. A…
No parameter schema on file.
List all SPI providers registered with the running kernel, including driver origin (community/enterprise priority).
No parameter schema on file.
Snapshot of the kernel bootstrap dependency DAG — nodes (subsystems) with their phase, declared dependencies, and running state.
No parameter schema on file.
What the JVM running the kernel actually resolved at startup: selected GC, max/committed heap, visible processors, and the container limits it detected (cgroup CPU quota/period, memory cap, cpuset) plus large-page, CDS and AOT-cache state. Null fields mean the kernel could not determine that…
No parameter schema on file.
Detail for a single kernel subsystem by name (e.g. memory, crypto, persistence, graph, transport, events, flow, http, security).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Subsystem name to describe. |
List all @ExerisDomain types known to the active LSP session.
No parameter schema on file.
Return the source-model description of an @ExerisDomain type: fields, actions, relationships, generated artefacts, and the sourceDigest that lsp-preview_mutation takes as its concurrency token.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| qualifiedName | string | yes | Fully-qualified Java class name. |
List all @Action methods across the workspace, with their owning @ExerisDomain.
No parameter schema on file.
Preview how the SDK's canonical writer would change an @ExerisDomain source file for one mutation, applied in memory. Returns { result, sourcePath, diff }: a unified diff and the SDK outcome in result.outcome — SUCCESS, CONFLICT (the source drifted from the baseline; the result carries…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| qualifiedName | string | yes | Fully-qualified Java class name of the target domain. |
| op | object | yes | One SDK MutationOp, discriminated by op: addField, removeField, renameField, changeFieldType, addRelationship, removeRelationship, changeRelationshipCardinality, addAction, removeAction. Every op ca |
| baselineJson | string | no | The entity's last-emitted target/classes/exeris-metadata/<entity>.json (see build-get_domain_metadata), as a string. The base of the three-way drift check. |
| concurrencyToken | string | no | The sourceDigest returned by lsp-describe_domain for this domain. |
List Exeris SDK annotations from the authoring contract: name, qualified name, package, targets, retention, and purpose. Supports optional filtering by package (e.g. 'system', 'security', 'capability', or full package name), target (e.g. 'METHOD', 'TYPE', 'FIELD'), or query string.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| package | string | no | Optional package filter, e.g. 'system', 'security', 'capability', or full package name. |
| target | string | no | Optional ElementType target filter, e.g. 'TYPE', 'METHOD', 'FIELD', 'PARAMETER'. |
| query | string | no | Optional case-insensitive search string matching annotation name or purpose. |
Describe a specific Exeris SDK annotation: simple and qualified name, owning package rationale, targets, retention, purpose, detailed description, all attributes (with types, defaults, required-ness, descriptions, and deprecations), and annotation-level deprecation status.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| annotation | string | yes | The annotation name to inspect. Accepts simple name (e.g. 'ExerisDomain', 'Field', 'Validation') or fully-qualified name (e.g. 'eu.exeris.sdk.annotation.ExerisDomain'). Case-insensitive. |
Get canonical authoring contract scoping rules for Exeris SDK annotations (including @Field vs @Validation split, FieldMetadata as single AST carrier per ADR-054, derived SQL NOT NULL and API not-blank generator semantics, form lifecycle scoping, deprecations, and sibling vs nested form trap).…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| rule | string | no | Optional rule identifier (e.g. 'field-vs-validation-split', 'single-ast-carrier', 'derived-nullability-semantics', 'form-lifecycle-scoping', 'deprecation-fallbacks', 'nested-form-trap') or search quer |
List all deprecated Exeris SDK annotations and attributes across the authoring contract, including replacement guidance, since version, and forRemoval status. Supports filtering by package or forRemoval only.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| forRemovalOnly | boolean | no | If true, only returns items marked for removal (forRemoval: true). Defaults to false. |
| package | string | no | Optional package filter (e.g. 'system', 'security', 'capability', or full package name). |
Get JSON Schema for the Exeris build-time DomainMetadata AST and sibling records. If 'definition' is omitted, returns the top-level schema envelope, reader requirements (such as Jackson 3 constraints), and definition list. If 'definition' is specified (e.g. 'DomainMetadata', 'FieldMetadata',…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| definition | string | no | Optional AST definition name (e.g. 'DomainMetadata', 'FieldMetadata', 'ActionMetadata'). |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under Apache-2.0
- 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 Exeris AI Bridge 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 94 / 100
Release 0.8.0 · scanned 28 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 score94
Findings3 threat · 0 capability
Capabilityhigh
Coveragesource
Verificationsource
Surface digeste0b28cc22cc22148da3cb75abc7f449410e8603724df2bfc72023010f01fde8b
Score vectorthreat 100 → client 94
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| 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 surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, 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. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
can execute shell commands or code
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 digeste0b28cc22cc22148
Scanned2026-10-28
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.8.0. Pin a release below and the command asks for exactly that one.
0.8.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 Exeris AI Bridge 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.