# Fify (remote · fify-chatgpt.renfei1992.chatgpt.site)

Turn grounded AI answers into trusted comparisons, plans, timelines, and decision views.

- Trust score: 74/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `fify-chatgpt.renfei1992.chatgpt.site`: 74/100 (this document), [markdown](https://verifymcp.io/servers/renfei-design-fify/api-mcp.md), [page](https://verifymcp.io/servers/renfei-design-fify/api-mcp)

## Channel facts

- Endpoint: `https://fify-chatgpt.renfei1992.chatgpt.site/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.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-09-20.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - 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**: 33/100
  - 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 294 tokens (~49/item across 6 items; 2 tools + 4 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 87/100
  - Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 74/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 8% 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 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.
  - Supports UI / widget rendering.

## Install

### How do I install the Fify MCP server?

Fify is a hosted endpoint at https://fify-chatgpt.renfei1992.chatgpt.site/api/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 renfei-design-fify 'https://fify-chatgpt.renfei1992.chatgpt.site/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "renfei-design-fify": {
      "url": "https://fify-chatgpt.renfei1992.chatgpt.site/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "renfei-design-fify": {
      "type": "http",
      "url": "https://fify-chatgpt.renfei1992.chatgpt.site/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.renfei-design-fify]
url = "https://fify-chatgpt.renfei1992.chatgpt.site/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "renfei-design-fify": {
      "type": "remote",
      "url": "https://fify-chatgpt.renfei1992.chatgpt.site/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add renfei-design-fify --url 'https://fify-chatgpt.renfei1992.chatgpt.site/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  renfei-design-fify:
    url: "https://fify-chatgpt.renfei1992.chatgpt.site/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "renfei-design-fify": {
      "Transport": "http",
      "Url": "https://fify-chatgpt.renfei1992.chatgpt.site/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add renfei-design-fify -t streamable-http -u 'https://fify-chatgpt.renfei1992.chatgpt.site/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "renfei-design-fify": {
      "type": "http",
      "url": "https://fify-chatgpt.renfei1992.chatgpt.site/api/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-09-20 (score 74, +1)

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

### 2026-09-18 (score 73, +1)

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

### 2026-09-16 (score 72, +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-09-14 (score 71, +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-09-12 (score 70, +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-09-10 (score 69, +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-09-08 (score 68, +1)

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

### 2026-09-05 (score 67, +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.

## MCP tools (2)

### `render_information_ui` (~216 tokens)

Render information as an interactive view

Render a fully grounded answer as a non-consequential interactive information view when structure or interaction materially improves it. Complete factual reasoning first and always pass the authoritative plain answer. If the user supplied sufficient facts, use them directly and invoke immediately without extra retrieval. For a named real-person profile, set profileSubject to the canonical name unless the user requests no image; Fify will perform a bounded trusted Wikimedia portrait lookup. Pre-resolved attributed Wikimedia or Openverse media may also be supplied, but never invent or guess media URLs.

Input parameters:

- `continuationState` (object)
- `groundedAnswer` (string, required)
- `locale` (string, required)
- `media` (array)
- `originalRequest` (string, required)
- `profileSubject` (string): Canonical person name for a real-person profile. Omit when the user requests no image or the subject is not a person.
- `sections` (array, required)
- `sources` (array, required)
- `suggestedRefinements` (array, required)
- `version` (string, required)

Output parameters:

- `fallbackText` (string)
- `frames` (array)
- `lastSequence` (number)
- `runId` (string)
- `state` (string)

### `read_information_ui_run` (~38 tokens)

Read an information UI run

App-only unseen-frame reader for the mounted Fify widget.

Input parameters:

- `afterSequence` (integer, required)
- `runId` (string, required)

Output parameters:

- `frames` (array)
- `lastSequence` (number)
- `runId` (string)
- `state` (string)

## Diagnostics

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

## Score history

- 2026-09-20: 74
- 2026-09-19: 73
- 2026-09-18: 73
- 2026-09-17: 72
- 2026-09-16: 72
- 2026-09-15: 71
- 2026-09-14: 71
- 2026-09-13: 70
- 2026-09-12: 70
- 2026-09-11: 69
- 2026-09-10: 69
- 2026-09-09: 68
- 2026-09-08: 68
- 2026-09-07: 67
- 2026-09-06: 67
- 2026-09-05: 67
- 2026-09-04: 66
- 2026-09-03: 66
- 2026-09-02: 65
- 2026-09-01: 65
- 2026-08-31: 64
- 2026-08-30: 64
- 2026-08-29: 63
- 2026-08-28: 63
- 2026-08-27: 62
- 2026-08-26: 62
- 2026-08-25: 59

## Common questions

### What is the Fify MCP server?

Fify is an MCP server listed in the public MCP registry as io.github.renfei-design/fify. Turn grounded AI answers into trusted comparisons, plans, timelines, and decision views. This page covers its hosted endpoint (https://fify-chatgpt.renfei1992.chatgpt.site/api/mcp).

### Is the Fify MCP server safe to use?

Fify scores 74 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 Fify MCP server expose?

Fify exposes 2 tools: render_information_ui, read_information_ui_run. Their descriptions and schemas cost roughly 254 tokens of context every time the server is loaded.

### Does the Fify MCP server require authentication?

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

### Is the Fify MCP server still maintained?

Fify is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://fify-chatgpt.renfei1992.chatgpt.site/api/mcp
- Repository: https://github.com/renfei-design/fify-plugin
- Changelog RSS feed: https://verifymcp.io/servers/renfei-design-fify/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/renfei-design-fify/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/renfei-design-fify/api-mcp