yof MCP server
io.yof/yofyof.iostreamable-httpv0.3.2Scanned
Checks AI-written code for leaked keys and made-up packages, on your machine. Never uploads code.
8 tools: 4 change things and 4 only read.
- Reads private data · 2
- Reads text others write · 2
- Can send data out · 0
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
4 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the yof MCP server can do
The yof MCP server is published by yof.io, a domain the MCP Registry verified. It has 8 tools. It can create or change data (4 tools: yof_fix_prompt, yof_verify, yof_check and yof_patch_status), but cannot delete data. 4 tools only read.
2 tools read private data (yof_apps and yof_findings); 2 tools bring in text other people can write (yof_check and yof_lessons).
The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 10, 2026, version 0.3.2.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
8 tools
Changes things 4Claude Code: ask
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).Reads text others writeNo findings
Why it is in this group
- The description's first verb is "start": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Start 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 result. Each call uses your daily check allowance (10 a day, 100 with Patch) as well as yof's own limits per app and site; a repo read also needs a proven app, Patch and a linked repository. Returns started, target and id, or started false with a code and the reason.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
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.1 finding
Why it is in this group
- The description's first verb is "write": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "yof_fix_prompt" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "write": a word for a change.
Description, as the server wrote it Write 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 reads that stored finding (file, line, app address) to make the steps specific; one of the two ids is required. Returns rule and instructions, plus finding_id when one was passed.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
yof_patch_statusList Patch's open fix pull requests, with the state of each one's CI checks.1 finding
Why it is in this group
- The name "yof_patch_status" says "patch": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "yof_patch_status" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "yof_patch_status" says "patch": a word for a change.
Description, as the server wrote it List 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 about each pull request (up to 50, newest first) without asking GitHub again. Returns open (repository, number, url, draft, rule, title, checks, failed_checks, opened) and a note; an empty list means Patch has no open pull request.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
yof_verifyReport whether one finding is fixed, according to yof's latest finished check; it does not run a new check.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Report 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, last_check and why; a risk you accepted shows status accepted and fixed false.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 4Show 4 read-only tools
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.Reads private dataNo findings
Why it is in this group
- The description's first verb is "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "repository": it reads repositories.
Description, as the server wrote it List 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 for your account (up to 50 apps); it starts no check. Returns apps; an empty list means no app was added in the yof dashboard yet.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
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.No findings
Why it is in this group
- The name "yof_explain" says "explain": a word for reading.
Description, as the server wrote it Explain 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 only, no account data; an unknown rule id is an error. Returns rule, title, why, severity, safe_fix and standards.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
yof_findingsList open findings for your proven apps, from their live sites and linked GitHub repositories, with secret values redacted.Reads private dataNo findings
Why it is in this group
- The description's first verb is "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "repository": it reads repositories.
Description, as the server wrote it List 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 stored from its latest checks, most recently seen first; this server cannot read files on your computer (the local server's yof_check does that). Returns findings (id, app, rule, title, severity, kind, where, value, first and last seen) and next; an empty list means no open findings, and apps not proven yours are left out.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
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.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "list" and "pull request": it reads issues, which other people can write.
Description, as the server wrote it List 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 still open. Reads stored data only (up to 50 merged pull requests, most recently opened first); a fix that yof's re-scan did not confirm is never reported as fixed. Returns lessons (repository, pull_request, merged, rule, note, avoid_next_time); an empty list means no Patch fix has been merged yet.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data2
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 17, 2026, 15:21 UTC, unchanged since Nov 17, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 4
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.yof.io/mcp: tools/list returned 8 tools to an anonymous client, including yof_fix_prompt (write), yof_verify (write), yof_check (write), yof_patch_status (write)
Posture changes
- Nov 17, 2026
- HTTP status of an anonymous initialize: 401 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 4
- Protocol version: none to 2025-06-18
- WWW-Authenticate on 401: yes to not observed
Findings
Matches of fixed checks, with the text they matched.
- Warnyof_fix_prompt
The server marks "yof_fix_prompt" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "write": a word for a change.
- Warnyof_patch_status
The server marks "yof_patch_status" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "yof_patch_status" says "patch": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. HTTP status of an anonymous initialize: 401 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 4 (and 2 more).View diff
- HTTP status of an anonymous initialize: 401 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 4
- Protocol version: none to 2025-06-18
- WWW-Authenticate on 401: yes to not observed
Tools8 changed.~8 changedView diff
- Changed:yof_appsOnly readsdescription
- Changed:yof_checkChanges thingsdescriptioninputSchema
- Changed:yof_explainOnly readsdescriptioninputSchema
- Changed:yof_findingsOnly readsdescriptioninputSchema
- Changed:yof_fix_promptChanges thingsdescriptioninputSchema
- Changed:yof_lessonsOnly readsdescriptioninputSchema
- Changed:yof_patch_statusChanges thingsdescriptioninputSchema
- Changed:yof_verifyChanges thingsdescription
Install
Pinned to version 0.3.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http yof https://mcp.yof.io/mcp --header 'Authorization: <your-authorization>'claude mcp add --transport http yof https://mcp.yof.io/mcp --header 'Authorization: <your-authorization>'Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__yof__yof_apps",
"mcp__yof__yof_findings",
"mcp__yof__yof_explain",
"mcp__yof__yof_lessons"
],
"ask": [
"mcp__yof__yof_fix_prompt",
"mcp__yof__yof_verify",
"mcp__yof__yof_check",
"mcp__yof__yof_patch_status"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as yof. Review it before you use it.
Capability tags behind 4 rules
- mcp__yof__yof_apps private-data
- mcp__yof__yof_findings private-data
- mcp__yof__yof_check untrusted-input
- mcp__yof__yof_lessons untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.yof/yof/verify?hash=f8eb24dd40d70d7fa83d73b19863a2f250a0ccf881ad514adc12f122251be63a" | jq -e '.changed == false'Pinned hash f8eb24dd40d7, from Nov 10, 2026, 20:20 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.yof/yof/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.yof/yof)Source: MCP Registry · repository. Synced Nov 10, 2026, 20:20 UTC.
yof MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the yof MCP server safe?
- No scan can promise that. What its definitions show: 8 tools, 4 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the yof MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the yof MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the yof MCP server have?
- 8 tools: 4 write, 4 read. yof_fix_prompt, yof_verify, yof_check, yof_patch_status, yof_apps, yof_findings, yof_explain and yof_lessons.
Does the yof MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the yof MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the yof MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 10, 2026. Every change is on this page and in its Atom feed.