Official MCP server for esa.io - a documentation sharing service for teams
Nothing to run from here
Bevy Manual 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.
91/100
trust score
16
tools declared
local
runs on your machine
33
downloads
What it does
Version-accurate Bevy API docs, Book, migration guides and examples for AI agents.
Quickstart
Install it the way its author documents:
1. cargo install bevy-manual-mcp --version 0.5.2
The full guide: https://crates.io/crates/bevy-manual-mcp
Publishernot claimed
KIAll 1 server
kinkirill1 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 Bevy Manual 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.
Install it the way its author documents:
1. cargo install bevy-manual-mcp --version 0.5.2
The full guide: https://crates.io/crates/bevy-manual-mcp
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.
Reports which Bevy version is indexed, how many records exist, and which source directories were found. Call this first if search results look wrong, empty, or from the wrong version - it is the fastest way to find out whether the API index is missing entirely.
No parameter schema on file.
Hybrid search over the Bevy API reference (rustdoc), the Bevy Book, migration guides, release notes and engine examples, all pinned to the configured Bevy version. Use this for ANY question about how to do something in Bevy. Pass an exact symbol (e.g. "App::add_systems", "Query") to get its real…
No parameter schema on file.
Exact lookup of an API item in the rustdoc index for the configured Bevy version. Returns the real signature, full documentation, doctest examples and related items. Use this whenever you need to confirm a type, trait, method or function exists and how it is actually spelled in this version.…
No parameter schema on file.
Finds runnable Bevy example code, either from the engine's own examples/ directory or from the Bevy Book's quick-start projects. Use this when you need a working pattern for a concrete task (2D/3D rendering, UI, input, audio, assets, state, gizmos) rather than an API signature. Returns the…
No parameter schema on file.
Returns breaking changes between two Bevy versions. Use this whenever upgrading a project, when the user's code fails to compile, or when you are unsure whether an API changed between releases. Includes consolidated migration guides and per-PR breaking-change notes.
No parameter schema on file.
Shows the same API symbol as it exists in each compiled Bevy version, and states plainly whether the signature changed. Use this during an upgrade to decide whether a specific call site actually needs rewriting, instead of guessing from a migration guide. Call bevy_indexed_versions first to see…
No parameter schema on file.
Checks THIS MCP server's published release index for a newer corpus than the installed one: patch refreshes, index revisions, and new Bevy minors. It compares the installed corpus version/revision with the GitHub index-manifest.json, caches the result for six hours, and returns the exact…
No parameter schema on file.
Checks crates.io for the newest published Bevy version and compares it to the version this server is indexed for. IMPORTANT: it distinguishes a PATCH release (bug fixes only, no API changes) from a MINOR release (where Bevy makes sweeping breaking API changes). Pre-releases are reported separately…
No parameter schema on file.
Lists every Bevy version this server knows about, marking the active one and whether its compiled corpus is installed. Use this to discover whether you can compare APIs across versions (for example to show a user how a signature differs between two releases). The active version is the one matching…
No parameter schema on file.
Checks which Bevy features are enabled in the project's Cargo.toml and whether specific symbols or subcrates are available. Use this when writing code to verify that types, plugins, or systems you reference are actually available given the project's feature flags. Returns a clear yes/no for each…
No parameter schema on file.
Lints one or more Rust fn items against Bevy's system access rules (R1-R5). Catches the class of bug that compiles cleanly but panics at runtime: B0001 (conflicting Query refs) and B0002 (Res/ResMut and &mut World conflicts). Parses with syn, so a fn inside a comment or string is ignored,…
No parameter schema on file.
Provides performance guidance for Bevy systems. With a topic argument, returns the exact API symbols to use. With code, detects anti-patterns such as manual is_changed/is_added checks that prevent archetype optimisation. Today the advice comes from built-in topics (change-detection, archetypes,…
No parameter schema on file.
Takes a pasted panic or warning message from Bevy and explains the cause, severity and suggested fix. Extracts error codes such as B0001/B0002 automatically, resolves them against the pinned version's vendored guides, and rejects codes that do not exist in that version. Uncoded panics get an…
No parameter schema on file.
Fans out search across the primary Bevy corpus and any compiled plugin corpora installed under data/corpora/<crate>/<version>/ (or listed in the config's corpora array). Every result is labelled with its corpus id so bevy_egui::Button and bevy_ui::Button stay distinct. corpora_searched and…
No parameter schema on file.
Answers both directions of the plugin compatibility question: which plugin versions go with the pinned Bevy, and what does a plugin require. Uses the vendored vendor/ecosystem/compat.json snapshot only (offline, no crates.io fallback) and reports its provenance. Unsupported requirement operators…
No parameter schema on file.
Generates a self-contained plugin scaffold for the pinned Bevy version and fills supported parameters (PLUGIN_NAME, RESOURCE_TYPE, SYSTEM_NAME, SYSTEM_SET, UPDATE). The result is parsed with syn before it is returned, and every template is complete on its own. Symbol presence is reported as…
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 Bevy Manual 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 91 / 100
Release 0.5.2 · scanned 30 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 score91
Findings1 threat · 0 capability
Capabilityminimal
Coveragemetadata
Verificationrepo
Surface digest2dc22d3bf39daa3966da07121ef3ae7218597d0cc75600bd6ac9471b4c82a657
Score vectorthreat 100 → client 91
| 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 | metadata | inspection depth (metadata) — how much of the target the scan could see | −8 |
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 sourcenot available
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>".
The implementation source was not read — the published package was fetched but contains no source files the scanner reads.
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 digest2dc22d3bf39daa39
Scanned2026-10-30
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
It installs from its repository rather than from a versioned package, so the command cannot be pinned to a release. The history below is for reading; the current release on file is 0.5.2.
0.5.2
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 Bevy Manual 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.