765T Flow
REMOTE · 765TFLOW.COM
AI for Revit: 450+ tools, 1 undo step. Windows, Revit 2024–2027 (2021–2023 included). Free account.
Available components
Last scanned (18 hours ago)
Scores higher than 26% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Design and Media
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 Security92
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
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. Claim this server and supply a read-only token to verify it and lift the score.
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.
- 26 Oct 26 +1
- Authorization: partial → pass ▲ security
- 22 Oct 26 −37
- Endpoint reachability: reachable → behind authorisation ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 21 Oct 26 +37
- Transport: unverified → pass ▲ security
- 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. security
- MCP protocol: unverified → fail ▼ functional
- 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 functional
- 13 Oct 26 36
First indexed and scored.
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 4 Nov 2026 · Probed https://765tflow.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=765tflow.com | CN=WE1,O=Google Trust Services,C=US | 21 Oct 2026 | 19 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | fb9c431f2e8a0b930e403e95b2ee2c82 |
| SANs: 765tflow.com, *.765tflow.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 insecure
Validation of 765tflow.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| 765tflow.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer realm="765tflow", resource_metadata="https://765tflow.com/.well-known/oauth-protected-resource?resource=https%3A%2F%2F765tflow.com%2Fmcp"
Bearer realm="765tflow", resource_metadata="https://765tflow.com/.well-known/oauth-protected-resource?resource=https%3A%2F%2F765tflow.com%2Fmcp"| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| www-authenticate | Bearer realm="765tflow", resource_metadata="https://765tflow.com/.well-known/oauth-protected-resource?resource=https%3A%2F%2F765tflow.com%2Fmcp" |
Protected resource metadata
| Document | https://765tflow.com/.well-known/oauth-protected-resource?resource=https%3A%2F%2F765tflow.com%2Fmcp |
|---|---|
| Retrieved | Yes |
| Resource | https://765tflow.com/mcp |
| Authorisation server | https://765tflow.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://765tflow.com/mcp | Auth required | 401 | |
| http (plaintext) | http://765tflow.com/mcp | HTTPS enforced | 301 | https://765tflow.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 →
flow_call Run a catalog tool ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| arguments | object | yes | The tool's own advertised arguments plus the reserved call members |
| tool | string | yes | The exact catalog tool name (a hub tool name is refused) |
No output schema declared.
No examples provided.
flow_find Find a tool or guide ~232
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.
| Name | Type | Req | Description |
|---|---|---|---|
| kinds | array | – | – |
| limit | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
flow_get Read a guide ~55
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ref | string | yes | – |
No output schema declared.
No examples provided.
flow_list_instances List Revit instances ~73
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).
| Name | Type | Req | Description |
|---|---|---|---|
| part | integer | – | – |
| textSha256 | string | – | – |
No output schema declared.
No examples provided.
flow_read_result Read result part ~81
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.
| Name | Type | Req | Description |
|---|---|---|---|
| callId | string | yes | – |
| part | integer | yes | – |
| textSha256 | string | yes | – |
No output schema declared.
No examples provided.
flow_report_issue Report an issue ~155
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | object | – | Optional typed context for triage — the closed member set below; no free-form fields. |
| kind | string | yes | bug | feedback | feature |
| message | string | yes | The report text — what happened, or what you suggest. Never project data, model content, file paths or secrets. |
No output schema declared.
No examples provided.
flow_tools Browse tool catalog ~122
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.
| Name | Type | Req | Description |
|---|---|---|---|
| group | string | – | A group id from the no-argument answer |
| part | integer | – | – |
| textSha256 | string | – | – |
| tool | string | – | An exact tool name |
No output schema declared.
No examples provided.
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.
remote · 765tflow.com
claude mcp add --transport http com-765tflow-flow 'https://765tflow.com/mcp'
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.