Home / MCP registry index / io.roadflow/roadflow

Roadflow

io.roadflow/roadflow in the official MCP registry. Endpoint https://roadflow.io/mcp.

The registry describes it as: Create and edit roadmaps with JSON or markup; share edit and view links from AI agents.

We read its 43 tools on 2026-10-30. Nothing in them matched our tool-poisoning rules.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http roadflow https://roadflow.io/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "roadflow": {
      "url": "https://roadflow.io/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"roadflow","type":"http","url":"https://roadflow.io/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

roadflow_new roadflow_status roadflow_get roadflow_apply_json roadflow_apply_markup roadflow_open_shared roadflow_create_shared roadflow_export_json roadflow_export_markup roadflow_export_csv roadflow_list_versions roadflow_get_version roadflow_discard artifacts_new artifacts_status artifacts_get artifacts_apply_json artifacts_open_shared artifacts_create_shared artifacts_export_json artifacts_list_versions artifacts_get_version artifacts_discard model_new model_open model_status model_get model_discard model_patch_project model_list_parameters model_get_parameter model_upsert_parameter model_upsert_parameters model_delete_parameter model_list_observations model_upsert_observation model_upsert_observations model_delete_observation model_list_edges model_upsert_edge model_delete_edge model_evaluate model_list_dictionaries

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-10-30): a9862660c4b28fd0. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-roadflow-roadflow/badge.svg)](https://lazaretto.dev/mcp-registry/io-roadflow-roadflow)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.