# FoxPlug (remote · foxplug.com)

Your agent records what you ship; FoxPlug drafts launch posts and a changelog. Nothing posts.

- Trust score: 78/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-22

## Components

- remote · `foxplug.com`: 78/100 (this document), [markdown](https://verifymcp.io/servers/osakasaul-foxplug/foxplug.md), [page](https://verifymcp.io/servers/osakasaul-foxplug/foxplug)

## Channel facts

- Endpoint: `https://foxplug.com/mcp`
- Transports: `streamable-http`
- Auth: `required (not validated)`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-22.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Registry listing versus package

Where what the registry lists and what we observed about the package disagree. This view is read from the stored diagnostics trace and is never an input to the score. Each row links to its evidence.

### Authorisation metadata

- Registry says: `https://foxplug.com/mcp`
- Package shows: `https://fybedvapqhhgctkeqvbs.supabase.co/functions/v1/lcnc-mcp`
- What it means: The document's resource does not share an origin with the endpoint we probed.
- Evidence: https://verifymcp.io/servers/osakasaul-foxplug/foxplug#diagnostics-auth

## Install

### 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.

### Claude

```bash
claude mcp add --transport http osakasaul-foxplug 'https://foxplug.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "osakasaul-foxplug": {
      "url": "https://foxplug.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "osakasaul-foxplug": {
      "type": "http",
      "url": "https://foxplug.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.osakasaul-foxplug]
url = "https://foxplug.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "osakasaul-foxplug": {
      "type": "remote",
      "url": "https://foxplug.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add osakasaul-foxplug --url 'https://foxplug.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  osakasaul-foxplug:
    url: "https://foxplug.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "osakasaul-foxplug": {
      "Transport": "http",
      "Url": "https://foxplug.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add osakasaul-foxplug -t streamable-http -u 'https://foxplug.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "osakasaul-foxplug": {
      "type": "http",
      "url": "https://foxplug.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 78, +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.

### 2026-11-19 (score 77, +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.

### 2026-11-17 (score 76, +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.

### 2026-11-15 (score 75, +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.

### 2026-11-14 (score 74, 0)

- [cosmetic] “record_work” added an optional parameter “from_app”

### 2026-11-13 (score 74, +1)

- [functional improvement] 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

### 2026-11-12 (score 73)

First indexed and scored.

## MCP tools (11)

### `record_work` (~275 tokens)

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.

Input parameters:

- `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, required): 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, required): A short human summary of what you built or changed this session (1-3 sentences). No secrets.

### `log_update` (~263 tokens)

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.

Input parameters:

- `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, required): 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.

### `get_brief` (~168 tokens)

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.

Input parameters:

- `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…

### `list_drafts` (~150 tokens)

The latest post drafts FoxPlug wrote for the founder (channel, status, text). Read-only; nothing is posted or changed.

Input parameters:

- `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…

### `simulate_buyers` (~288 tokens)

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.

Input parameters:

- `change` (string, required): 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…

### `set_plan` (~232 tokens)

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.

Input parameters:

- `horizon` (string): Optional. The time frame this plan covers (e.g. 'this week', 'this sprint').
- `plan` (string, required): The current plan, intent, or priorities for this project, in 1 to 5 sentences. No secrets.
- `project` (string, required): 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…

### `check_drift` (~167 tokens)

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.

Input parameters:

- `project` (string, required): 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…

### `get_plan_status` (~164 tokens)

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.

Input parameters:

- `project` (string, required): 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…

### `what_nobody_knows` (~170 tokens)

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.

Input parameters:

- `days` (integer): How far back to look. Defaults to 30.
- `project` (string, required): 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…

### `recall` (~172 tokens)

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.

Input parameters:

- `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…

### `supersede_fact` (~115 tokens)

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.

Input parameters:

- `fact_id` (string, required): The id of the fact, from recall.
- `reason` (string, required): Why it is no longer true. Required.
- `replacement_fact_id` (string): Optional. The fact that replaced it.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/osakasaul-foxplug/foxplug#diagnostics

## Score history

- 2026-11-22: 78
- 2026-11-21: 78
- 2026-11-20: 77
- 2026-11-19: 77
- 2026-11-18: 76
- 2026-11-17: 76
- 2026-11-16: 75
- 2026-11-15: 75
- 2026-11-14: 74
- 2026-11-13: 74
- 2026-11-12: 73

## Common questions

### 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.

## Links

- Remote endpoint: https://foxplug.com/mcp
- Authorisation metadata: https://foxplug.com/.well-known/oauth-protected-resource/mcp
- Website: https://foxplug.com/
- Changelog RSS feed: https://verifymcp.io/servers/osakasaul-foxplug/foxplug.xml
- Changelog JSON feed: https://verifymcp.io/servers/osakasaul-foxplug/foxplug/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/osakasaul-foxplug/foxplug.json
- HTML version of this page: https://verifymcp.io/servers/osakasaul-foxplug/foxplug
