# Flowgraf (remote · flowgraf.in)

Create and edit architecture diagrams from your AI agent; get an SVG and a live editable canvas.

- Trust score: 64/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `flowgraf.in`: 64/100 (this document), [markdown](https://verifymcp.io/servers/in-flowgraf-flowgraf/api-mcp.md), [page](https://verifymcp.io/servers/in-flowgraf-flowgraf/api-mcp)
- npm · `flowgraf-mcp`: 29/100, [markdown](https://verifymcp.io/servers/in-flowgraf-flowgraf/flowgraf-mcp.md), [page](https://verifymcp.io/servers/in-flowgraf-flowgraf/flowgraf-mcp)

## Channel facts

- Endpoint: `https://flowgraf.in/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.2`

## 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-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 56/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1586 tokens (~528/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 90/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 71% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http in-flowgraf-flowgraf https://flowgraf.in/api/mcp
```

### Codex

```toml
[mcp_servers.in-flowgraf-flowgraf]
url = "https://flowgraf.in/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "in-flowgraf-flowgraf": {
      "type": "remote",
      "url": "https://flowgraf.in/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add in-flowgraf-flowgraf --url https://flowgraf.in/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  in-flowgraf-flowgraf:
    url: "https://flowgraf.in/api/mcp"
```

### Other

```json
{
  "mcpServers": {
    "in-flowgraf-flowgraf": {
      "type": "http",
      "url": "https://flowgraf.in/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-08-02 (score 64, +1)

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

### 2026-07-31 (score 63, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 61, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 60, +1)

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

### 2026-07-27 (score 59, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 58)

First indexed and scored.

## MCP tools (3)

### `create_diagram` (~791 tokens)

Create architecture diagram

Create a NEW architecture diagram from a graph that YOU author, and get back a shareable, editable canvas URL plus a rendered SVG and Mermaid.

You produce only the SEMANTICS — nodes, the groups (VPC/cluster/...) they live in, and the directed edges between them. You do NOT lay anything out: never send x/y/position/pinned. A deterministic layout engine computes all geometry and an icon layer picks the pictures from each node's kind.

kind.catalog is one of aws | gcp | azure | k8s | saas | generic, each with rich per-catalog kind.types (e.g. aws:lambda, gcp:bigquery, azure:cosmos_db, k8s:deployment, saas:kafka):
\- "aws" (api_gateway, lambda, s3, rds, dynamodb, sqs, bedrock, kinesis, fargate, eventbridge, aurora, ...).
\- "gcp" (compute_engine, gke, cloud_run, cloud_sql, spanner, firestore, bigquery, pubsub, dataflow, vertex_ai, ...).
\- "azure" (virtual_machine, aks, app_service, functions, blob_storage, sql_database, cosmos_db, service_bus, event_hubs, key_vault, ...).
\- "k8s" (pod, deployment, statefulset, daemonset, job, cronjob, service, ingress, configmap, secret, hpa, ...).
\- "saas" for hosted third-parties (redis, postgresql, mysql, mongodb, kafka, stripe, twilio, auth0, github, cloudflare, ...).
\- "generic" primitive when nothing branded fits: service, database, cache, queue, user, external_system, storage, gateway, function, note.
\- "generic" FLOWCHART kinds for processes/flowcharts: process, decision, terminator, data, document, subprocess.
edge.kind is one of: request, response, async_event, data_flow, dependency, network, generic.

WORKED EXAMPLE — a user hitting an API in a VPC that talks to Postgres:
{
  "title": "Web API",
  "domain": "cloud_architecture",
  "graph": {
    "groups": [{ "id": "g_vpc", "label": "VPC", "type": "vpc" }],
    "nodes": [
      { "id": "n_user", "label": "User", "kind": { "catalog": "generic", "type": "user" } },
      { "id": "n_api", "label": "API", "kind": { "catalog": "aws", "type": "api_gateway" }, "parentId": "g_vpc" },…

Input parameters:

- `domain` (string): Optional domain hint (default: generic).
- `graph` (object, required)
- `title` (string, required): A short title for the diagram.

### `edit_diagram` (~722 tokens)

Edit architecture diagram

Apply a list of operations to an EXISTING diagram. The ops re-use this tool's op vocabulary; you author them, we validate + apply + re-layout + re-render.

ALWAYS call get_diagram(diagramId) first: it returns the current ids and the `version`. Pass that version as `baseVersion`. If the diagram changed since you fetched it, you get a STALE_VERSION error telling you the current version — refetch with get_diagram, recompute your ops, and retry.

The operations (each element of `ops`):
\- add_node    { op, node:{ id, label, kind, parentId? } }
\- remove_node { op, id }                       (also drops edges touching the node)
\- update_node { op, id, patch:{ label?, kind?, parentId?, metadata? } }
\- add_edge    { op, edge:{ id, source, target, kind, label?, directed? } }
\- remove_edge { op, id }
\- update_edge { op, id, patch:{ source?, target?, label?, kind?, directed? } }
\- add_group   { op, group:{ id, label, type, parentId? } }
\- remove_group{ op, id }
\- move_to_group { op, nodeId, groupId }        (groupId null un-nests the node)
\- set_layout  { op, patch:{ direction?, spacing? } }
\- insert_between { op, newNode:{ id, label, kind, parentId? }, sourceId, targetId, inKind?, outKind? }

insert_between IS THE KEY OP for "add X between A and B" requests. It splices newNode onto the existing A→B edge: removes that edge, adds the node, and wires A→newNode→B so the connection re-routes through it automatically.

WORKED EXAMPLE — "add a Redis cache between the API and the DB" on the diagram above:
1\) get_diagram(diagramId) → shows nodes n_api, n_db and version 1.
2\) edit_diagram({ diagramId, baseVersion: 1, ops: [
     { "op": "insert_between", "sourceId": "n_api", "targetId": "n_db",
       "newNode": { "id": "n_redis", "label": "Redis", "kind": { "catalog": "saas", "type": "redis" }, "parentId": "g_vpc" },
       "inKind": "request", "outKind": "data_flow" }
   ] })
The API→DB edge is gone and now flows API→Redis→DB. Never send x/y/position — geometry is computed for you.…

Input parameters:

- `baseVersion` (integer, required): The version you are editing against — get it from get_diagram. Stale → STALE_VERSION.
- `diagramId` (string, required): The diagram to edit (from create_diagram or get_diagram).
- `ops` (array, required)

### `get_diagram` (~73 tokens)

Get architecture diagram

Fetch a diagram's raw IR (nodes, groups, edges with their real ids) and its current `version`. Call this before edit_diagram so your ops reference ids that actually exist and you pass the correct baseVersion. Returns { diagram, version }.

Input parameters:

- `diagramId` (string, required): The diagram to fetch.

## Diagnostics

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

## Score history

- 2026-08-03: 64
- 2026-08-02: 64
- 2026-08-01: 63
- 2026-07-31: 63
- 2026-07-30: 61
- 2026-07-29: 60
- 2026-07-28: 60
- 2026-07-27: 59
- 2026-07-26: 58

## Links

- Remote endpoint: https://flowgraf.in/api/mcp
- Changelog RSS feed: https://verifymcp.io/servers/in-flowgraf-flowgraf/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/in-flowgraf-flowgraf/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/in-flowgraf-flowgraf/api-mcp