Contractor License Verification (TradesAPI) vs MCP Expert Witness Directory
A side-by-side look at the Contractor License Verification (TradesAPI) and MCP Expert Witness Directory MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Contractor License Verification (TradesAPI) for legal work as a local process; choose MCP Expert Witness Directory for legal as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Contractor License Verification (TradesAPI) when
- You need dedicated capabilities in the Legal domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
CLV_API_URL, CLV_API_KEY. - You want tools like
verify_license.
Choose MCP Expert Witness Directory when
- You need dedicated capabilities in the Legal domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
APIFY_TOKEN.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 49/100 · Fair | 36/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | CLV_API_URLCLV_API_KEY | APIFY_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 1 | Not listed |
| Full listing | View Contractor License Verification (TradesAPI) | View MCP Expert Witness Directory |
Tools & capabilities
Contractor License Verification (TradesAPI) tools 1
verify_licenseVerify a single contractor license against the official state (or city) licensing portal.
MCP Expert Witness Directory tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Contractor License Verification (TradesAPI)
{
"mcpServers": {
"contractor-license-verification-tradesapi-2": {
"command": "npx",
"args": [
"-y",
"contractor-license-mcp-server"
],
"env": {
"CLV_API_URL": "YOUR_CLV_API_URL_HERE",
"CLV_API_KEY": "YOUR_CLV_API_KEY_HERE"
}
}
}
}
MCP Expert Witness Directory
{
"mcpServers": {
"mcp-expert-witness-directory": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-expert-witness-directory"
],
"env": {
"APIFY_TOKEN": "YOUR_APIFY_TOKEN_HERE"
}
}
}
}
Frequently asked questions
Contractor License Verification (TradesAPI) is categorized under Legal and uses a local stdio subprocess. MCP Expert Witness Directory belongs to Legal and uses a local stdio subprocess. Pick Contractor License Verification (TradesAPI) for legal work and MCP Expert Witness Directory for legal.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Contractor License Verification (TradesAPI) has no declared pricing — check the project's own site. MCP Expert Witness Directory has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add contractor-license-verification-tradesapi-2 and mcp-expert-witness-directory as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Contractor License Verification (TradesAPI) has a quality signal of 49/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. MCP Expert Witness Directory has 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.