mcp-registry/ai.licensy/mcp-server · v3.4.5
As of 2026-10-22 03:52 UTC, the Licensy MCP server is up (it requires sign-in) with a Glimind reliability score of 82/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 1 minutes.
Real-time U.S. medical license verification across all 50 states + DC.
Claude Code
claude mcp add --transport http licensy-mcp-server https://mcp.licensy.ai/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"licensy-mcp-server": {
"type": "http",
"url": "https://mcp.licensy.ai/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
9 parameter(s) across 9 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
9 of 9 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Requires authentication (Bearer); tool definitions could not be read anonymously.
If discovery should be public, allow initialize + tools/list without credentials and gate only tools/call. Directories and routers can then list your tools.
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 9 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fai.licensy%2Fmcp-server/fixes
{
"name": "get_license_history",
"description": "Return a physician's license status as it was on a specific past date (point-in-time / retroactive lookup).\n\nUse this when:\n - Insurance company asks 'was this physician licensed when they treated patient X on 2024-08-12?'\n - Legal discovery for a malpractice case\n - Retroactive credentialing audit\n\nInput: NPI + state + as_of_date (ISO 8601).\n\nCoverage caveat: full append-only license history is on the roadmap. v1 returns best-available data and a `coverage_start` date marking the earliest relia",
"inputSchema": {
"type": "object",
"required": [
"inp"
],
"properties": {
"inp": {
"type": "object",
"required": [
"npi",
"state",
"as_of_date"
],
"properties": {
"npi": {
"type": "string",
"pattern": "^\\d{10}$"
},
"state": {
"type": "string",
"maxLength": 20,
"minLength": 2
},
"as_of_date": {
"type": "string",
"description": "ISO 8601 date (YYYY-MM-DD)."
}
}
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_license_status",
"description": "Return only the license status string for a single physician in a single state. The minimal-output companion to verify_license: optimized for agents that need only a yes/no decision and want to minimize tokens in the LLM context.\n\nUse this when:\n - You need a one-word answer for routing logic (active vs anything else)\n - You're checking a license inside a tight inner loop\n - You want to minimize tokens spent on auxiliary fields\n\nUse verify_license instead when you need expiration date, license_a",
"inputSchema": {
"type": "object",
"required": [
"inp"
],
"properties": {
"inp": {
"type": "object",
"required": [
"npi",
"state"
],
"properties": {
"npi": {
"type": "string",
"pattern": "^\\d{10}$"
},
"state": {
"type": "string",
"maxLength": 20,
"minLength": 2
}
}
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_screenshot_url",
"description": "Return an audit-grade screenshot of the state medical board page used to verify a physician's license. The URL is signed and valid for 15 minutes.\n\nUse this when:\n - You need primary-source evidence for an audit, credentialing file, or insurance contract\n - The end user asks 'where did this come from?'\n - You're generating a credentialing PDF that needs proof attachments\n\nIdentify the license by: NPI + state, OR by `license_id` if you already fetched it via verify_license / list_physician_licens",
"inputSchema": {
"type": "object",
"required": [
"inp"
],
"properties": {
"inp": {
"type": "object",
"properties": {
"npi": {
"anyOf": [
{
"type": "string",
"pattern": "^\\d{10}$"
},
{
"type": "null"
}
],
"default": null
},
"state": {
"anyOf": [
{
"type": "string",
"maxLength": 20,
"minLength": 2
},
{
"type": "null"
}
],
"default": null
},
"license_id": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"description": "Licensy internal license_id. Use this when you previously fetched a license via verify_license and want the screenshot for that exact row."
}
}
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/ai.licensy/mcp-server"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/ai.licensy/mcp-server"}) over MCP.
verify_license ~374 tokensget_screenshot_url ~307 tokenssearch_disciplinary_actions ~284 tokenssubscribe_to_changes ~280 tokensbulk_verify ~270 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fai.licensy%2Fmcp-server?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fai.licensy%2Fmcp-server?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.licensy%2Fmcp-server.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.licensy%2Fmcp-server.svg :target: https://glimind.com/server/mcp-registry%2Fai.licensy%2Fmcp-server?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:8bf6e51e7e5ff909…, first seen 2026-10-17, included at leaf 5785 of 43,675. Version history · verify what your client received.
Compare: most reliable data servers · most reliable knowledge servers · most reliable web servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-22 03:52 UTC, the Licensy MCP server is up (it requires sign-in) with a Glimind reliability score of 82/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 1 minutes.
Licensy MCP server advertises 9 tools, including bulk_verify, get_license_history, get_license_status, get_screenshot_url, list_physician_licenses.
Point your MCP client at this streamable-http endpoint: https://mcp.licensy.ai/mcp
Glimind scanned all 9 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.