A
licenseA
qualityD
maintenanceReal-time contractor license verification across 45 US states. Verifies license status, expiration, and disciplinary history directly against state licensing board portals.
4
98
MIT
Licensy
by ai.licensy
Server Details
Real-time U.S. medical license verification across all 50 states + DC.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4.6/5.0
Tool DescriptionsA
Average 4.6/5 across 9 of 9 tools scored.
Server CoherenceA
Disambiguation5/5
Each tool has a distinct purpose: bulk_verify for batch checks, verify_license for single detailed, get_license_status for minimal status, get_license_history for retroactive queries, list_physician_licenses for multi-state overview, search_disciplinary_actions for sanctions, get_screenshot_url for audit evidence, and subscribe_to_changes/unsubscribe for webhook management. Overlaps are clearly delineated by use case and input/output differences.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern: get_*, list_*, search_*, subscribe_to_changes, unsubscribe, bulk_verify. The naming is predictable and intuitive, making it easy for an agent to infer functionality from the name alone.
Tool Count5/5
With 9 tools, the set is well-scoped for medical license verification. Each tool serves a necessary function without redundancy, covering single queries, bulk operations, historical lookups, disciplinary searches, audit evidence, and webhook subscriptions. The count feels neither sparse nor bloated.
Completeness5/5
The tool surface comprehensively covers the core workflows: verifying current status (single and bulk), historical verification, listing all licenses, disciplinary actions, audit-grade screenshots, and change notifications. No obvious gaps exist for the server's stated purpose of license verification and monitoring.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- AlicenseAqualityDmaintenance50-state professional license verification for AI agents.315MIT
- Flicense-qualityBmaintenanceSource-provenanced US federal healthcare provider data over MCP. Resolve any NPI or CCN across NPPES, OIG LEIE, SAM.gov, state Medicaid exclusions, CMS PECOS, Care Compare, and Open Payments — every field carries a 14-field provenance contract, and an "excluded or compromised anywhere" check runs on every lookup.
- Flicense-qualityDmaintenanceEnables identity verification by checking name, address, and date of birth against national databases.
