F

Flowlines

ai.flowlines/flowlines · v2.0.0 · MCP server

by ai.flowlinesScan grade: GoodOfficial MCP registry · source scanned

MCP observability: analyse MCP server usage, investigate sessions, and instrument MCP servers.

Protect this install with HOL Guard

Guard checks the skills and MCP servers a plugin adds on your machine and asks you before a risky action runs. The scores above are free, and no plan changes them.

Is Flowlines a fit?

From the plugin's manifest and HOL's scan. Anything the plugin does not declare is shown as not declared.

Works with

  • MCP
  • 1 MCP server

Before you install

Sign-in
Not declared
Declared access
Not declared
License
Not declared

Check before relying on it

  • Some security checks did not finish: Cisco skill scan and Cisco MCP scan. See the evidence
  • The publisher has not verified ownership on HOL.
  • No license declared in the manifest.

What is Flowlines?

Flowlines is a published mcp server plugin for AI coding agents in the MCP ecosystem, developed by ai.flowlines and distributed through the HOL AI plugin registry. MCP observability: analyse MCP server usage, investigate sessions, and instrument MCP servers.

Canonical slug
ai.flowlines/flowlines
Version
v2.0.0 · updated Oct 29, 2026

Registry snapshot

Owner verification
Not verified
Scanner
HOL plugin scanner
Security result
Needs review
Digest verified
No

Trust and security

Provenance

Plugin root
.
Source repo
https://github.com/flowlines-ai/plugins
Source commit
dc803febecbf…
Publisher verified
No
Owner verified
Not owner verified
Needs review
Security result
87
Security score
0
High findings
Provider
codex-plugin-scanner
Grade
B · Good
Version
3.24.2
codex:hol-plugin-scanner-wmunS6 / flowlines / cisco-skill-scanner: failedcodex:hol-plugin-scanner-wmunS6 / flowlines / cisco-mcp-scanner: unavailable

[claude:.] Claude Plugin

22/22

5 checks

[claude:.] Security

13/16

6 checks

[claude:.] Operational Security

14/17

5 checks

[claude:.] Code Quality

10/10

2 checks

[claude:plugins/flowlines] Claude Plugin

18/18

5 checks

[claude:plugins/flowlines] Security

18/24

6 checks

[claude:plugins/flowlines] Operational Security

N/A

5 checks · not applicable

[claude:plugins/flowlines] Code Quality

10/10

2 checks

[codex:.] Repository Marketplace

15/15

3 checks

[codex:.] Repository Operational Security

14/17

5 checks

[codex:.] flowlines · Manifest Validation

28/31

9 checks

[codex:.] flowlines · Security

18/24

9 checks

[codex:.] flowlines · Best Practices

9/15

5 checks

[codex:.] flowlines · Skill Security

5/5

4 checks

[codex:.] flowlines · Code Quality

10/10

2 checks

Findings

lowsecuritySECURITY_MD_MISSING

Plugins should publish a SECURITY.md file for responsible disclosure and support guidance.

Add a SECURITY.md file with reporting guidance and supported versions.

lowoperational-securityDEPENDABOT_MISSINGReported 2 times

Automation or dependency surfaces exist, but .github/dependabot.yml is missing.

Add Dependabot updates for GitHub Actions and dependency manifests.

lowsecuritySECURITY_MD_MISSINGReported 2 times

Plugins should publish a SECURITY.md file for responsible disclosure and support guidance.

Add a SECURITY.md file with reporting guidance and supported versions.

lowsecurityLICENSE_MISSINGReported 2 times

Plugins should ship a LICENSE file so consumers can review usage rights.

Add a LICENSE file that matches the manifest license metadata.

lowbest-practicesREADME_MISSING

Plugins should document installation, usage, and security expectations in README.md.

Add a README.md that explains setup, usage, and operational constraints.

infomanifest-validationPLUGIN_JSON_INTERFACE_ASSET_COMPOSERICON

The interface field "composerIcon" must use HTTPS or point to a safe in-repo asset.

Update "composerIcon" to use HTTPS or an existing relative asset path.

infomanifest-validationPLUGIN_JSON_INTERFACE_ASSET_LOGO

The interface field "logo" must use HTTPS or point to a safe in-repo asset.

Update "logo" to use HTTPS or an existing relative asset path.

infomanifest-validationPLUGIN_JSON_INTERFACE_ASSET_SCREENSHOTS

The interface field "screenshots" must use HTTPS or point to a safe in-repo asset.

Update "screenshots" to use HTTPS or an existing relative asset path.

infobest-practicesCODEXIGNORE_MISSING

A .codexignore file helps prevent accidental inclusion of local artifacts and secrets.

Add a .codexignore file with generated assets, local state, and secret paths.

Install guidance

Install in MCP

Connect the bundled MCP server shipped in the repository .mcp.json file.

MCP docs
  1. 1

    Clone the repository

    shell
  2. 2

    Register the server in your MCP client

    Claude Code reads a project .mcp.json file and asks you to approve its servers when you open the folder. Other clients keep their own MCP configuration, so copy the server entry from .mcp.json into that client. If this repository configures its server differently, follow the MCP setup the publisher documents.

  3. 3

    Verify the server

    Check the MCP server list in your client. The server declared in .mcp.json should report as connected. In Claude Code, run /mcp to see it.

Did setup work in MCP?

No setup reports for MCP yet. Self-reported by signed-in visitors. Copying a command is not counted, and most installs are never reported.

Attested installs: Fewer than 10 attested installs of this plugin in week 2026-W43, so no number is shown. Counted from opt-in HOL Guard install reports, once per machine and runtime, and never mixed with the answers above. How install reports work.

Loading reviews

Plugin manifest

{
  "source": "official-mcp-registry",
  "evidenceState": "scanned_source",
  "registryName": "ai.flowlines/flowlines",
  "publishedAt": "2026-10-29T11:33:49.169955Z",
  "packages": [],
  "remotes": [
    {
      "type": "streamable-http",
      "url": "https://api.flowlines.ai/mcp"
    }
  ],
  "sourceScannedAt": "2026-10-30T21:12:50.726Z",
  "sourceScanCommit": "dc803febecbfb0f9d12b6319a99181d41dbf6790"
}

File inventory

File inventory is unavailable for this plugin right now.

Flowlines — Frequently asked questions

What is Flowlines?
Flowlines is an AI plugin in the HOL registry. MCP observability: analyse MCP server usage, investigate sessions, and instrument MCP servers.
How do I install Flowlines?
Install Flowlines in your harness: MCP — git clone https://github.com/flowlines-ai/plugins. Full step-by-step guidance is on the HOL plugin page.
How do I install Flowlines in MCP?
To install Flowlines in MCP, start with git clone https://github.com/flowlines-ai/plugins. The complete step-by-step install guide for MCP is on the HOL plugin page.
Who publishes Flowlines?
Flowlines is published by ai.flowlines and listed on HOL.

Directory acceptance

Listed in 0 of 5 directory lists

Read from the list each directory publishes on GitHub. Being listed means the directory accepted the plugin; it is not a HOL security rating.

Lists last read . HOL re-reads them every day.

Submitting it? Check it against each directory's rules

Install signal

HOL cannot see every install. These are separate signals from different sources, so they are not added together. Counts under each floor show as <N.

Install commands issued here
<5
HOL Guard install commands issued from this listing, last 28 days.
Opt-in install reports
<10
Machines that reported installing it through HOL Guard in week 2026-W43. Reporting is opt-in, so most installs are not counted.
HOL Guard workspaces
<5
Workspaces that approved it or include it in an approved-plugin feed, as of today.