A
licenseNot graded
qualityA
maintenanceAn MCP server that gives AI agents observability over their own tool calls, enabling auditing, cost tracking, latency analysis, and alerting.
MIT
runmeter
Related Servers
Alternatives to runmeter
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceA MCP server for tracking AI usage metrics and structured logs across applications. Monitor model calls, analyze usage patterns, track costs, and debug AI interactions.59 npmMIT
- AlicenseAqualityAmaintenanceAn MCP server that records agent execution metrics and exposes a Context Window Explorer to visualize exactly what entered the model's context window across sessions, tokens, and tool calls.83MIT
- AlicenseAqualityBmaintenanceMCP server for AI agent observability, providing trace and span logging, search, latency/tokens/cost metrics, and anomaly detection using an in-memory buffer.631 npmMIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server for comprehensive monitoring and observability of systems using Langfuse.1MIT
- AlicenseAqualityCmaintenanceMCP server for measuring, tracking, scoring, and improving AI agent reliability with tools for recording interactions, scoring reliability, analyzing failures, recommending improvements, generating audit reports, and checking MCP health.8MIT
TDQS
A4.4/5.0
Scored across 6 tools
Disambiguation5/5
Each tool targets a distinct operation: recording, retrieving a single run, listing with filters, aggregating summaries, exporting, and deleting. There is no overlap in purpose, making tool selection unambiguous.
Naming Consistency5/5
All tool names follow the pattern 'runmeter_' + verb (get, summary, record, list, export, delete). The consistent prefix and verb-based naming make the toolset predictable and easy to navigate.
Tool Count5/5
Six tools is well within the ideal 3-15 range and perfectly scoped for a telemetry server. Each tool earns its place, covering core operations without unnecessary bloat.
Completeness5/5
The toolset covers the full lifecycle of LLM/agent run telemetry: record, retrieve, list, analyze, export, and delete. There are no obvious missing operations for the domain, and the single-run delete with confirmation prevents accidental data loss.
Maintenance
ActivityActive
ResponsivenessNo issues