1. Conduid
  2. Communication
  3. Dashboard
MCP server · Communication

Dashboard

The MCP Dashboard is a comprehensive management and monitoring interface for multiple Model Context Protocol (MCP) servers. Built on the foundation of MCP Inspector, it provides enhanced capabilities for connecting to, managing, and monitoring multiple MCP servers simultaneously with real-time updates and analytics.

34Low

Scored 10 hours ago · breakdown

About Dashboard

Dashboard is an MCP server published by bryankthompson in the Communication category: the MCP Dashboard is a comprehensive management and monitoring interface for multiple Model Context Protocol (MCP) servers. Built on the foundation of MCP Inspector, it provides enhanced capabilities for connecting to, managing, and monitoring multiple MCP servers simultaneously with real-time updates and analytics.

The repository has 4 stars and 0 forks, with the last commit a year ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.

Install

From source
git clone https://github.com/bryankthompson/mcp-dashboard

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 Dashboard

Powered by Claude · Grounded in docs

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

Security checks

6 checks have not been run yet.

Questions

About Dashboard

How do I install Dashboard?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is Dashboard 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 Dashboard still maintained?

The last commit was a year ago. That's long enough that you should check whether the maintainer is responding to issues before depending on it.