Is the Ninihen1 Flowstudio MCP server down?

mcp-registry/io.github.ninihen1/flowstudio-mcp · v1.3.126

As of 2026-10-17 05:51 UTC, the Ninihen1 Flowstudio MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 4 outages in 90 days, with a median recovery of 3 minutes.

Debug, build, and manage Power Automate cloud flows with AI agents

claude mcp add --transport http ninihen1-flowstudio-mcp-server https://mcp.flowstudio.app/mcp

{
  "mcpServers": {
    "ninihen1-flowstudio-mcp-server": {
      "type": "http",
      "url": "https://mcp.flowstudio.app/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (83/100)

What to fix (6)

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.ninihen1/flowstudio-mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.ninihen1/flowstudio-mcp"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• Every tool declares whether it is read-only or destructive.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Tool names are unique and portable across clients.
• 99.97% uptime over 30 days.

Largest tool definitions

• update_live_flow ~1,215 tokens
• resolve_live_parameters ~648 tokens
• describe_live_connector ~578 tokens
• get_live_flow_run_action_outputs ~558 tokens
• list_live_flows ~484 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.ninihen1%2Fflowstudio-mcp.svg)](https://glimind.com/server/mcp-registry%2Fio.github.ninihen1%2Fflowstudio-mcp?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fio.github.ninihen1%2Fflowstudio-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.ninihen1%2Fflowstudio-mcp.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.ninihen1%2Fflowstudio-mcp.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.ninihen1%2Fflowstudio-mcp?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:aa864c4ae7c7a662…, first seen 2026-10-17, included at leaf 11309 of 16,986. Version history · verify what your client received.

Tools (30)

• add_live_flow_to_solution
• cancel_live_flow_run
• create_live_connection
• describe_live_connector
• get_live_flow
• get_live_flow_run_action_outputs
• get_live_flow_run_error
• get_live_flow_runs
• get_store_flow
• get_store_flow_runs
• get_store_flow_summary
• get_store_maker
• list_live_connections
• list_live_environments
• list_live_flows
• list_skills
• list_store_connections
• list_store_environments
• list_store_flows
• list_store_makers
• list_store_power_apps
• report_bug
• resolve_live_parameters
• resubmit_live_flow_run
• set_live_flow_state
• test_live_connection
• tool_search
• trigger_live_flow
• update_live_flow
• update_store_flow

Compare: most reliable devops servers · most reliable other servers · most reliable knowledge servers · most reliable data servers · most reliable productivity servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Ninihen1 Flowstudio MCP server down right now?

As of 2026-10-17 05:51 UTC, the Ninihen1 Flowstudio MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 4 outages in 90 days, with a median recovery of 3 minutes.

How many tools does Ninihen1 Flowstudio MCP server provide?

Ninihen1 Flowstudio MCP server advertises 30 tools, including add_live_flow_to_solution, cancel_live_flow_run, create_live_connection, describe_live_connector, get_live_flow.

How do I install Ninihen1 Flowstudio MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.flowstudio.app/mcp

Is the Ninihen1 Flowstudio MCP server safe to connect to an AI agent?

Glimind scanned all 30 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Ninihen1 Flowstudio MCP server?

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.