# FAHCE Integrity Repair (remote · fahce.kinganlogic.com)

Free FAHCE contract discovery. Paid evidence determinations use wallet-only x402 REST endpoints.

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

## Components

- remote · `fahce.kinganlogic.com`: 85/100 (this document), [markdown](https://verifymcp.io/servers/com-kinganlogic-fahce-integrity-repair/fahce.md), [page](https://verifymcp.io/servers/com-kinganlogic-fahce-integrity-repair/fahce)

## Channel facts

- Endpoint: `https://fahce.kinganlogic.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-11-05.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 79/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 441 tokens (~110/item across 4 items; 4 tools + 0 resources), lean.
  - Tools include usage examples.
- **Stability & Change Management**: 70/100
  - Stability observed for 21 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the FAHCE Integrity Repair MCP server?

FAHCE Integrity Repair is a hosted endpoint at https://fahce.kinganlogic.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 com-kinganlogic-fahce-integrity-repair 'https://fahce.kinganlogic.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-kinganlogic-fahce-integrity-repair": {
      "url": "https://fahce.kinganlogic.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-kinganlogic-fahce-integrity-repair": {
      "type": "http",
      "url": "https://fahce.kinganlogic.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-kinganlogic-fahce-integrity-repair]
url = "https://fahce.kinganlogic.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-kinganlogic-fahce-integrity-repair": {
      "type": "remote",
      "url": "https://fahce.kinganlogic.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-kinganlogic-fahce-integrity-repair --url 'https://fahce.kinganlogic.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-kinganlogic-fahce-integrity-repair:
    url: "https://fahce.kinganlogic.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-kinganlogic-fahce-integrity-repair": {
      "Transport": "http",
      "Url": "https://fahce.kinganlogic.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-kinganlogic-fahce-integrity-repair -t streamable-http -u 'https://fahce.kinganlogic.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-kinganlogic-fahce-integrity-repair": {
      "type": "http",
      "url": "https://fahce.kinganlogic.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-04 (score 85, +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-11-02 (score 84, +1)

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

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

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

### 2026-10-29 (score 82, +2)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “fahce_diagnose_integrity” rewrote its description, which is the text the model reads
- [security] Tool “fahce_integrity_repair_bundle” rewrote its description, which is the text the model reads
- [security] Tool “fahce_plan_bounded_repair” rewrote its description, which is the text the model reads
- [security] Tool “fahce_verify_repaired_output” rewrote its description, which is the text the model reads
- [functional improvement] Schema quality: fail → pass
- [cosmetic] “fahce_diagnose_integrity” reworded the description of “idempotency_key”
- [cosmetic] “fahce_diagnose_integrity” reworded the description of “request”
- [cosmetic] “fahce_integrity_repair_bundle” reworded the description of “idempotency_key”
- [cosmetic] “fahce_integrity_repair_bundle” reworded the description of “request”
- [cosmetic] “fahce_plan_bounded_repair” reworded the description of “idempotency_key”
- [cosmetic] “fahce_plan_bounded_repair” reworded the description of “request”
- [cosmetic] “fahce_verify_repaired_output” reworded the description of “idempotency_key”
- [cosmetic] “fahce_verify_repaired_output” reworded the description of “request”

### 2026-10-28 (score 80, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “fahce_diagnose_integrity” rewrote its description, which is the text the model reads
- [security] Tool “fahce_integrity_repair_bundle” rewrote its description, which is the text the model reads
- [security] Tool “fahce_plan_bounded_repair” rewrote its description, which is the text the model reads
- [security] Tool “fahce_verify_repaired_output” rewrote its description, which is the text the model reads
- [cosmetic] “fahce_diagnose_integrity” reworded the description of “request”
- [cosmetic] “fahce_integrity_repair_bundle” reworded the description of “request”
- [cosmetic] “fahce_plan_bounded_repair” reworded the description of “request”
- [cosmetic] “fahce_verify_repaired_output” reworded the description of “request”

### 2026-10-26 (score 80, +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-24 (score 79, +5)

- [security] Tool “fahce_diagnose_integrity” rewrote its description, which is the text the model reads
- [security] Tool “fahce_integrity_repair_bundle” rewrote its description, which is the text the model reads
- [security] Tool “fahce_plan_bounded_repair” rewrote its description, which is the text the model reads
- [security] Tool “fahce_verify_repaired_output” rewrote its description, which is the text the model reads
- [functional improvement] Schema quality: 246 → 166
- [functional improvement] Schema quality: fail → pass
- [functional] Schema quality: fair → good
- [cosmetic] “fahce_diagnose_integrity” reworded the description of “idempotency_key”
- [cosmetic] “fahce_integrity_repair_bundle” reworded the description of “idempotency_key”
- [cosmetic] “fahce_plan_bounded_repair” reworded the description of “idempotency_key”
- [cosmetic] “fahce_verify_repaired_output” reworded the description of “idempotency_key”

### 2026-10-23 (score 74, +2)

- [security improvement] DNSSEC: fail → pass
- [functional] Server version: 1.4.0 → 1.5.0

## MCP tools (4)

### `fahce_diagnose_integrity` (~98 tokens)

Discover evidence-based claim diagnosis via x402 POST /api/v1/diagnose. Returns findings and a receipt. Example: claimed success versus a failure log.

Input parameters:

- `idempotency_key` (string): REST retry key; reuse only for identical operation, input, and authorization.
- `request` (object, required): REST body only; maximum 524288 UTF-8 bytes for the complete serialized body. Field limits also apply.

Output parameters:

- `attestation` (object)
- `authority` (object)
- `billing` (object)
- `binding` (object)
- `diagnosis` (object)
- `evidence_provenance` (array)
- `execution_state` (object)
- `input_hash` (string)
- `next_safe_action` (object)
- `operation`
- `receipt` (object)
- `repair`
- `request_id` (string): Determination ID; equals receipt.case_id/run_id and identifies the saved receipt. Error request_id is a separate trace.
- `schema`
- `verification` (object)

### `fahce_plan_bounded_repair` (~98 tokens)

Discover correction planning via x402 POST /api/v1/repair. Returns an evidence-preserving proposal and receipt. Example: correct a contradicted success claim.

Input parameters:

- `idempotency_key` (string): REST retry key; reuse only for identical operation, input, and authorization.
- `request` (object, required): REST body only; maximum 524288 UTF-8 bytes for the complete serialized body. Field limits also apply.

Output parameters:

- `attestation` (object)
- `authority` (object)
- `billing` (object)
- `binding` (object)
- `diagnosis` (object)
- `evidence_provenance` (array)
- `execution_state` (object)
- `input_hash` (string)
- `next_safe_action` (object)
- `operation`
- `receipt` (object)
- `repair`
- `request_id` (string): Determination ID; equals receipt.case_id/run_id and identifies the saved receipt. Error request_id is a separate trace.
- `schema`
- `verification` (object)

### `fahce_verify_repaired_output` (~97 tokens)

Discover submitted-answer verification via x402 POST /api/v1/verify. Returns evidence-bounded findings and a receipt. Example: check a revised deployment status.

Input parameters:

- `idempotency_key` (string): REST retry key; reuse only for identical operation, input, and authorization.
- `request` (object, required): REST body only; maximum 524288 UTF-8 bytes for the complete serialized body. Field limits also apply.

Output parameters:

- `attestation` (object)
- `authority` (object)
- `billing` (object)
- `binding` (object)
- `diagnosis` (object)
- `evidence_provenance` (array)
- `execution_state` (object)
- `input_hash` (string)
- `next_safe_action` (object)
- `operation`
- `receipt` (object)
- `repair`
- `request_id` (string): Determination ID; equals receipt.case_id/run_id and identifies the saved receipt. Error request_id is a separate trace.
- `schema`
- `verification` (object)

### `fahce_integrity_repair_bundle` (~100 tokens)

Discover combined diagnosis, proposed correction, and verification via x402 POST /api/v1/repair-bundle. Example: resolve a disputed completion claim. No repair executes.

Input parameters:

- `idempotency_key` (string): REST retry key; reuse only for identical operation, input, and authorization.
- `request` (object, required): REST body only; maximum 524288 UTF-8 bytes for the complete serialized body. Field limits also apply.

Output parameters:

- `attestation` (object)
- `authority` (object)
- `billing` (object)
- `binding` (object)
- `diagnosis` (object)
- `evidence_provenance` (array)
- `execution_state` (object)
- `input_hash` (string)
- `next_safe_action` (object)
- `operation`
- `receipt` (object)
- `repair`
- `request_id` (string): Determination ID; equals receipt.case_id/run_id and identifies the saved receipt. Error request_id is a separate trace.
- `schema`
- `verification` (object)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-kinganlogic-fahce-integrity-repair/fahce#diagnostics

## Score history

- 2026-11-05: 85
- 2026-11-04: 85
- 2026-11-03: 84
- 2026-11-02: 84
- 2026-11-01: 83
- 2026-10-31: 83
- 2026-10-30: 82
- 2026-10-29: 82
- 2026-10-28: 80
- 2026-10-27: 80
- 2026-10-26: 80
- 2026-10-25: 79
- 2026-10-24: 79
- 2026-10-23: 74
- 2026-10-22: 72
- 2026-10-21: 72
- 2026-10-20: 71
- 2026-10-19: 71
- 2026-10-18: 70
- 2026-10-17: 68
- 2026-10-16: 67
- 2026-10-15: 67

## Common questions

### What is the FAHCE Integrity Repair MCP server?

FAHCE Integrity Repair is an MCP server listed in the public MCP registry as com.kinganlogic/fahce-integrity-repair. Free FAHCE contract discovery. Paid evidence determinations use wallet-only x402 REST endpoints. This page covers its hosted endpoint (https://fahce.kinganlogic.com/mcp).

### Is the FAHCE Integrity Repair MCP server safe to use?

FAHCE Integrity Repair scores 85 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 FAHCE Integrity Repair MCP server expose?

FAHCE Integrity Repair exposes 4 tools: fahce_diagnose_integrity, fahce_plan_bounded_repair, fahce_verify_repaired_output, fahce_integrity_repair_bundle. Their descriptions and schemas cost roughly 393 tokens of context every time the server is loaded.

### Does the FAHCE Integrity Repair MCP server require authentication?

No. We connected to FAHCE Integrity Repair without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the FAHCE Integrity Repair MCP server still maintained?

FAHCE Integrity Repair 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 did VerifyMCP test on the FAHCE Integrity Repair MCP server?

VerifyMCP ran 13 checks on FAHCE Integrity Repair, 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://fahce.kinganlogic.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-kinganlogic-fahce-integrity-repair/fahce.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-kinganlogic-fahce-integrity-repair/fahce/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-kinganlogic-fahce-integrity-repair/fahce.json
- HTML version of this page: https://verifymcp.io/servers/com-kinganlogic-fahce-integrity-repair/fahce