FRENES

Developer tools · MCP server

Hono telescope: MCP server, setup and security

Hono telescope is an open-source MCP server published on GitHub that lets an AI agent inspect Hono exceptions, request logs and the slowest database queries. Its repository has 27 stars and its last commit is from October 19, 2026 and it is licensed under MIT.

Actively maintained

What Hono telescope does

According to its repository: “Read-only debugging for Hono apps: recent exceptions with their requests, logs and queries, requests filtered by status or duration, and the slowest queries.”

The Model Context Protocol (MCP) is a standard plug between an AI agent and an outside service: once the server is connected, its tools show up in the agent, which decides when to call them. Hono telescope is listed under Developer tools, a category of 475 servers in the directory, where it ranks #308 by stars.

Topics declared by the repository: bun, debugging, hono, middleware, monitoring, nodejs.

Installing and connecting Hono telescope

No package or remote server is declared in the official MCP registry: you install it from source, following the repository README.

It works with any MCP-compatible client (Claude Desktop, Claude Code, Cursor, VS Code, Codex and most recent agents). You add one entry to the client's MCP configuration: server name, start command or URL, environment variables. Project language: TypeScript.

Security: what to check

Connecting an MCP server means installing software that talks straight to your agent: it runs with your rights and the model trusts its tool descriptions. The risk therefore depends on what it can touch and how far its code can be trusted.

None of the risk signals we track (system access, secrets, missing licence, abandonment) applies to Hono telescope. That does not replace reading the code.

Good practice: grant only the rights needed (least privilege), require human approval for irreversible actions, and run the AI agent security check.

Project activity and maintenance

Created on October 16, 2025, the Jubstaaa/hono-telescope repository has 27 stars and 0 forks, with 1 open issues. It has more stars than 43% of the servers in the directory. It received changes this month.

Stars measure attention, not quality: a recent, heavily promoted project can collect them fast, while a useful but niche server will have few.

StorybookStorybook : 91.4K91.4KFront End ChecklistFront End Checklist : 74.6K74.6KTldrawTldraw : 51.1K51.1KCodebase MemoryCodebase Memory : 47.4K47.4KCCXTCCXT : 44.5K44.5KPostHog MCP ServerPostHog MCP Server : 40.4K40.4KClaude task masterClaude task master : 28.3K28.3KAgent Skills Search ServerAgent Skills Search Server : 26.6K26.6KHono telescopeHono telescope : 2727
GitHub stars of the most followed servers in the category (log scale); Hono telescope in orange. Checked October 25, 2026.

Verdict

Hono telescope is a reasonable choice; check the points below before connecting it.

Strengths

  • Active project: recent commit
  • Permissive licence (MIT)

Limitations

  • Install from source

Frequently asked questions

How do I install Hono telescope?

No package is declared in the MCP registry: clone the Jubstaaa/hono-telescope repository, follow its README, then declare the start command in your client's MCP configuration.

Is Hono telescope free?

The code is published under the MIT licence and can be used free of charge.

Is Hono telescope safe?

No risk signal found (system access, secrets, licence, abandonment). As with any MCP server, keep rights minimal and read the code before sensitive use.

Is it an official server?

Nothing says so: it is a project published by Jubstaaa on GitHub. Check who maintains it before giving it access.

What are the alternatives to Hono telescope?

In the same category: Radar Kubernetes MCP Server, Repowise, Jscpd, and Apify MCP server. Radar Kubernetes MCP Server and Repowise score higher on our grid.

Related articles

Neutrality. No affiliate links. No vendor pays to be reviewed, rated or ranked. Reviews are directed by François Chollet, neutral and factual, and every data point is dated and sourced. How we score