1. Conduid
  2. Analytics
  3. Mcpulse
MCP server · Analytics

Mcpulse

MCPulse - MCP Analytics Platform

Unclaimed last commit 11 months ago aianalyticsclaudemcpmcp-analyticsmcp-clientmcp-server
43Fair

Scored 7 hours ago · breakdown

About Mcpulse

Mcpulse is an MCP server published by sirrobot01 in the Analytics category: mCPulse - MCP Analytics Platform. It has been installed 0 times through Conduid.

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

Install

Install
npx mcp-mcpulse

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 Mcpulse

Powered by Claude · Grounded in docs

I know everything about Mcpulse. 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 permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

Releases

v0.0.1v0.0.1 · 11 Oct 2025Changelog 523fe13cf4ba1df5d34b856435a13d4124b90e41 fix goreleaser 3e4ed226ec43e4a75a97d84220493a9a3ac63a3f chore: setup mcp-mcpulse

README

MCP-MCPulse

An MCP (Model Context Protocol) server that provides tools to query and analyze metrics from your MCPulse analytics platform directly within any MCP-compatible client.

Built using the official github.com/modelcontextprotocol/go-sdk for proper MCP protocol compliance.

Features

  • Official MCP Implementation: Uses the official Go SDK for Model Context Protocol
  • Query Server Metrics: Get overall metrics for any MCP server
  • Tool Statistics: View performance stats for individual tools
  • Error Analysis: Browse recent errors and failures
  • Timeline Data: See how tool performance changes over time
  • Session Tracking: Monitor active and completed sessions
  • Server Discovery: List all tracked MCP servers

Installation

From Source

go build -o mcp-mcpulse .

Using Go Install

go install github.com/sirrobot01/mcp-mcpulse

Configuration

Configure using environment variables:

# MCPulse gRPC endpoint (default: localhost:9090)
export MCPULSE_URL=localhost:9090

# MCPulse API Key for authentication
export MCPULSE_KEY=your-api-key-here

Usage

In Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "mcpulse": {
      "command": "/path/to/mcp-mcpulse",
      "env": {
        "MCPULSE_URL": "localhost:9090",
        "MCPULSE_KEY": "your-api-key-here"
      }
    }
  }
}

Standalone

MCPULSE_URL=localhost:9090 \
MCPULSE_API_KEY=your-key \
./mcp-mcpulse

Available Tools

1. list_servers

List all MCP servers being tracked in MCPulse.

Parameters: None

Example:

Tool: list_servers
Arguments: {}

2. get_server_metrics

Get overall metrics for an MCP server including request counts, success rates, latency percentiles, and active sessions.

Parameters:

  • server_id (required): The ID of the MCP server
  • from (optional): Start time (e.g., "24h", "7d", "2025-01-01") - default: "24h"
  • to (optional): End time (e.g., "now", "2025-01-31") - default: "now"

Example:

Tool: get_server_metrics
Arguments: {
  "server_id": "my-python-server",
  "from": "24h"
}

3. get_tools_stats

Get statistics for all tools on an MCP server, including call counts, success rates, and latency metrics.

Parameters:

  • server_id (required): The ID of the MCP server
  • from (optional): Start time (e.g., "24h", "7d") - default: "24h"
  • limit (optional): Maximum number of tools to return - default: 20

Example:

Tool: get_tools_stats
Arguments: {
  "server_id": "my-python-server",
  "from": "7d",
  "limit": 10
}

4. get_tool_timeline

Get timeline data showing how a specific tool's performance changed over time.

Parameters:

  • server_id (required): The ID of the MCP server
  • tool_name (required): The name of the tool
  • from (optional): Start time (e.g., "24h", "7d") - default: "24h"
  • interval (optional): Time bucket size (e.g., "1h", "5m") - default: "1h"

Example:

Tool: get_tool_timeline
Arguments: {
  "server_id": "my-python-server",
  "tool_name": "search_database",
  "from": "24h",
  "interval": "1h"
}

5. get_errors

Get recent errors for an MCP server, optionally filtered by tool name.

Parameters:

  • server_id (required): The ID of the MCP server
  • from (optional): Start time (e.g., "1h", "24h") - default: "1h"
  • limit (optional): Maximum number of errors to return - default: 10
  • tool_name (optional): Filter errors by specific tool name

Example:

Tool: get_errors
Arguments: {
  "server_id": "my-python-server",
  "from": "1h",
  "limit": 5,
  "tool_name": "search_database"
}

6. get_sessions

Get active or recent sessions for an MCP server.

Parameters:

  • server_id (required): The ID of the MCP server
  • from (optional): Start time (e.g., "1h", "24h") - default: "1h"
  • status (optional): Filter by status: "active", "completed", or empty for all

Example:

Tool: get_sessions
Arguments: {
  "server_id": "my-python-server",
  "status": "active"
}

Example Queries in Claude

Once configured, you can ask Claude questions like:

  • "Show me metrics for my-python-server in the last 24 hours"
  • "What are the top 5 most used tools on my-server?"
  • "Show me recent errors for the search_database tool"
  • "How has the calculate tool's performance changed over the last 7 days?"
  • "List all active sessions on my-server"
  • "What servers are being tracked in MCPulse?"

License

Same as parent MCPulse project.

Contributing

See the main MCPulse contributing guide.

README mirrored from the source repository 7 hours ago. The original is authoritative.

Questions

About Mcpulse

How do I install Mcpulse?

Run npx mcp-mcpulse, 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 Mcpulse safe to use with an AI agent?

Its trust score is 43 out of 100 (fair). It passes 0 of 1 static security checks; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Mcpulse still maintained?

The last commit was 11 months ago, with 0 open issues. That's long enough that you should check whether the maintainer is responding to issues before depending on it.