Skip to main content
Glama
Jubstaaa

hono-telescope

by Jubstaaa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to hono-telescope

  • Axiom by axiomhq

    Axiomofficial

    axiomhq
    A
    license
    Not graded
    quality
    F
    maintenance
    A Model Context Protocol server implementation for Axiom that enables AI agents to query your data using Axiom Processing Language (APL).
    60
    MIT

  • Hono MCP Server

    mattzcarey
    A
    license
    Not graded
    quality
    D
    maintenance
    Exposes Hono API endpoints as Model Context Protocol tools, allowing LLMs to interact with your API routes through a dedicated MCP endpoint. It provides helpers to describe routes and includes a codemode for dynamic API interaction via search and execute tools.
    25 npm
    86
    MIT

  • Sentry

    universal-mcp
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables interaction with Sentry's error tracking and monitoring tools through a unified API, allowing natural language access to Sentry services.
    MIT

Related Servers

  • hono-mcp-server

    ninjacazul
    A
    license
    Not graded
    quality
    C
    maintenance
    Easily expose your Hono API endpoints as MCP tools with minimal configuration, supporting type-safe input handling and tool registration.
    25 npm
    2
    MIT

  • izlek

    barisGultekin
    F
    license
    Not graded
    quality
    B
    maintenance
    Read-only MCP server for izlek, a terminal-first local frontend observability tool. Enables agents to query live session status, logs, errors, and HTTP request/response records from a running development session.
    -

  • ai-usage-mcp

    flaviozantut
    F
    license
    Not graded
    quality
    B
    maintenance
    Read-only MCP server for querying AI usage metrics (exact tokens, cost, latency, errors, productivity) from a local SQLite database, enabling charts and analysis in Claude Code and Cursor.
    -

  • mcp-honojs

    zahidhasanaunto
    F
    license
    Not graded
    quality
    D
    maintenance
    A lightweight Hono.js middleware for building Model Context Protocol servers using a simple, fluent API and supporting both SSE and HTTP transports. It enables developers to create type-safe, edge-ready MCP-compatible APIs with built-in session management.
    -

  • req-mcp-server

    TarminaRX
    F
    license
    Not graded
    quality
    D
    maintenance
    A Bun-based MCP server providing a persistent HTTP request toolset for testing and inspecting JSON APIs. It supports session-aware operations, including cookie persistence, automatic bearer token reuse, and configurable base URLs.
    -

  • Carbo MCP Gateway

    sircarbo
    F
    license
    Not graded
    quality
    B
    maintenance
    A read-only, OAuth 2.1-authenticated MCP server that lets Claude inspect the live state of a self-hosted server — system resources, containers, service and website health, n8n automations, video jobs, backups, repositories, error summaries, a component design system, uptime monitoring, and its own audit trail. All twenty-one tools are strictly observation-only, with no shell, file browser, SQL console, or Docker socket, so nothing can be started, stopped, deployed, or deleted.
    -
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.4/5.0

Scored across 5 tools

Disambiguation5/5

Each tool maps to a distinct investigation step: stats for overview, recent_exceptions for thrown failures, recent_requests for status-based failures, slow_queries for DB performance, and request_detail for full inspection. There is no pair an agent would realistically confuse after reading the descriptions.

Naming Consistency4/5

All names are snake_case noun phrases with a consistent recent_* prefix for list views and a clear singular request_detail for deep dive. The only minor deviation is the abbreviated stats, but the overall pattern is otherwise uniform.

Tool Count5/5

Five tools is well-scoped for a Telescope observability server: an entry point, two list views, one detail drill-down, and one performance view. There are no redundant tools, and the count fits the purpose comfortably.

Completeness5/5

The tools cover the full inspection workflow: check what is retained, list failures, drill into a single request, and identify slow queries. The workflow has no dead ends because every list tool points toward request_detail for deeper context.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources