LicenseGround MCP server
com.licenseground/licensegroundlicenseground.comstreamable-httpv1.0.1Scanned
Deterministic trade contractor license verification & compliance gating for autonomous AI agents.
6 tools: 4 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
4 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the LicenseGround MCP server can do
The LicenseGround MCP server is published by licenseground.com, a domain the MCP Registry verified. It has 6 tools. It can create or change data (4 tools: verify_license, check_compliance_risk, check_federal_debarment and audit_osha_safety), but cannot delete data. 2 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 13, 2026, version 1.0.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Changes things 4Claude Code: ask
audit_osha_safetyAudit contractor worksite safety history against the OSHA inspection and enforcement database.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Audit contractor worksite safety history against the OSHA inspection and enforcement database. Evaluates willful safety violations, repeat fall protection citations, and cumulative penalties. Args: entity_name: Official business or entity name to evaluate.
check_compliance_riskPerform an automated compliance and liability risk assessment for autonomous onboarding, hiring, or payments.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Perform an automated compliance and liability risk assessment for autonomous onboarding, hiring, or payments. Args: state: Two-letter US state code ('CA', 'FL', or 'TX'). Required. entity_name: Company name or DBA to assess. license_number: State license number to assess. trade: Trade category: 'roofing', 'hvac', 'electrical', 'plumbing', 'general_contractor', or 'any'. require_workers_comp: If true, fails compliance if no verified workers' comp policy is active on file. require_surety_bond: If true, fails compliance if contractor bond is inactive or missing. max_disciplinary_actions: Maximum allowed board citations or disciplinary orders (default 0). min_confidence_score: Minimum entity name match confidence threshold (0.0 to 1.0, default 0.85). Returns: JSON with 'can_hire' boolean, 'risk_level' ('LOW', 'MEDIUM', 'HIGH', 'CRITICAL'), 'risk_score' (0.0 to 100.0), specific 'flags', and the full underlying verification result.
check_federal_debarmentCheck if a contractor is actively debarred or suspended on the federal SAM.gov Excluded Parties List System (EPLS).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Check if a contractor is actively debarred or suspended on the federal SAM.gov Excluded Parties List System (EPLS). Crucial for public contracts, infrastructure, and enterprise B2B compliance. Args: entity_name: Official business or entity name to evaluate against federal sanctions.
verify_licenseVerify an entity's trade contractor license against the official state licensing board (CSLB, DBPR, or TDLR).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Verify an entity's trade contractor license against the official state licensing board (CSLB, DBPR, or TDLR). Args: state: Two-letter US state code ('CA', 'FL', or 'TX'). Required. entity_name: The company name, DBA, or contractor name to verify (e.g. 'Apex Roofing LLC'). license_number: The official state license or certificate ID (e.g. '1058291', 'CCC1330999', 'TACLA29188C'). trade: Trade category: 'roofing', 'hvac', 'electrical', 'plumbing', 'general_contractor', or 'any'. Default is 'any'. city: Optional city to filter geographic disambiguation. Returns: Deterministic, machine-actionable JSON containing verification status, canonical name, active standing, disciplinary action count, workers' compensation status, bond status, and confidence score.
Only reads 2Show 2 read-only tools
get_registry_statusCheck the system health, cache performance statistics, and multi-state registry connectivity.No findings
Why it is in this group
- The name "get_registry_status" says "get": a word for reading.
Description, as the server wrote it Check the system health, cache performance statistics, and multi-state registry connectivity. Returns: JSON object with cache hit/miss counts, total records cached, and connector status for CA, FL, TX, NY, MA, IL, AZ.
search_contractorsDiscover active, verified trade contractors in California, Florida, or Texas by trade classification and location.No findings
Why it is in this group
- The name "search_contractors" says "search": a word for reading.
Description, as the server wrote it Discover active, verified trade contractors in California, Florida, or Texas by trade classification and location. Args: state: Two-letter US state code ('CA', 'FL', or 'TX'). Required. trade: Trade category ('roofing', 'hvac', 'electrical', 'plumbing', 'general_contractor'). Required. city: Optional city to filter contractors by location. limit: Maximum number of contractors to return (1 to 50, default 10). Returns: JSON list of verified contractors with active licenses, phone numbers, and addresses.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:41 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 4
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- yes
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://licenseground.com/mcp: tools/list returned 6 tools to an anonymous client, including verify_license (write), check_compliance_risk (write), check_federal_debarment (write), audit_osha_safety (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http licenseground https://licenseground.com/mcpclaude mcp add --transport http licenseground https://licenseground.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__licenseground__search_contractors",
"mcp__licenseground__get_registry_status"
],
"ask": [
"mcp__licenseground__verify_license",
"mcp__licenseground__check_compliance_risk",
"mcp__licenseground__check_federal_debarment",
"mcp__licenseground__audit_osha_safety"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as licenseground. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.licenseground/licenseground/verify?hash=15654005d3afacad98a71f8b41b0c85cb33e825053bcef309d8cf5079dbf04e0" | jq -e '.changed == false'Pinned hash 15654005d3af, from Nov 13, 2026, 16:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.licenseground/licenseground/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.licenseground/licenseground)Source: MCP Registry. Synced Oct 21, 2026, 17:58 UTC.
LicenseGround MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the LicenseGround MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the LicenseGround MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the LicenseGround MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the LicenseGround MCP server have?
- 6 tools: 4 write, 2 read. verify_license, check_compliance_risk, check_federal_debarment, audit_osha_safety, search_contractors and get_registry_status.
Does the LicenseGround MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the LicenseGround MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the LicenseGround MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 13, 2026.