Licenscheck vs Obsidian Regulatory MCP
A side-by-side look at the Licenscheck and Obsidian Regulatory MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
L
LicenscheckLegalVerify US contractor licenses across states: Clear, Review or Risk, with the reasons.37FairAuth: not declaredVerdict: choose Licenscheck for legal work; choose Obsidian Regulatory MCP for legal over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Obsidian Regulatory MCP when
- You need dedicated capabilities in the Legal domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | L Licenscheck | |
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 37/100 · Fair | 40/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Licenscheck | View Obsidian Regulatory MCP |
Tools & capabilities
Licenscheck tools
No tool names declared yet. Check the project README from the listing page.
Obsidian Regulatory MCP 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.
Licenscheck
No confirmed install command for Licenscheck yet — follow the setup steps linked from its listing page rather than a guessed package name.
Obsidian Regulatory MCP
{
"mcpServers": {
"obsidian-regulatory-mcp": {
"url": "https://obsidianri.com/mcp"
}
}
}
Frequently asked questions
Licenscheck is categorized under Legal and uses an install path we have not confirmed yet. Obsidian Regulatory MCP belongs to Legal and uses a remote HTTP/SSE transport. Pick Licenscheck for legal work and Obsidian Regulatory MCP 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. Licenscheck has no confirmed install command yet — follow its own setup instructions.
Licenscheck has no declared pricing — check the project's own site. Obsidian Regulatory MCP 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 licenscheck and obsidian-regulatory-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Licenscheck has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Obsidian Regulatory MCP has 40/100 (Fair) with 2 views, 0 installs and 0 GitHub stars.