Skip to main content
Glama
minanyang

Nameable

by minanyang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GH_TOKENNoOptional GitHub token used for GitHub checks to get a higher rate limit.
GITHUB_TOKENNoOptional GitHub token used for GitHub checks to get a higher rate limit.
NAMEABLE_CACHE_DIRNoOptional directory where Nameable keeps its downloaded registry name lists.

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
check_namesA

Check whether names are free on package registries, GitHub, agent and editor directories, app stores and domains.

Each result has a status:

  • available: nobody holds it and the registry would accept it. certainty "confirmed" means every rule that public data allows was checked; "probable" means one could not be, and note says which.

  • reclaimable: held before but released; it can be taken again.

  • taken: someone holds it; url shows who. Where names are not exclusive (MCP Registry, Google Play, Gemini CLI gallery) it means another entry uses the name, and note says it does not block a new one.

  • unavailable: nobody holds it exactly, but the registry would refuse it (invalid, reserved, too similar to an existing name, or blocked for now after a deletion); note says why.

  • unknown: no trustworthy answer (network error, rate limit). Never treat it as free.

Pick only the channels that matter for the project instead of checking everything.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

TDQS

A4.5/5.0

Scored across 1 tool

Disambiguation5/5

There is only one tool, so there is nothing to confuse it with. Its purpose is clearly stated and narrowly scoped to checking name availability across registries.

Naming Consistency5/5

A single tool named check_names uses a clear, conventional verb_noun snake_case pattern. There are no other names to clash with, so consistency is trivially satisfied.

Tool Count4/5

One tool is thin for a named server, but the domain is narrow and the tool bundles many channels into a single well-scoped operation. It earns its place, though a batch or channel-listing variant could add value.

Completeness4/5

The tool covers the full name-checking lifecycle across package registries, GitHub, directories, app stores and domains, with nuanced statuses. Minor gaps remain, such as no explicit way to list supported channels or batch-check names in one call.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources