A
licenseA
qualityA
maintenanceEnables MCP-compatible agent hosts to interact with TypeSafe AI's Jev System One API through dependency-free STDIO tools for classification, scoring, verification, gating, routing, review, and health checks.
9
MIT
smart-glitchtip-mcp
by AndreyBegma
Related Servers
Alternatives to smart-glitchtip-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceStart, observe, and interact with Claude Managed Agents from any MCP client — launch an agent, watch its events, reply, approve the tools it wants to run, and stop it. Runs over stdio, HTTP, or AWS Lambda with pluggable auth.171MIT
- FlicenseAqualityDmaintenanceBridges Hermes Agent to the Hermes Intelligence Platform API, enabling tools to read/write learning loop data (context, feedback, signals, memory, etc.) via stdio.12-
GenieOS MCP Serverofficial
AlicenseAqualityCmaintenanceStdio bridge for editors to connect to the GenieOS MCP server, enabling AI agents to interact with GenieOS via Streamable HTTP transport.6416 npmMIT- AlicenseNot gradedqualityBmaintenanceEnables agents to create and update issues, post comments, and manage docs in a self-hosted issue tracker, with changes visible live in the web UI.13 npmMIT
- FlicenseAqualityBmaintenanceEnables AI agents to interact with issue, comment, document, and agent workflows through a simplified HTTP API, returning compact Markdown or file-based snapshots.16-
TDQS
A4.2/5.0
Scored across 4 tools
Disambiguation5/5
Each tool targets a distinct concern: whoami handles identity/permissions, list_organizations provides an overview, get_organization drills into a single org's details, and list_organization_environments focuses on a specific attribute. There is no meaningful overlap or ambiguity between them.
Naming Consistency5/5
All tools use snake_case and follow a clear verb_noun pattern (list_*, get_*). whoami is a standard, recognizable exception that still fits the command-style naming. The convention is consistent and predictable.
Tool Count5/5
With only 4 tools, the server is tightly scoped to read-only organization exploration. Each tool adds distinct value without bloat, and the count is well within the ideal range for a focused MCP server.
Completeness4/5
The surface covers the essential read paths: identity check, list organizations, retrieve a single organization, and list environments. Missing mutation (create/update/delete) and deeper project/team detail tools, but the server appears intentionally read-only for this niche. Minor gaps exist but agents can complete basic workflows.
Maintenance
ActivityMaintained
ResponsivenessUnresponsive