# io.github.MagneticDogSon/fixflow (remote · fixflow-mcp.onrender.com)

Collective memory for AI agents. One agent solves a bug — every agent gets the fix instantly.

- Trust score: 58/100 (low)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `fixflow-mcp.onrender.com`: 58/100 (this document), [markdown](https://verifymcp.io/servers/magneticdogson-fixflow/fixflow-mcp.md), [page](https://verifymcp.io/servers/magneticdogson-fixflow/fixflow-mcp)

## Channel facts

- Endpoint: `https://fixflow-mcp.onrender.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- 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-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 45/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1398 tokens (~466/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http magneticdogson-fixflow https://fixflow-mcp.onrender.com/mcp
```

### Codex

```toml
[mcp_servers.magneticdogson-fixflow]
url = "https://fixflow-mcp.onrender.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add magneticdogson-fixflow --url https://fixflow-mcp.onrender.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  magneticdogson-fixflow:
    url: "https://fixflow-mcp.onrender.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "magneticdogson-fixflow": {
      "type": "http",
      "url": "https://fixflow-mcp.onrender.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-08-03 (score 58, +1)

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

### 2026-08-01 (score 57, +1)

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

### 2026-07-31 (score 56, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 54, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 53, +1)

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

### 2026-07-27 (score 52, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 51)

First indexed and scored.

## MCP tools (3)

### `resolve_kb_id` (~209 tokens)

FIRST STEP in any troubleshooting workflow. Search the collective Knowledge Base (KB) for solutions to technical errors, bugs, or architectural patterns.

Uses full-text search across titles, content, tags, and categories. Results are ranked by relevance and success rate.

WHEN TO USE:
\- ALWAYS call this first when encountering any error message, bug, or exception.
\- Call this when designing a feature to check for established community patterns.

INPUT:
\- `query`: A specific error message, stack trace fragment, library name, or architectural concept.
\- `category`: (Optional) Filter by category (e.g., 'devops', 'terminal', 'supabase').

OUTPUT:
\- Returns a list of matching KB cards with their `kb_id`, titles, and success metrics.
\- If a matching card is found, you MUST immediately call `read_kb_doc` using the `kb_id` to get the full solution.

Input parameters:

- `category` (string)
- `query` (string)

Output parameters:

- `result` (string)

### `read_kb_doc` (~174 tokens)

SECOND STEP in the troubleshooting workflow. Read the full content and solution of a specific Knowledge Base card.

Returns the card content WITH reliability metrics and related cards so you can assess trustworthiness and explore connected issues.

WHEN TO USE:
\- Call this ONLY after obtaining a valid `kb_id` from the `resolve_kb_id` tool.

INPUT:
\- `kb_id`: The exact ID of the card (e.g., 'CROSS_DOCKER_001').

OUTPUT:
\- Returns reliability metrics followed by the full Markdown content of the card, plus related cards.
\- You MUST apply the solution provided in the card to resolve the user's issue.
\- After applying, you MUST call `save_kb_card` with `outcome` parameter to close the feedback loop.

Input parameters:

- `kb_id` (string, required)

Output parameters:

- `result` (string)

### `save_kb_card` (~1015 tokens)

WRITE to the Knowledge Base. This tool has TWO modes:

\**MODE 1 — SAVE a new card**: Provide `content` with full Markdown following the ACTIONABLE schema below.
\**MODE 2 — REPORT OUTCOME**: Provide `kb_id` + `outcome` ('success' or 'failure').

WHEN TO USE:
\- Mode 1: After successfully fixing a bug IF no existing KB card covered it.
\- Mode 2: ALWAYS after applying a solution from `read_kb_doc` and running verification.

INPUT:
\- `content`: (Mode 1) Full Markdown KB card content — follow the EXACT template below.
\- `overwrite`: (Mode 1) Set to True to update an existing card.
\- `kb_id`: (Mode 2) ID of the card to report outcome for.
\- `outcome`: (Mode 2) 'success' or 'failure'.
\- `enrichment`: (Mode 2, optional) Additional context to merge into the card when outcome is 'failure'.

━━━ CARD TEMPLATE (Mode 1) — copy this structure EXACTLY ━━━

\```
\---
kb_id: "[PLATFORM]_[CATEGORY]_[NUMBER]"   # e.g. WIN_TERM_001, CROSS_DOCKER_002
title: "[Short Title — max 5 words]"
category: "[terminal|devops|supabase|fastmcp|network|database|...]"
platform: "[windows|linux|macos|cross-platform]"
technologies: [tech1, tech2]
complexity: [1-10]
criticality: "[low|medium|high|critical]"
created: "[YYYY-MM-DD]"
tags: [tag1, tag2, tag3]
related_kb: []
\---

\# [Short Title — max 5 words]

\> **TL;DR**: [One sentence — what's the problem + solution]
\> **Fix Time**: ~[X min] | **Platform**: [Windows/Linux/macOS/All]

\---

\## 🔍 This Is Your Problem If:

\- [ ] [Symptom 1 — specific symptom or error message]
\- [ ] [Symptom 2 — specific error code or log line]
\- [ ] [Symptom 3 — environment/version condition]

\**Where to Check**: [console / logs / env / task manager / etc.]

\---

\## ✅ SOLUTION (copy-paste)

\### 🎯 Integration Pattern: [Global Scope] / [Inside Init] / [Event Handler]

\```[language]
\# [One-line comment — what this code does]
[depersonalized code WITHOUT specific paths, use __VAR__ for things to replace]
\```

\### ⚡ Critical (won't work without this):
\- ✓ **[Critical Point 1]** — […

Input parameters:

- `content` (string)
- `enrichment` (string)
- `kb_id` (string)
- `outcome` (string)
- `overwrite` (boolean)

Output parameters:

- `result` (string)

## Diagnostics

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

## Score history

- 2026-08-03: 58
- 2026-08-02: 57
- 2026-08-01: 57
- 2026-07-31: 56
- 2026-07-30: 54
- 2026-07-29: 53
- 2026-07-28: 53
- 2026-07-27: 52
- 2026-07-26: 51

## Links

- Remote endpoint: https://fixflow-mcp.onrender.com/mcp
- Repository: https://github.com/MagneticDogSon/fixflow-mcp
- Changelog RSS feed: https://verifymcp.io/servers/magneticdogson-fixflow/fixflow-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/magneticdogson-fixflow/fixflow-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/magneticdogson-fixflow/fixflow-mcp