Legiscan MCP vs Research Hub — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Legiscan MCP vs Research Hub
In-depth architectural comparison of the Legiscan MCP and Research Hub MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Legiscan MCP
Research · Local stdio
Quality: 61/100 (Good) | Auth: API Key required
Research Hub
Research · Local stdio
Quality: 56/100 (Good) | Auth: API Key required
Verdict Summary: Choose Legiscan MCP if you need specialized Research tools running via a local process. Choose Research Hub if your workspace requires Research integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Legiscan MCP when:
You need dedicated capabilities in the Research domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: LEGISCAN_API_KEY.
You need dedicated capabilities in the Research domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: ZOTERO_API_KEY, ZOTERO_USER_ID, NOTEBOOKLM_API_KEY, GOOGLE_API_KEY, GOOGLE_OAUTH_CLIENT_ID, GOOGLE_OAUTH_CLIENT_SECRET.
Access legislative data from all 50 US states and Congress — search bills, get full text, track votes, and look up legislators via the LegiScan API.
Research workspace MCP integrating Zotero, Obsidian, and NotebookLM. Search papers (arXiv/Semantic Scholar/PubMed/CrossRef), ingest into Zotero, sync notes to Obsidian, verify NotebookLM briefs. All three external tools optional. pip install research-hub-pipeline then research-hub serve.
Category & Scope
Tools & Capabilities Breakdown
Legiscan MCP Tools (10)
legiscan_find_legislator
Find a legislator's people_id by name. Supports partial matching.
legiscan_get_legislator_votes
Get how a legislator voted on multiple bills in one call.
legiscan_get_primary_authored
Get only bills where legislator is primary author (not co-sponsor).
legiscan_get_bill
Get detailed bill info (sponsors, history, votes, texts)
legiscan_find_bill_by_number
Find bill by number (handles AB 858, AB858, AB-858, A.B. 858). Best for exact bill lookup.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Legiscan MCP is categorized under Research and uses a local stdio subprocess. In contrast, Research Hub belongs to Research using local stdio subprocess. Select Legiscan MCP when you need capabilities focused on research and Research Hub when you require tools for research.
Primary tools included: Unified search across arXiv, Semantic Scholar, PubMed, and CrossRef, Integration with Zotero for reference management, Obsidian note syncing and dashboard visualization.