Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search
Nothing to run from here
Modei 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.
99/100
trust score
1
downloads a day
local
runs on your machine
50
downloads in 30d
What it does
Modei MCP Server — trust infrastructure tools for AI agents in Claude, Cursor, and any MCP client
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user modei-mcp '--' npx -y modei-mcp
# 2 — ask your agent for something these tools do
# get_anonymous_policy, set_anonymous_policy, get_anonymous_log and 42 more
Modei costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
STAll 1 server
standardlogic1 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 Modei 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 modei-mcp '--' npx -y modei-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
45 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.
Get the anonymous access policy for a gate.
No parameter schema on file.
Configure anonymous access policy on a gate.
No parameter schema on file.
Get the anonymous access audit log for a gate.
No parameter schema on file.
List your API keys.
No parameter schema on file.
Create a new API key.
No parameter schema on file.
Revoke an API key.
No parameter schema on file.
List attestations (audit log entries) for a gate. Shows what agents did and whether actions were allowed.
No parameter schema on file.
Record a new attestation. Usually called automatically by MCP servers, but can be called manually for testing.
No parameter schema on file.
Get the active draft permission catalog for a gate.
No parameter schema on file.
Create or update the permission catalog for a gate. Defines what permissions agents can request.
No parameter schema on file.
Build, sign, and atomically publish a catalog snapshot.
No parameter schema on file.
List all published catalog versions (metadata only).
No parameter schema on file.
Get a specific published catalog version.
No parameter schema on file.
Get impact analysis for pending catalog changes.
No parameter schema on file.
Test a passport against a gate to preview the canonical authorization decision (allow on grant, block on refusal).
No parameter schema on file.
Test authorization without executing. Simulates a full gate check.
No parameter schema on file.
Discover services by capability (public, no auth required).
No parameter schema on file.
Issue a consumption attestation for bilateral metering.
No parameter schema on file.
Generate a billing settlement for a period.
No parameter schema on file.
List settlement summaries.
No parameter schema on file.
Get a settlement by ID.
No parameter schema on file.
Transition a settlement to a new status.
No parameter schema on file.
Get SLA compliance metrics for a gate.
No parameter schema on file.
Get constraints for a passport.
No parameter schema on file.
Set constraints on a passport.
No parameter schema on file.
List available constraint type definitions.
No parameter schema on file.
List system and user constraint templates.
No parameter schema on file.
Apply a constraint template to a passport.
No parameter schema on file.
Create a user constraint template.
No parameter schema on file.
Evaluate constraints and record an enforcement attestation via CEL.
No parameter schema on file.
List enforcement attestations for a passport.
No parameter schema on file.
Get a single enforcement attestation by ID.
No parameter schema on file.
Verify the cryptographic signature of an enforcement attestation.
No parameter schema on file.
List all gates you own. Gates are permission enforcement points that protect your tools.
No parameter schema on file.
Get details for a specific gate.
No parameter schema on file.
Create a new gate. A gate defines what permissions exist and enforces access control for your tools.
No parameter schema on file.
Update settings for an existing gate.
No parameter schema on file.
Delete (archive) a gate. This will deactivate all signing keys.
No parameter schema on file.
List all active passports for a gate.
No parameter schema on file.
Get details for a specific passport.
No parameter schema on file.
Issue a new passport to an agent. The passport grants the agent specific permissions for this gate.
No parameter schema on file.
Revoke a passport immediately. The agent will no longer be able to use it.
No parameter schema on file.
Re-issue a passport pinned to a newer catalog version.
No parameter schema on file.
Get spending and rate limit state for a passport.
No parameter schema on file.
Reset cumulative spending and rate counters for a passport.
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 Modei 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 99 / 100
Release 1.0.3 · 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 score99
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digest66ff59ecd2ab13834449f31a5644ee7fea1ab9ede72d8a783912a6a34bd6a117
Score vectorthreat 100 → client 99
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| 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. minimal 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. | ||
No tool surface was enumerated, so there is nothing to attribute a capability to.
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 digest66ff59ecd2ab1383
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 1.0.3. Pin a release below and the command asks for exactly that one.
1.0.3
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 Modei 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.