FAHCE Integrity Repair
REMOTE · FAHCE.KINGANLOGIC.COM
Free FAHCE contract discovery. Paid evidence determinations use wallet-only x402 REST endpoints.
Available components
Last scanned (6 hours ago)
Scores higher than 91% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Testing and QA
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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 441 tokens (~110/item across 4 items; 4 tools + 0 resources), lean.Pass
- Tools include usage examples.Pass
Stability & Change Management70
- Stability observed for 21 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 31 Oct 26 +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.
- 29 Oct 26 +2
- 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 security
- Schema quality: fail → pass ▲ functional
- “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” cosmetic
- 28 Oct 26 0
- 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 security
- “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” cosmetic
- 26 Oct 26 +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.
- 24 Oct 26 +5
- 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 security
- Schema quality: 246 → 166 ▲ functional
- Schema quality: fail → pass ▲ functional
- Schema quality: fair → good functional
- “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” cosmetic
- 23 Oct 26 +2
- DNSSEC: fail → pass ▲ security
- Server version: 1.4.0 → 1.5.0 functional
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 5 Nov 2026 · Probed https://fahce.kinganlogic.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=kinganlogic.com | CN=WE1,O=Google Trust Services,C=US | 11 Sept 2026 | 10 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d183029e28d0ba57137a0c1f15e87cd1 |
| SANs: kinganlogic.com, fahce.kinganlogic.com, *.fahce.kinganlogic.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 secure
Validation of fahce.kinganlogic.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| kinganlogic.com. | present | 2371 | 13 | Verified |
| fahce.kinganlogic.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=86400 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://fahce.kinganlogic.com/mcp | Verified | 200 | |
| http (plaintext) | http://fahce.kinganlogic.com/mcp | HTTPS enforced | 301 | https://fahce.kinganlogic.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 →
fahce_diagnose_integrity ~98
Discover evidence-based claim diagnosis via x402 POST /api/v1/diagnose. Returns findings and a receipt. Example: claimed success versus a failure log.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | – | REST retry key; reuse only for identical operation, input, and authorization. |
| request | object | yes | REST body only; maximum 524288 UTF-8 bytes for the complete serialized body. Field limits also apply. |
| Name | Type | Req | Description |
|---|---|---|---|
| attestation | object | – | – |
| authority | object | – | – |
| billing | object | yes | – |
| binding | object | – | – |
| diagnosis | object | yes | – |
| evidence_provenance | array | – | – |
| execution_state | object | – | – |
| input_hash | string | yes | – |
| next_safe_action | object | yes | – |
| operation | – | yes | – |
| receipt | object | yes | – |
| repair | – | yes | – |
| request_id | string | yes | Determination ID; equals receipt.case_id/run_id and identifies the saved receipt. Error request_id is a separate trace. |
| schema | – | yes | – |
| verification | object | yes | – |
{"request":{"candidate_output":"Deployment completed successfully.","evidence":[{"id":"deployment_log","kind":"log","source_label":"caller-supplied deployment log","text":"Deployment failed."}],"schema":"FAHCE_MACHINE_REQUEST_V1"}}fahce_integrity_repair_bundle ~100
Discover combined diagnosis, proposed correction, and verification via x402 POST /api/v1/repair-bundle. Example: resolve a disputed completion claim. No repair executes.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | – | REST retry key; reuse only for identical operation, input, and authorization. |
| request | object | yes | REST body only; maximum 524288 UTF-8 bytes for the complete serialized body. Field limits also apply. |
| Name | Type | Req | Description |
|---|---|---|---|
| attestation | object | – | – |
| authority | object | – | – |
| billing | object | yes | – |
| binding | object | – | – |
| diagnosis | object | yes | – |
| evidence_provenance | array | – | – |
| execution_state | object | – | – |
| input_hash | string | yes | – |
| next_safe_action | object | yes | – |
| operation | – | yes | – |
| receipt | object | yes | – |
| repair | – | yes | – |
| request_id | string | yes | Determination ID; equals receipt.case_id/run_id and identifies the saved receipt. Error request_id is a separate trace. |
| schema | – | yes | – |
| verification | object | yes | – |
{"request":{"candidate_output":"Deployment completed successfully.","evidence":[{"id":"deployment_log","kind":"log","source_label":"caller-supplied deployment log","text":"Deployment failed."}],"schema":"FAHCE_MACHINE_REQUEST_V1"}}fahce_plan_bounded_repair ~98
Discover correction planning via x402 POST /api/v1/repair. Returns an evidence-preserving proposal and receipt. Example: correct a contradicted success claim.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | – | REST retry key; reuse only for identical operation, input, and authorization. |
| request | object | yes | REST body only; maximum 524288 UTF-8 bytes for the complete serialized body. Field limits also apply. |
| Name | Type | Req | Description |
|---|---|---|---|
| attestation | object | – | – |
| authority | object | – | – |
| billing | object | yes | – |
| binding | object | – | – |
| diagnosis | object | yes | – |
| evidence_provenance | array | – | – |
| execution_state | object | – | – |
| input_hash | string | yes | – |
| next_safe_action | object | yes | – |
| operation | – | yes | – |
| receipt | object | yes | – |
| repair | – | yes | – |
| request_id | string | yes | Determination ID; equals receipt.case_id/run_id and identifies the saved receipt. Error request_id is a separate trace. |
| schema | – | yes | – |
| verification | object | yes | – |
{"request":{"candidate_output":"Deployment completed successfully.","evidence":[{"id":"deployment_log","kind":"log","source_label":"caller-supplied deployment log","text":"Deployment failed."}],"schema":"FAHCE_MACHINE_REQUEST_V1"}}fahce_verify_repaired_output ~97
Discover submitted-answer verification via x402 POST /api/v1/verify. Returns evidence-bounded findings and a receipt. Example: check a revised deployment status.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | – | REST retry key; reuse only for identical operation, input, and authorization. |
| request | object | yes | REST body only; maximum 524288 UTF-8 bytes for the complete serialized body. Field limits also apply. |
| Name | Type | Req | Description |
|---|---|---|---|
| attestation | object | – | – |
| authority | object | – | – |
| billing | object | yes | – |
| binding | object | – | – |
| diagnosis | object | yes | – |
| evidence_provenance | array | – | – |
| execution_state | object | – | – |
| input_hash | string | yes | – |
| next_safe_action | object | yes | – |
| operation | – | yes | – |
| receipt | object | yes | – |
| repair | – | yes | – |
| request_id | string | yes | Determination ID; equals receipt.case_id/run_id and identifies the saved receipt. Error request_id is a separate trace. |
| schema | – | yes | – |
| verification | object | yes | – |
{"request":{"candidate_output":"Deployment failed.","evidence":[{"id":"deployment_log","kind":"log","source_label":"caller-supplied deployment log","text":"Deployment failed."}],"schema":"FAHCE_MACHINE_REQUEST_V1"}}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.
remote · fahce.kinganlogic.com
claude mcp add --transport http com-kinganlogic-fahce-integrity-repair 'https://fahce.kinganlogic.com/mcp'
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.