Obsidian Regulatory MCP vs License Verify MCP
A side-by-side look at the Obsidian Regulatory MCP and License Verify MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Obsidian Regulatory MCP for legal work over a hosted endpoint; choose License Verify MCP 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 Obsidian Regulatory MCP when
- You need dedicated capabilities in the Legal domain.
- You prefer a remote HTTP/SSE transport.
Choose License Verify MCP when
- You need dedicated capabilities in the Legal domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
jurisdiction, license_number, business_name.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 37/100 · Fair | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Paid service |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 3 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | Not listed | 3 |
| Full listing | View Obsidian Regulatory MCP | View License Verify MCP |
Tools & capabilities
Obsidian Regulatory MCP tools
No tool names declared yet. Check the project README from the listing page.
License Verify MCP tools 3
jurisdictionlicense_numberbusiness_name
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.
Obsidian Regulatory MCP
{
"mcpServers": {
"obsidian-regulatory-mcp": {
"url": "https://obsidianri.com/mcp"
}
}
}
License Verify MCP
{
"mcpServers": {
"lmaniraruta-license-verify-mcp": {
"command": "npx",
"args": [
"-y",
"apify"
]
}
}
}
Frequently asked questions
Obsidian Regulatory MCP is categorized under Legal and uses a remote HTTP/SSE transport. License Verify MCP belongs to Legal and uses a local stdio subprocess. Pick Obsidian Regulatory MCP for legal work and License Verify 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.
Obsidian Regulatory MCP has no declared pricing — check the project's own site. License Verify MCP is listed as a paid service. Auth: no auth required. 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 obsidian-regulatory-mcp and lmaniraruta-license-verify-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Obsidian Regulatory MCP has a quality signal of 37/100 (Fair) with 3 views, 0 installs and 0 GitHub stars. License Verify MCP has 57/100 (Good) with 5 views, 0 installs and 0 GitHub stars.