A
licenseA
qualityB
maintenanceEnables AI agents to push and read metrics from EzStat, track counters/gauges, and ask natural-language questions about telemetry.
4
66 npm
MIT
mcp-counter-server
by Discordit142
Related Servers
Alternatives to mcp-counter-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceTracks and analyzes AI agent tool calls with event logging, dashboard, per-tool and per-agent analytics, and error monitoring.MIT
- AlicenseNot gradedqualityDmaintenanceProvides tools for AI models to count characters and words in text, supporting English and other space-delimited languages.1MIT
- AlicenseAqualityBmaintenanceLets AI agents query, manage, and operate their LLM observability data directly from the conversation. Provides 87 tools for cost analysis, alerting, anomaly detection, and runtime control gates.87204 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to track LLM costs, enforce budgets, compare models, and estimate expenses through simple tool calls.-
- AlicenseAqualityDmaintenanceProvides state and log management tools designed for long-lived AI agents that may be interrupted and resumed. It enables tracking agent progress and maintaining an append-only event history to ensure continuity across multiple sessions.4MIT
TDQS
A4.1/5.0
Scored across 7 tools
Disambiguation4/5
Tools are mostly distinct: increment, reset, delete, get, list, and history each target a unique operation. However, counter_parse_and_apply can also perform increment, reset, delete, and set actions, creating some overlap with the direct tools, though it is clearly scoped as a text-parsing batch operation.
Naming Consistency5/5
All tools follow a consistent counter_<verb> pattern, using snake_case for multi-word verbs like parse_and_apply. The naming is uniform and predictable, making it easy to infer the tool's function from its name.
Tool Count5/5
With 7 tools, the server is well-scoped for a counter management domain. Each tool serves a distinct operational need without excessive overlap or redundancy, striking a balance between completeness and simplicity.
Completeness4/5
The core counter lifecycle is well covered: create (via increment), read (get/list), update (increment/reset), and delete. However, direct decrement and set-to-arbitrary-value operations are missing, requiring agents to use counter_parse_and_apply with text, which is an awkward workaround for simple cases.
Maintenance
ActivityStale
ResponsivenessNo issues