Local MCP capabilities provider for Expo
Nothing to run from here
yof 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.
97/100
trust score
8
tools declared
local
or remote
—
downloads a day
What it does
Checks AI-written code for leaked keys and made-up packages, on your machine. Never uploads code.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user yof-mcp '--' npx -y @yof/cli mcp
# 2 — ask your agent for something these tools do
# yof_check, yof_check_diff, yof_explain and 5 more
yof costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
YOAll 1 server
yof1 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 can run either way — at an address its publisher runs, or as a process under your own user, with your files and your network — and this marketplace is in the path of neither.
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 yof-mcp '--' npx -y @yof/cli mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Or connect to its publisher’s address
Its publisher also runs it at https://mcp.yof.io/mcp: nothing to start on your machine, and this marketplace is not in the path.
claude mcp add --scope user --transport http yof-mcp https://mcp.yof.io/mcpFree 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 YOF_API_KEY (Optional. The key the yof dashboard makes for this connection (Connect your AI builder). Without it, only the local tools run.) if you want to set it.
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
8 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.
Scan the project folder on this computer for leaked keys and made-up or risky packages. Runs locally; code is never uploaded. Use before you say a change is done.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | no | — | |
| offline | no | — |
Scan only the lines that changed: pass a unified diff, or leave it out to scan the working tree's changes against the last commit (plus new files). Fast; run it after editing files.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| diff | string | no | A unified diff (at most 1 MB). Leave out to use git. |
| offline | no | — |
What a yof rule means, why it matters and the safe way to fix it, in plain words. Pass the rule id from a finding (for example secret.stripe_live or package.made_up).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| rule_id | string | yes | The rule id of a finding. |
Exact instructions to fix one finding, ready to follow. The secret value is never included, only a short prefix.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| rule_id | string | yes | The rule id of the finding. |
| file | no | — | |
| line | integer | no | The line of the finding. |
| package | string | no | For a package finding: the package name. |
| finding_id | string | no | A finding id from yof_findings (yof.io account findings). |
Re-scan one file and say whether a finding is fixed. Pass the file and the rule id (or leave the rule out to check the file for every key rule).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| file | yes | — | |
| rule_id | string | no | The rule id to look for. |
| package | string | no | For a package rule: the package name. |
| offline | no | — |
Open findings from your yof.io account (your live site and connected GitHub repositories). Needs the yof key in this tool's config.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| app_id | string | no | One app's id (default: all your apps). |
| severity | string | no | Only this urgency. |
| limit | integer | no | At most this many (default 50). |
Patch's open fix pull requests and the state of their CI checks. Read only: nothing is merged or changed.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| app_id | string | no | One app's id (default: all). |
Short notes from Patch fixes that were merged in your projects: what was fixed, where, and whether the next check confirmed it. Use them to avoid the same mistake again.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| app_id | string | no | One app's id (default: all). |
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 yof 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 97 / 100
Release 0.3.0 · scanned 10 Nov 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 score97
Findings6 threat · 0 capability
Capabilitymoderate
Coveragesource
Verificationsource
Surface digest7663c2e63274f814650e4463ac62f3265f9012aab12ab9f7649752cac0c26984
Score vectorthreat 100 → client 97
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| 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. moderate 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 start a fixed program (a process-spawning capability, not arbitrary code execution)
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 digest7663c2e63274f814
Scanned2026-11-10
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.3.0. Pin a release below and the command asks for exactly that one.
0.3.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 yof 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.