# 765T Flow (remote · 765tflow.com)

AI for Revit: 450+ tools, 1 undo step. Windows, Revit 2024–2027 (2021–2023 included). Free account.

- Trust score: 37/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- remote · `765tflow.com`: 37/100 (this document), [markdown](https://verifymcp.io/servers/com-765tflow-flow/765tflow.md), [page](https://verifymcp.io/servers/com-765tflow-flow/765tflow)

## Channel facts

- Endpoint: `https://765tflow.com/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.26`

## 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-04.

- **Endpoint Security**: 92/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata.
  - 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.
  - The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism.
- **Transport & Reachability**: 0/100
  - Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- **Schema Quality & AI Usability**: 0/100
  - Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Tool Safety**: 0/100
  - Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Capabilities**: 0/100
  - Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

**Unverified: 6 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the 765T Flow MCP server?

765T Flow is a hosted endpoint at https://765tflow.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-765tflow-flow 'https://765tflow.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-765tflow-flow": {
      "url": "https://765tflow.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-765tflow-flow": {
      "type": "http",
      "url": "https://765tflow.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-765tflow-flow]
url = "https://765tflow.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-765tflow-flow": {
      "type": "remote",
      "url": "https://765tflow.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-765tflow-flow --url 'https://765tflow.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-765tflow-flow:
    url: "https://765tflow.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-765tflow-flow": {
      "Transport": "http",
      "Url": "https://765tflow.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-765tflow-flow -t streamable-http -u 'https://765tflow.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-765tflow-flow": {
      "type": "http",
      "url": "https://765tflow.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-10-26 (score 37, +1)

- [security improvement] Authorization: partial → pass

### 2026-10-22 (score 36, −37)

- [security regression] Endpoint reachability: reachable → behind authorisation
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → unverified
- [security] Authorization: The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata.
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-10-21 (score 73, +37)

- [security improvement] Transport: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Authorization: Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: 100
- [functional] First check of Schema quality: good
- [functional] First check of Tool coverage: 39

### 2026-10-13 (score 36)

First indexed and scored.

## MCP tools (7)

### `flow_list_instances` (~73 tokens)

List Revit instances

List this account's connected Revit instances and their open documents. The instanceId it returns is the reserved member every catalog tools/call requires; documentKey is required on document-scoped tools only (tools/list names each tool's scope).

Input parameters:

- `part` (integer)
- `textSha256` (string)

### `flow_read_result` (~81 tokens)

Read result part

Read one part of a call's tools/call answer — call it exactly the way a parted answer's `next` member names it: {callId, part, textSha256} verbatim. Never form the arguments by hand.

Input parameters:

- `callId` (string, required)
- `part` (integer, required)
- `textSha256` (string, required)

### `flow_report_issue` (~155 tokens)

Report an issue

Report a bug, feedback or a feature request to the 765T Flow team. Call this tool only when the user asks you to report something or agrees a report should be sent — never on your own initiative. The `message` is the report; never include project data, model content, file paths or secrets. The answer returns the `reportId` reference the team tracks the report by.

Input parameters:

- `context` (object): Optional typed context for triage — the closed member set below; no free-form fields.
- `kind` (string, required): bug | feedback | feature
- `message` (string, required): The report text — what happened, or what you suggest. Never project data, model content, file paths or secrets.

### `flow_tools` (~122 tokens)

Browse tool catalog

The 765T Flow catalog door. Call it with no arguments for the tool groups; with {group} for one group's members; with {tool} for one tool's exact input schema (the schema flow_call's arguments for that tool take, reserved members included) with its document scope, dry-run support and credit class. Names are matched exactly.

Input parameters:

- `group` (string): A group id from the no-argument answer
- `part` (integer)
- `textSha256` (string)
- `tool` (string): An exact tool name

### `flow_call` (~125 tokens)

Run a catalog tool

Execute one 765T Flow catalog tool by its exact name. `arguments` is exactly the arguments a direct call to that tool carries — the advertised input schema flow_tools answers for it, including the reserved members (instanceId always; documentKey where the tool is document-scoped; optional idempotencyKey and dryRun). Read the schema with flow_tools first; names never resolve by similarity.

Input parameters:

- `arguments` (object, required): The tool's own advertised arguments plus the reserved call members
- `tool` (string, required): The exact catalog tool name (a hub tool name is refused)

### `flow_find` (~232 tokens)

Find a tool or guide

Find the right 765T Flow tool, or the how-to, for a Revit job. Describe the job in plain words, in English or Vietnamese. The answer ranks tools and short guides; each result lists the tools it leads to. When the catalog has no tool for the job, `answer.kind` is `negative` and `answer.workaround` names the nearest tools and what to do instead. Results are ranked for you to choose from; before you call a tool a result names, read that result with flow_get: a how-to card states what the tool does beyond its schema. `reference` lists up to three sections of curated Revit playbooks on the topic: background to read, ranked by wording only. It never changes `answer.kind`, never lists a tool, and is not proof that the catalog has a tool for the job. Read-only: it never reads or changes a Revit model. Never put project data, model content, file paths or secrets in the query.

Input parameters:

- `kinds` (array)
- `limit` (integer)
- `query` (string, required)

### `flow_get` (~55 tokens)

Read a guide

Read one guide, tool entry or playbook section in full, by the `ref` flow_find returned for it. Pass the ref exactly as returned; never form one by hand. Read-only.

Input parameters:

- `ref` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-765tflow-flow/765tflow#diagnostics

## Score history

- 2026-11-04: 37
- 2026-11-03: 37
- 2026-11-02: 37
- 2026-11-01: 37
- 2026-10-31: 37
- 2026-10-30: 37
- 2026-10-29: 37
- 2026-10-28: 37
- 2026-10-27: 37
- 2026-10-26: 37
- 2026-10-25: 36
- 2026-10-24: 36
- 2026-10-23: 36
- 2026-10-22: 36
- 2026-10-21: 73
- 2026-10-20: 36
- 2026-10-19: 36
- 2026-10-18: 36
- 2026-10-17: 36
- 2026-10-16: 36
- 2026-10-15: 36
- 2026-10-14: 36
- 2026-10-13: 36

## Common questions

### What is the 765T Flow MCP server?

765T Flow is an MCP server listed in the public MCP registry as com.765tflow/flow. AI for Revit: 450+ tools, 1 undo step. Windows, Revit 2024–2027 (2021–2023 included). Free account. This page covers its hosted endpoint (https://765tflow.com/mcp).

### Is the 765T Flow MCP server safe to use?

765T Flow scores 37 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 765T Flow MCP server expose?

765T Flow exposes 7 tools: flow_list_instances, flow_read_result, flow_report_issue, flow_tools, flow_call, and 2 more. Their descriptions and schemas cost roughly 843 tokens of context every time the server is loaded.

### Does the 765T Flow MCP server require authentication?

Yes. 765T Flow asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the 765T Flow MCP server still maintained?

765T Flow is still listed as active in the MCP registry. We last reached this channel on 4 November 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://765tflow.com/mcp
- Website: https://765tflow.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-765tflow-flow/765tflow.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-765tflow-flow/765tflow.json
- HTML version of this page: https://verifymcp.io/servers/com-765tflow-flow/765tflow