FoxPlug
REMOTE · FOXPLUG.COM
Your agent records what you ship; FoxPlug drafts launch posts and a changelog. Nothing posts.
Available components
Last scanned (10 hours ago)
Scores higher than 71% of remote servers
Reachable. Last reached 22 Nov 2026.
Category Marketing and SEO
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2295 tokens (~208/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Where what the registry lists and what we observed about the package disagree. This is read from the stored diagnostics and is never an input to the score.
Authorisation metadata
- Registry says
https://foxplug.com/mcp- Package shows
https://fybedvapqhhgctkeqvbs.supabase.co/functions/v1/lcnc-mcp
The document's resource does not share an origin with the endpoint we probed. See the evidence →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 0
- “record_work” added an optional parameter “from_app” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 13 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 12 Nov 26 73
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Nov 2026 · Probed https://foxplug.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=foxplug.com | CN=WE1,O=Google Trust Services,C=US | 24 Oct 2026 | 22 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 48ab319bdf67feb413d594836e6887b7 |
| SANs: foxplug.com, *.foxplug.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of foxplug.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| foxplug.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="lcnc-mcp", error="invalid_token", error_description="Authorization required (Bearer token)", resource_metadata="https://fybedvapqhhgctkeqvbs.supabase.co/functions/v1/lcnc-mcp/.well-known/oauth-protected-resource"
Bearer realm="lcnc-mcp", error="invalid_token", error_description="Authorization required (Bearer token)", resource_metadata="https://fybedvapqhhgctkeqvbs.supabase.co/functions/v1/lcnc-mcp/.well-known/oauth-protected-resource" | Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
Protected resource metadata
| Document | https://fybedvapqhhgctkeqvbs.supabase.co/functions/v1/lcnc-mcp/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Problem | Describes a different resource |
| Resource | https://fybedvapqhhgctkeqvbs.supabase.co/functions/v1/lcnc-mcp |
| Authorisation server | https://fybedvapqhhgctkeqvbs.supabase.co/functions/v1/lcnc-mcp |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://foxplug.com/mcp | Verified | 200 | |
| http (plaintext) | http://foxplug.com/mcp | HTTPS enforced | 301 | https://foxplug.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_drift ~167
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.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | yes | The project this work belongs to — a FoxPlug project name, domain, or repo (e.g. 'foxplug', 'foxplug.com', or 'owner/lcncagents'). Matched case-insensitively against your own FoxPlug projects and any… |
No output schema declared.
No examples provided.
get_brief ~168
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.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | – | The project this work belongs to — a FoxPlug project name, domain, or repo (e.g. 'foxplug', 'foxplug.com', or 'owner/lcncagents'). Matched case-insensitively against your own FoxPlug projects and any… |
No output schema declared.
No examples provided.
get_plan_status ~164
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.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | yes | The project this work belongs to — a FoxPlug project name, domain, or repo (e.g. 'foxplug', 'foxplug.com', or 'owner/lcncagents'). Matched case-insensitively against your own FoxPlug projects and any… |
No output schema declared.
No examples provided.
list_drafts ~150
The latest post drafts FoxPlug wrote for the founder (channel, status, text). Read-only; nothing is posted or changed.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many, 1 to 10. Defaults to 5. |
| project | string | – | The project this work belongs to — a FoxPlug project name, domain, or repo (e.g. 'foxplug', 'foxplug.com', or 'owner/lcncagents'). Matched case-insensitively against your own FoxPlug projects and any… |
No output schema declared.
No examples provided.
log_update ~263
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.
| Name | Type | Req | Description |
|---|---|---|---|
| details | string | – | Optional. Notable decisions or trade-offs (1-2 sentences). |
| project | string | – | The project this work belongs to — a FoxPlug project name, domain, or repo (e.g. 'foxplug', 'foxplug.com', or 'owner/lcncagents'). Matched case-insensitively against your own FoxPlug projects and any… |
| summary | string | yes | One short plain paragraph on what changed and why a person would care. No secrets. |
| user_facing | boolean | – | True (default) when a user would notice the change. False for plumbing: refactors, dependency bumps, migrations. |
No output schema declared.
No examples provided.
recall ~172
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.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | – | The project this work belongs to — a FoxPlug project name, domain, or repo (e.g. 'foxplug', 'foxplug.com', or 'owner/lcncagents'). Matched case-insensitively against your own FoxPlug projects and any… |
No output schema declared.
No examples provided.
record_work ~275
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.
| Name | Type | Req | Description |
|---|---|---|---|
| decisions | string | – | Optional. Notable decisions or trade-offs made this session (1-2 sentences). |
| files_touched | array | – | Optional. Key file paths changed this session — context only. |
| from_app | string | – | Optional. Set by the FoxPlug app for Jira so the record shows a From Jira label. Leave out otherwise. |
| project | string | yes | The project this work belongs to — a FoxPlug project name, domain, or repo (e.g. 'foxplug', 'foxplug.com', or 'owner/lcncagents'). Matched case-insensitively against your own FoxPlug projects and any… |
| summary | string | yes | A short human summary of what you built or changed this session (1-3 sentences). No secrets. |
No output schema declared.
No examples provided.
set_plan ~232
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.
| Name | Type | Req | Description |
|---|---|---|---|
| horizon | string | – | Optional. The time frame this plan covers (e.g. 'this week', 'this sprint'). |
| plan | string | yes | The current plan, intent, or priorities for this project, in 1 to 5 sentences. No secrets. |
| project | string | yes | The project this work belongs to — a FoxPlug project name, domain, or repo (e.g. 'foxplug', 'foxplug.com', or 'owner/lcncagents'). Matched case-insensitively against your own FoxPlug projects and any… |
No output schema declared.
No examples provided.
simulate_buyers ~288
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.
| Name | Type | Req | Description |
|---|---|---|---|
| change | string | yes | The change as a buyer would read it (20 to 4000 characters): the new pricing page text, the feature description or the launch copy. |
| project | string | – | The project this work belongs to — a FoxPlug project name, domain, or repo (e.g. 'foxplug', 'foxplug.com', or 'owner/lcncagents'). Matched case-insensitively against your own FoxPlug projects and any… |
No output schema declared.
No examples provided.
supersede_fact ~115
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.
| Name | Type | Req | Description |
|---|---|---|---|
| fact_id | string | yes | The id of the fact, from recall. |
| reason | string | yes | Why it is no longer true. Required. |
| replacement_fact_id | string | – | Optional. The fact that replaced it. |
No output schema declared.
No examples provided.
what_nobody_knows ~170
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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | How far back to look. Defaults to 30. |
| project | string | yes | The project this work belongs to — a FoxPlug project name, domain, or repo (e.g. 'foxplug', 'foxplug.com', or 'owner/lcncagents'). Matched case-insensitively against your own FoxPlug projects and any… |
No output schema declared.
No examples provided.
How do I install the FoxPlug MCP server?
FoxPlug is a hosted endpoint at https://foxplug.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · foxplug.com
claude mcp add --transport http osakasaul-foxplug 'https://foxplug.com/mcp'
What is the FoxPlug MCP server?
FoxPlug is an MCP server listed in the public MCP registry as io.github.OsakaSaul/foxplug. Your agent records what you ship; FoxPlug drafts launch posts and a changelog. Nothing posts. This page covers its hosted endpoint (https://foxplug.com/mcp).
Is the FoxPlug MCP server safe to use?
FoxPlug scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the FoxPlug MCP server expose?
FoxPlug exposes 11 tools: record_work, log_update, get_brief, list_drafts, simulate_buyers, and 6 more. Their descriptions and schemas cost roughly 2,164 tokens of context every time the server is loaded.
Does the FoxPlug MCP server require authentication?
Yes. FoxPlug asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the FoxPlug MCP server still maintained?
FoxPlug is still listed as active in the MCP registry. We last reached this channel on 22 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the FoxPlug MCP server?
VerifyMCP ran 13 checks on FoxPlug, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.