FoxPlug status
Answered our latest tool-list check 16 hours ago with 11 tools. It will be marked verified after 3 successful checks in 7 days.
- Answered (30 days)
- 1 of 1 checks
- Last seen working
- 16 Nov, 18:17 UTC
- Last commit
- —
- Licence
- Not stated
Live checks
We call this hosted server's tools/list endpoint without credentials, from the public internet, every day while it answers and weekly otherwise.
- Answered
- Needs sign-in
- No answer
| Checked (UTC) | Result | Response time | Tools |
|---|---|---|---|
| 16 Nov, 18:17 | Answered | 1.6 s | 11 |
Tools (11)
Read from the server on 16 Nov 2026.
- record_work
- 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.
- log_update
- 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.
- get_brief
- 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.
- list_drafts
- The latest post drafts FoxPlug wrote for the founder (channel, status, text). Read-only; nothing is posted or changed.
- simulate_buyers
- 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
- set_plan
- 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.
- check_drift
- 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.
- get_plan_status
- 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.
- what_nobody_knows
- 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.
- recall
- 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.
- supersede_fact
- 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.