Skip to main content
Glama
minte-app

mcp-untun

by minte-app
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
start_tunnelA

Creates a secure tunnel from a public internet address to your local server.

This tool will:

  • Start an untun tunnel process connecting to your specified local URL

  • Return a public URL that can be used to access your local server

  • Allow you to name your tunnel for easier management

After starting a tunnel, wait a few seconds and use 'list_tunnels' to check its status and get the public URL.

stop_tunnelA

Stops a running tunnel or all local tunnels.

This tool will:

  • Stop a specific tunnel identified by name (if provided)

  • Stop all local tunnels (if no name is provided)

  • Only affects tunnels running on the current machine

  • Will not affect tunnels running on other machines

After stopping tunnels, you can use 'list_tunnels' to confirm they've been terminated.

list_tunnelsA

Lists all active tunnels including their status and details.

This tool will:

  • Show all tunnels in the registry

  • Auto-detect any running tunnels not in the registry

  • Display tunnel status, name, URLs, and runtime information

  • Indicate whether tunnels are local or running on remote machines

Use this tool to check the status of your tunnels and get their public URLs.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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.5/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: list_tunnels for viewing status, start_tunnel for creation, and stop_tunnel for termination. The descriptions reinforce these distinct roles, making misselection unlikely.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern (list_tunnels, start_tunnel, stop_tunnel) with uniform snake_case styling. This predictability makes the tool set easy to understand and navigate.

Tool Count5/5

With 3 tools, this server is well-scoped for tunnel management, covering the essential lifecycle operations: list, start, and stop. Each tool earns its place without bloat or thinness.

Completeness5/5

The tool set provides complete CRUD-like coverage for tunnel management: list (read), start (create), and stop (delete). There are no obvious gaps, and the descriptions indicate seamless workflow integration.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources