Skip to main content
Glama
jakejackson910

license-verifier-mcp

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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
verify_licenseA

Verify a professional license in a specific state. Returns license status, holder name, issue/expiration dates, and any disciplinary actions.

search_licenseA

Search for a professional license across multiple states. Useful when you don't know which state issued the license.

list_supported_statesA

List all states currently supported for license verification, with their capabilities.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.3/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: verify_license for a known state, search_license for unknown states, and list_supported_states for metadata. There is no overlap or ambiguity between them.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with lowercase and underscores (verify_license, search_license, list_supported_states). This predictable structure makes the API easy to navigate.

Tool Count5/5

Three tools are well-scoped for a license verification service. Each tool serves a necessary function without unnecessary bloat, and the count fits comfortably within the ideal 3-15 range.

Completeness5/5

The tool set fully covers the core workflow: verify a known license, search when the state is unknown, and check supported states. There are no obvious missing operations for the stated domain.

Maintenance

ActivityInactive
ResponsivenessNo issues