Checks AI-written code for leaked keys and made-up packages, on your machine. Never uploads code.
Connect Remote server
claude mcp add --transport http yof https://mcp.yof.io/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
{
"mcpServers": {
"yof": {
"url": "https://mcp.yof.io/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
{
"servers": {
"yof": {
"type": "http",
"url": "https://mcp.yof.io/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
Settings > Connectors > Add custom connector
URL: https://mcp.yof.io/mcp
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools 8 found in our last check
yof_appsList your apps on yof with their id, address, whether you proved the site is yours, the latest check score and the linked GitHub repository. Call it first to get the app_id that yof_findings, yof_check, yof_patch_status and yof_lessons take. Reads only what yof already stored fo…
yof_findingsList open findings for your proven apps, from their live sites and linked GitHub repositories, with secret values redacted. Use it to see what to fix; pass a finding id to yof_fix_prompt for steps and to yof_verify after a fix, and use yof_check to look again. Reads results yof…
yof_explainExplain one yof rule in plain words: what it means, why it matters, how urgent it is, the safe fix and its CWE and OWASP references. Use it to understand a finding from yof_findings; use yof_fix_prompt instead for step-by-step instructions for one finding. Reads yof's rule list…
yof_fix_promptWrite step-by-step instructions to fix one finding (pass finding_id) or one kind of problem (pass rule_id), with any secret shown only as a prefix plus REDACTED. Use it after yof_findings; use yof_explain for background on a rule, and yof_verify after the fix. With finding_id it…
yof_verifyReport whether one finding is fixed, according to yof's latest finished check; it does not run a new check. After a fix, run yof_check first, wait for it to finish, then call this; use yof_findings to get finding ids. Returns finding_id, rule, status, fixed, fixed_at, last_seen,…
yof_checkStart a new check of one of your apps: target site checks the live site, target repo reads the linked GitHub repository (read only). Use it after a fix is deployed or pushed, then ask yof_verify or yof_findings a few minutes later; it returns at once and does not wait for the re…
yof_patch_statusList Patch's open fix pull requests, with the state of each one's CI checks. Use it to see whether a fix Patch proposed is waiting, passing or failing; use yof_lessons for fixes already merged, and yof_findings for problems with no pull request yet. Reads what yof last stored ab…
yof_lessonsList short lessons from Patch fixes that were merged: what was fixed, in which pull request, whether yof's next check confirmed it, and how to avoid it next time. Use it before writing similar code so the same problem does not come back; use yof_patch_status for pull requests st…
Headers
| Name | Description |
|---|---|
AuthorizationRequired, secret | Bearer followed by the key the yof dashboard makes for this connection. Needed to run any tool; the tool list can be read without it. |
Details
| Endpoint | https://mcp.yof.io/mcp (Streamable HTTP) |
| Package | @yof/[email protected] (NPM, stdio) |
| First published | 10 Nov 2026 |
| Last updated | 10 Nov 2026 |
| Registry name | io.yof/yof |
More developer tools servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
