# io.github.firmalemony/fizlog-mcp (npm · fizlog-mcp)

Publish changelog entries to Fizlog (in-app widget, public page, RSS) from any MCP client.

- Trust score: 80/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `fizlog-mcp`: 80/100 (this document), [markdown](https://verifymcp.io/servers/firmalemony-fizlog-mcp/fizlog-mcp.md), [page](https://verifymcp.io/servers/firmalemony-fizlog-mcp/fizlog-mcp)

## Channel facts

- Registry: `npm`
- Package: `fizlog-mcp`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-05.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 30 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 277 tokens (~138/item across 2 items; 2 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 96/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 88% 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.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.firmalemony/fizlog-mcp server?

io.github.firmalemony/fizlog-mcp runs locally as an npm package, launched with npx -y fizlog-mcp. 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 firmalemony-fizlog-mcp -- npx -y fizlog-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "firmalemony-fizlog-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "fizlog-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "firmalemony-fizlog-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "fizlog-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add firmalemony-fizlog-mcp -- npx -y fizlog-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "firmalemony-fizlog-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "fizlog-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add firmalemony-fizlog-mcp --command npx --arg -y --arg fizlog-mcp
```

### Hermes

```yaml
mcp_servers:
  firmalemony-fizlog-mcp:
    command: "npx"
    args: ["-y", "fizlog-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "firmalemony-fizlog-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "fizlog-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add firmalemony-fizlog-mcp -t stdio -c npx -a -y fizlog-mcp
```

### Other

```json
{
  "mcpServers": {
    "firmalemony-fizlog-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "fizlog-mcp"
      ]
    }
  }
}
```

## 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-05 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-23 (score 74, +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-10-22 (score 73, +3)

- [functional improvement] Stability: unverified → 0.27

## MCP tools (2)

### `publish_entry` (~204 tokens)

Publish changelog entry

Publish a new entry to the project's Fizlog changelog (in-app widget, public page and RSS). Use it after shipping a feature or fix. Write for end users, not developers: a short benefit-focused title and 1–3 sentences of Markdown (**bold**, *italic*, `code`, [links](url), '- ' lists). Set draft=true to save without publishing, or published_at to schedule.

Input parameters:

- `body` (string): Details in Fizlog's Markdown subset.
- `draft` (boolean): Save as an unpublished draft instead of publishing.
- `notify_subscribers` (boolean): Also email the project's subscribers (only for immediate, non-draft entries).
- `published_at` (string): ISO 8601 date-time. A future value schedules the entry.
- `title` (string, required): Short, user-facing headline, e.g. 'Dark mode is here'.
- `type` (string): new = feature, improved = enhancement, fixed = bug fix.

### `get_public_changelog` (~73 tokens)

Read public changelog

Read the latest published entries of a Fizlog project by its public key (the key in the embed snippet / public page URL). Useful to avoid duplicate announcements or to summarize recent releases.

Input parameters:

- `limit` (integer)
- `public_key` (string): Project public key. Defaults to FIZLOG_PUBLIC_KEY.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/firmalemony-fizlog-mcp/fizlog-mcp#diagnostics

## Score history

- 2026-11-05: 80
- 2026-11-04: 79
- 2026-11-03: 79
- 2026-11-02: 78
- 2026-11-01: 78
- 2026-10-31: 78
- 2026-10-30: 77
- 2026-10-29: 77
- 2026-10-28: 76
- 2026-10-27: 76
- 2026-10-26: 75
- 2026-10-25: 75
- 2026-10-24: 74
- 2026-10-23: 74
- 2026-10-22: 73
- 2026-10-21: 70
- 2026-10-20: 70
- 2026-10-19: 70
- 2026-10-18: 70
- 2026-10-17: 70
- 2026-10-16: 70
- 2026-10-15: 70
- 2026-10-14: 70
- 2026-10-13: 38
- 2026-10-12: 38
- 2026-10-11: 23
- 2026-10-07: 38

## Common questions

### What is the io.github.firmalemony/fizlog-mcp server?

io.github.firmalemony/fizlog-mcp is listed in the public MCP registry as io.github.firmalemony/fizlog-mcp. Publish changelog entries to Fizlog (in-app widget, public page, RSS) from any MCP client. This page covers its npm package (fizlog-mcp).

### Is the io.github.firmalemony/fizlog-mcp server safe to use?

io.github.firmalemony/fizlog-mcp scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 io.github.firmalemony/fizlog-mcp server expose?

io.github.firmalemony/fizlog-mcp exposes 2 tools: publish_entry, get_public_changelog. Their descriptions and schemas cost roughly 277 tokens of context every time the server is loaded.

### Is the io.github.firmalemony/fizlog-mcp server still maintained?

io.github.firmalemony/fizlog-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the io.github.firmalemony/fizlog-mcp server under?

io.github.firmalemony/fizlog-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/fizlog-mcp
- Socket report: https://socket.dev/npm/package/fizlog-mcp
- Repository: https://github.com/firmalemony/fizlog-mcp
- Changelog RSS feed: https://verifymcp.io/servers/firmalemony-fizlog-mcp/fizlog-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/firmalemony-fizlog-mcp/fizlog-mcp.json
- HTML version of this page: https://verifymcp.io/servers/firmalemony-fizlog-mcp/fizlog-mcp