s3-bibliometric
Related Servers
Alternatives to s3-bibliometric
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables manuscript researchers to conduct retrieval and scoring searches, inspect human-readable results, record inline reviews, rescore cached corpora, and export reports or ChatGPT-ready research packets.-
- AlicenseNot gradedqualityBmaintenanceEnables an AI assistant to run systematic review screening steps such as creating projects, importing records, scoring and ranking them with a zero-shot LLM classifier, presenting records for human decisions, applying a statistical stopping criterion, and exporting results. Human reviewers retain responsibility for inclusion decisions, with probabilities hidden unless requested.Apache 2.0
- AlicenseBqualityBmaintenanceEnables AI assistants such as Claude to search academic literature, retrieve abstracts and full text, trace citations and multi-generation citation networks, and analyze author profiles, journal quality and bibliometrics from a conversation. It works with Scopus by default and can run the same analyses against OpenAlex without a subscription.3546 PyPI1MIT
- AlicenseNot gradedqualityCmaintenanceEnables an assistant to run a traceable scoping review end to end: build and execute PubMed/Europe PMC queries with archived raw responses, deduplicate records, list and inspect references, record human or AI-recommended screening decisions, compute flow-diagram counts, check recall against known items, and import or export CSV/RIS files. Its behaviour is driven by an editable JSON protocol, so the workflow can be retargeted to another topic without changing code.MIT
- AlicenseNot gradedqualityDmaintenanceConnects Scopus to AI assistants for literature discovery. Provides tools for finding papers, experts, citation networks, and analyzing research trends.2GPL 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to conduct academic research workflows such as paper discovery, literature mapping, citation chasing, author pivots, citation repair, and regulatory or species document retrieval.MIT
TDQS
Scored across 23 tools
Most tools target clearly distinct stages of the S3 workflow: run setup, map comparison, analysis, inspection, labeling, export, and reporting. The only real overlap is among the triple-extraction tools (extract_triples, next_triple_batch, save_triples, add_triples), but their descriptions clarify the automated versus in-chat versus file-import paths.
The set overwhelmingly uses predictable snake_case verb_noun naming, such as list_runs, run_s3_analysis, get_community, save_triples, and export_results. Minor deviations like triple_extraction_options and next_triple_batch are noun-oriented or workflow-step names, but they remain readable and mostly consistent.
With 23 tools, the surface is on the heavy side for a single server and includes many inspection/reporting endpoints. Most tools do earn their place in a complex bibliometric pipeline, but the count sits at the borderline where consolidation could improve usability.
The surface covers the full S3 lifecycle: listing models and runs, running analyses, comparing maps, enriching citations, extracting/importing triples, inspecting thresholds, communities, outliers, citation structure and knowledge trees, searching papers, saving labels, exporting results and networks, answering ranked questions, and building reports. No obvious workflow dead end is apparent.