1. Conduid
  2. Blockchain
  3. Incident Flow
MCP server · Blockchain

Incident Flow

Event-driven incident management backend in Go with PostgreSQL, NATS JetStream, durable escalations and read-only MCP

34Low

Scored yesterday · breakdown

About Incident Flow

Incident Flow is an MCP server published by kirpepa in the Blockchain category: event-driven incident management backend in Go with PostgreSQL, NATS JetStream, durable escalations and read-only MCP. It has been installed 0 times through Conduid.

Install

Clone
git clone https://github.com/kirpepa/incident-flow

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

Ask AI about Incident Flow

Powered by Claude · Grounded in docs

I know everything about Incident Flow. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ·README presentNot checked yet.
  • ·License declaredNot checked yet.
  • ·Tests presentNot checked yet.
  • ·Dependencies pinnedNot checked yet.
  • ·No dynamic code executionNot checked yet.
  • ·Scoped permissionsNot checked yet.
Questions

About Incident Flow

How do I install Incident Flow?

Run git clone https://github.com/kirpepa/incident-flow, then add the server to your MCP client's configuration. Conduid has recorded 0 installs, so the command is known to work with current clients.

Is Incident Flow safe to use with an AI agent?

Its trust score is 34 out of 100 (low). Conduid hasn't run static security checks on this repository yet, so review the source yourself before granting it credentials. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Incident Flow still maintained?

Conduid hasn't recorded a commit date for this repository yet. Check the repository directly for recent activity.