hono-telescope
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TELESCOPE_URL | Yes | The MCP endpoint your instrumented Hono app serves, e.g. http://localhost:3000/telescope/mcp | |
| TELESCOPE_HEADER | No | Optional header sent with every request, e.g. 'Authorization: Basic ...' when the dashboard is behind basic auth |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| recent_exceptionsA | The most recent exceptions, each with the request that produced it and that request's logs, queries and outgoing calls. Start here when something failed. |
| recent_requestsA | Recent incoming requests with child counts. Filter with minStatus: 400 to find failures that returned an error status without throwing. |
| request_detailA | One request in full — headers, payload, response body — with every log, query, exception and outgoing call recorded inside it. Nothing is truncated. Reach for it once a list tool has narrowed the search to one request. |
| slow_queriesA | Recent database queries sorted slowest first, each with the request it ran in. Use request_detail on that request to see everything else it did. |
| statsA | How many entries of each type Telescope is holding right now. The counts cover what is still retained: the oldest entries are dropped once storage reaches maxEntries. Read it first to see whether there is anything to look at, then drill in with recent_exceptions or recent_requests. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jubstaaa/hono-telescope'
If you have feedback or need assistance with the MCP directory API, please join our Discord server