MCPSpend vs Heimdall Mcp

Side-by-side comparison of two Model Context Protocol servers — install paths, tools, quality signals, and directory engagement so you can pick the right one for Claude, Cursor, and other MCP clients.

Compare
M
MCPSpend
andreisirbu91-lab
📊 Monitoring
Heimdall Mcp
enmanuelmag
📊 Monitoring
SummaryReal-time cost observability for MCP tool calls. Transparent proxy auto-detects every MCP client (Claude Desktop, Cursor, Windsurf, VS Code, Claude Code, Zed, Continue.dev, Cline, Goose) and attributes spend per tool, per project, per end-customer. npx @mcpspend/proxy add install. Free tier 25K calls/month, no card. MIT proxy on npm. EU-hosted, GDPR-ready.Transparent proxy for any MCP server that intercepts all JSON-RPC messages, measures latency, and stores traces in SQLite, PostgreSQL, or MySQL. Exports OpenTelemetry (OTLP) spans to Jaeger, Tempo, or Grafana. Supports stdio, HTTP, and SSE transports. npx @cardor/heimdall-mcp
Quality signal25/100 (Emerging)25/100 (Emerging)
Install pathnpx · highnpx · high
Engagement 2 0 0 1 0 0 11
ToolsNot listed yetNot listed yet
Verified / officialNoNo
Open listingView MCPSpendView Heimdall Mcp
More alternatives to MCPSpendMore alternatives to Heimdall McpMonitoring category

Other servers like MCPSpend