Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search
Nothing to run from here
Eased 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.
96/100
tool-list score
5
tools declared
remote
at its publisher
—
calls last 7d
What it does
Motion-first React components for shadcn: search, read docs and get install commands.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http eased-mcp https://eased.dev/api/mcp
# 2 — ask your agent for something these tools do
# get_skill, list_components, search_components and 2 more
Eased costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
EAAll 1 server
eased1 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. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http eased-mcp https://eased.dev/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: 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 pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
5 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.
The Eased design skill as Markdown: how to install and compose Eased components, the tokens, and the checkable rules every component is built on (alignment, the 1:2 spacing ratio, concentric radii, springs per role, enter and exit, focus rings, reduced motion). Call it first, before you build or change UI with Eased, and follow it while you work.
No parameter schema on file.
List every Eased component (motion-first React components installed with the shadcn CLI) in catalogue order, with slug, title, one-line summary, tier (free or pro), interaction verb (Hover, Press, Drag, Slide, Select, Type, Loading, Scroll), the industries it suits and page URL. Use it to browse what exists, optionally for one industry (e.g. crypto, legal); use search_components to find one for a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tier | string | no | Only free (MIT, installable now) or only Pro components. Leave out for both. |
| industry | string | no | Only components tagged for this industry: ai (AI agents), devtools (developer tools), finance (fintech and FX), crypto (crypto), saas (SaaS analytics), legal (legal tech), ecommerce (e-commerce), real |
Find Eased components for a need, e.g. "loading state", "tooltip", "drag to adjust a number" or "tabs with a sliding indicator". Matches title, slug, interaction verb, description and README docs, best match first; pass industry to keep to one (e.g. "a swap UI" for crypto). Follow up with get_component for docs and source.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | What the component should be or do, in a few words. |
| industry | string | no | Only components tagged for this industry: ai (AI agents), devtools (developer tools), finance (fintech and FX), crypto (crypto), saas (SaaS analytics), legal (legal tech), ecommerce (e-commerce), real |
Everything about one Eased component as Markdown: title, description, tier, README docs (usage, props, motion signature), install command and dependencies. Free components also include the full source of their files and a demo showing real usage, so you can read or adapt the code. Pro components return docs and metadata only, unless this server was added with an Eased Pro token header, in which ca
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | The component slug, e.g. "button" or "hover-card", as returned by list_components or search_components. |
One npx shadcn add … command that installs the given Eased components (and their tokens and helpers) into the current project. Only free components install from the public registry; Pro components are listed separately as requiring Eased Pro.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slugs | array | yes | Component slugs to install, e.g. ["button", "tooltip"]. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- 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 Eased 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: —
ATool-list grade · score 96 / 100
Release 1.0.0 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
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 score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digest16db2da797e157444824a1c6ec4f4cebef36e92f1e8a6b36a79b9c92c7665464
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
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.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
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_skill | no tags | |
| list_components | untrusted-input | untrusted-input: keyword "browse" |
| search_components | no tags | |
| get_component | no tags | |
| get_install_command | 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 digest16db2da797e15744
Scanned2026-10-20
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
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.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 Eased 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.