FoxPlug MCP server
io.github.OsakaSaul/foxplugOsakaSaulstreamable-httpv1.0.0Scanned
Your agent records what you ship; FoxPlug drafts launch posts and a changelog. Nothing posts.
11 tools: 1 do something that can't be undone, 7 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- 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 FoxPlug MCP server can do
The FoxPlug MCP server is published by the GitHub account OsakaSaul. It has 11 tools. It can do things that cannot be undone, such as sending, paying or publishing (supersede_fact) and create or change data (7 tools: record_work, log_update, simulate_buyers, set_plan and 3 more), but cannot delete data. 3 tools only read.
1 tool brings in text other people can write (list_drafts).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 12, 2026, version 1.0.0.
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.
11 tools
Can't be undone 1Claude Code: ask
supersede_factMark a remembered fact as finished, so it is never proposed again.No findings
Why it is in this group
- The description's first verb is "mark": a word for a change.
- The description says "cannot be restored".
Description, as the server wrote it Mark a remembered fact as finished, so it is never proposed again. Takes the fact id from recall and a REASON — a fact struck out without a reason cannot be restored. This is the only one of these tools that changes anything, and it changes memory, never anything public. Free.
Annotations the server declares
- title: Supersede a fact
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
Changes things 7Claude Code: ask
check_driftCheck whether a project's recent work still matches its current plan.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 Check whether a project's recent work still matches its current plan. FoxPlug compares the plan you set (via set_plan) against the work recorded since, and returns an alignment verdict with any divergences — work that is off-plan, or plan items nothing has moved toward. Read-only judgment; it never posts anything. Free.
Annotations the server declares
- title: Check drift
- readOnlyHint: true
- destructiveHint: false
log_updateTell FoxPlug what you just finished building, in one short plain paragraph.1 finding
Why it is in this group
- The name "log_update" says "log": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
Findings
- Warn
The server marks "log_update" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false}; The name "log_update" says "log": a word for reading.
Description, as the server wrote it Tell FoxPlug what you just finished building, in one short plain paragraph. Call it after a change a user would notice (user_facing true) or after plumbing nobody outside needs to hear about (user_facing false, which is kept out of drafts and counts toward "not worth a post"). It never posts anything. Free. Do NOT include secrets, keys, or tokens.
Annotations the server declares
- title: Log an update
- readOnlyHint: false
- destructiveHint: false
recallWhat FoxPlug remembers about this maker, with an epistemic status on every fact: settled (more than one observation, none contradicting), thin (seen once), contested (the evidence …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 What FoxPlug remembers about this maker, with an epistemic status on every fact: settled (more than one observation, none contradicting), thin (seen once), contested (the evidence disagrees with itself), superseded (replaced by something later — never propose it again). Read-only. Free.
Annotations the server declares
- title: Recall what we know
- readOnlyHint: true
- destructiveHint: false
record_workRecord a build-work summary into FoxPlug as a milestone (source: Claude Code).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.
Description, as the server wrote it Record a build-work summary into FoxPlug as a milestone (source: Claude Code). Call this at the end of a session. It captures what you shipped so FoxPlug can score it and surface the shippable moments in your Radar. It never posts anything. Free — capture is not metered. Do NOT include secrets, keys, or tokens in the summary.
Annotations the server declares
- title: Record work
- readOnlyHint: false
- destructiveHint: false
set_planSet the current plan, intent, or priorities for a project in FoxPlug (source: Claude Code).No findings
Why it is in this group
- The name "set_plan" says "set": a word for a change.
Description, as the server wrote it Set the current plan, intent, or priorities for a project in FoxPlug (source: Claude Code). Call this when you set or change what a project is working toward, so FoxPlug knows the goal your later work is measured against. It replaces the project's previous current plan. Free — it never posts anything. Do NOT include secrets, keys, or tokens in the plan.
Annotations the server declares
- title: Set plan
- readOnlyHint: false
- destructiveHint: false
simulate_buyersBefore you merge or ship, ask your buyers.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.
Description, as the server wrote it Before you merge or ship, ask your buyers. Give the change as the buyer would see it (pricing text, a feature description, launch copy). FoxPlug builds 3 to 5 buyer personas ONLY from evidence the founder already gave it (their site, the feedback requests they connected, what they shipped), each citing its evidence, and returns how each would react: would buy, hesitate or leave, the objection, the exact sentence that confused them and what would change their mind, plus the top objections and a tighter rewrite. It is a SIMULATION, not real customers, and says so. The first simulation per project is free; more need a paid plan. Nothing is posted or changed.
Annotations the server declares
- title: Ask my buyers (simulated)
- readOnlyHint: false
- destructiveHint: false
what_nobody_knowsWhat this project shipped that nobody outside it knows about.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 What this project shipped that nobody outside it knows about. Counts the milestones worth talking about in a window and how many of them were actually posted, and names the loudest silent ones. Read-only — it generates nothing and posts nothing. Free.
Annotations the server declares
- title: What nobody knows yet
- readOnlyHint: true
- destructiveHint: false
Only reads 3Show 3 read-only tools
get_briefThis week's brief from FoxPlug: one thing to fix, one to say and one to skip, with where each number came from.No findings
Why it is in this group
- The name "get_brief" says "get": a word for reading.
Description, as the server wrote it This week's brief from FoxPlug: one thing to fix, one to say and one to skip, with where each number came from. Ask it when the founder wonders what to post. Read-only. It does not rebuild the brief; the founder presses Build the brief in FoxPlug.
Annotations the server declares
- title: Get the brief
- readOnlyHint: true
- destructiveHint: false
get_plan_statusGet where a project stands: its current plan, how much work has been recorded since the plan was set, and the latest drift verdict (if any).No findings
Why it is in this group
- The name "get_plan_status" says "get": a word for reading.
Description, as the server wrote it Get where a project stands: its current plan, how much work has been recorded since the plan was set, and the latest drift verdict (if any). Read-only and cheap — it runs no judgment, so use it to pull current state without re-running check_drift. It never posts anything. Free.
Annotations the server declares
- title: Get plan status
- readOnlyHint: true
- destructiveHint: false
list_draftsThe latest post drafts FoxPlug wrote for the founder (channel, status, text).Reads text others writeNo findings
Why it is in this group
- The name "list_drafts" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "post": it reads posts, which other people can write.
Description, as the server wrote it The latest post drafts FoxPlug wrote for the founder (channel, status, text). Read-only; nothing is posted or changed.
Annotations the server declares
- title: List drafts
- readOnlyHint: true
- destructiveHint: 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 private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- 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 19, 2026, 17:21 UTC, unchanged since Nov 12, 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
- 8
- Protocol version
- 2025-03-26
- 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
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 8 tools that change things (1 irreversible, 7 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://foxplug.com/mcp: tools/list returned 11 tools to an anonymous client, including supersede_fact (irreversible), record_work (write), log_update (write), simulate_buyers (write), set_plan (write) and 3 more
Findings
Matches of fixed checks, with the text they matched.
- Warnlog_update
The server marks "log_update" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false}; The name "log_update" says "log": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http foxplug https://foxplug.com/mcp --header 'Authorization: <your-authorization>'claude mcp add --transport http foxplug https://foxplug.com/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__foxplug__get_brief",
"mcp__foxplug__list_drafts",
"mcp__foxplug__get_plan_status"
],
"ask": [
"mcp__foxplug__record_work",
"mcp__foxplug__log_update",
"mcp__foxplug__simulate_buyers",
"mcp__foxplug__set_plan",
"mcp__foxplug__check_drift",
"mcp__foxplug__what_nobody_knows",
"mcp__foxplug__recall",
"mcp__foxplug__supersede_fact"
],
"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 foxplug. Review it before you use it.
Capability tags behind 1 rule
- mcp__foxplug__list_drafts 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.github.OsakaSaul/foxplug/verify?hash=cc41d685368a8b44699ad120fbb2d72cca69cecceebc31215c4a5fc28b04b74a" | jq -e '.changed == false'Pinned hash cc41d685368a, from Nov 12, 2026, 08:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.OsakaSaul/foxplug/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.OsakaSaul/foxplug)Source: MCP Registry. Synced Nov 12, 2026, 08:18 UTC.
FoxPlug MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the FoxPlug MCP server safe?
- No scan can promise that. What its definitions show: 11 tools, 8 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the FoxPlug MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the FoxPlug MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: supersede_fact.
What tools does the FoxPlug MCP server have?
- 11 tools: 1 irreversible, 7 write, 3 read. supersede_fact, record_work, log_update, simulate_buyers, set_plan, check_drift, what_nobody_knows, recall and 3 more.
Does the FoxPlug MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the FoxPlug MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the FoxPlug MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 12, 2026.