OokCite vs Sourceright
A side-by-side look at the OokCite and Sourceright MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose OokCite for research work as a local process; choose Sourceright for research as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose OokCite when
- You need dedicated capabilities in the Research domain.
- You prefer a local stdio subprocess transport.
- You want tools like
validate_doi, lookup_isbn, reverse_lookup.
Choose Sourceright when
- You need dedicated capabilities in the Research domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Research | Research |
| Quality signal | 57/100 · Good | 40/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 | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 1 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 38 | Not listed |
| Full listing | View OokCite | View Sourceright |
Tools & capabilities
OokCite tools 38
validate_doiCheck if a DOI exists (anti-hallucination)lookup_isbnLook up a book by ISBNreverse_lookupFind a paper from messy citation text; returns original query, confidence, and titlebatch_resolveResolve many citation strings in one request (max 50)enhanced_searchCorpus search with author / category / citation facetshealth_checkCheck API availability and healthformat_citationFormat a DOI in any of 2900+ CSL styles (no API key for a single citation)verify_referencesBatch-check DOIs, and any bibliographic claim passed with thembatch_formatFormat multiple citations at oncesearch_stylesFind CSL style IDs by namelist_stylesPage through the full CSL style listgroup_citeGenerate grouped in-text markers (e.g. [1-3])- +26 more on the listing page
Sourceright 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.
OokCite
{
"mcpServers": {
"ookcite": {
"command": "npx",
"args": [
"-y",
"@turtletech/ookcite-mcp"
]
}
}
}
Sourceright
{
"mcpServers": {
"sourceright": {
"command": "npx",
"args": [
"--yes",
"markdownlint-cli2@0.18.1"
]
}
}
}
Frequently asked questions
OokCite is categorized under Research and uses a local stdio subprocess. Sourceright belongs to Research and uses a local stdio subprocess. Pick OokCite for research work and Sourceright for research.
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.
OokCite has no declared pricing — check the project's own site. Sourceright 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 ookcite and sourceright as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, OokCite has a quality signal of 57/100 (Good) with 0 views, 0 installs and 2 GitHub stars. Sourceright has 40/100 (Fair) with 1 views, 0 installs and 1 GitHub stars.