In-depth architectural comparison of the Capital Equipment and Paper Chaser MCP 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
Capital Equipment
Research · Remote HTTP/SSE
Quality: 48/100 (Fair) | Auth: No auth required
Paper Chaser MCP
Research · Remote HTTP/SSE
Quality: 49/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Capital Equipment if you need specialized Research tools running via a hosted cloud SSE transport. Choose Paper Chaser MCP if your workspace requires Research integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Capital Equipment when:
You need dedicated capabilities in the Research domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Capital Equipment is categorized under Research and uses a remote streaming HTTP/SSE transport. In contrast, Paper Chaser MCP belongs to Research using remote streaming HTTP/SSE transport. Select Capital Equipment when you need capabilities focused on research and Paper Chaser MCP when you require tools for research.
Default trust-graded entrypoint for discovery, known-item recovery, citation repair, and regulatory routing.
follow_up_research
Grounded follow-up over a saved `searchSessionId`; returns explicit abstention/insufficient-evidence states when needed.
resolve_reference
Resolve citation-like input (citation, DOI, arXiv, URL, title fragment, regulatory reference) into the safest next anchor.
inspect_source
Inspect one `sourceId` from a guided result set for provenance, trust state, and direct-read follow-through.
get_runtime_status
Guided runtime summary for active profile, transport, smart-provider state, and warnings.
search_papers_smart
Concept-level discovery with query expansion, multi-provider fusion, reranking, reusable `searchSessionId`, and an evidence-first expert contract (`resultStatus`, `answerability`, `routingSummary`, `evidence`, `leads`, `evidenceGaps`, `structuredSources`, `coverageSummary`, `failureSummary`). Legac…
ask_result_set
Grounded QA, claim checks, and comparisons over a saved `searchSessionId`.
map_research_landscape
Cluster a saved result set into themes, gaps, disagreements, and next-search suggestions.
expand_research_graph
Expand paper anchors or a saved session into a citation/reference/author graph with frontier ranking.
search_papers
Brokered single-page search (default: Semantic Scholar → arXiv → CORE → SerpApi). Read `brokerMetadata.nextStepHint`; ScholarAPI is also available as an explicit opt-in broker target.
search_papers_bulk
Paginated bulk search (Semantic Scholar) up to 1,000 papers/call with boolean query syntax.
search_papers_semantic_scholar
Single-page Semantic Scholar-only search with full filter support.
+51 more tools listed on main page
Paper Chaser MCP vs Paper Search (arXiv + Semantic Scholar + OpenAlex)