world-reference-mcp
Related Servers
Alternatives to world-reference-mcp
No user-submitted related servers found.
Related Servers
FlicenseNot gradedqualityBmaintenanceConnects AI agents to a hosted remote MCP endpoint that searches academic papers, verifies references and retraction status, retrieves research datasets, grants, and biological or chemical data, and generates scientific figures across 50+ upstream sources. Supports OAuth sign-in with per-tool credit accounting, structured error reporting, and source attribution for results.-- AlicenseNot gradedqualityAmaintenanceRead-only biomedical MCP server connecting PubMed, ClinicalTrials.gov, ClinVar, gnomAD, OncoKB, Reactome, KEGG, UniProt, PharmGKB, CPIC, OpenFDA, Monarch Initiative, GWAS Catalog, and more. One command grammar for all biomedical entities — genes, variants, diseases, drugs, trials, articles, phenotypes, pathways, proteins, diagnostics, and adverse events. 27 tools. Apache-2.0 license.1Apache 2.0
- AlicenseAqualityAmaintenanceAn MCP server that gives AI assistants access to biological and biomedical RDF databases via SPARQL at the RDF Portal, as well as selected REST APIs (NCBI E-utilities, UniProt, ChEMBL, PDB, Reactome, Rhea, MeSH, and more).22921MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI clients to access virome datasets and external bioinformatics APIs through MCP tools, including Wikipedia, PubMed, NCBI Taxonomy, read-only SQL over S3 Parquet, pandas/Plotly analyses, and map visualizations, while keeping the client decoupled from data and business logic.-
- AlicenseBqualityBmaintenanceEnables biomedical research workflows via MCP, including experiment and document search, PDF text extraction, evidence retrieval, and validation with provenance tracking.10MIT
- AlicenseNot gradedqualityDmaintenanceProvides a single MCP endpoint for 90+ tools across 42 backend servers (search, legal, domain, etc.) with per-call credit billing and a single API key.1MIT
TDQS
Scored across 9 tools
Each tool targets a distinct external source and record type: NCBI taxonomy, GBIF backbone, GBIF occurrences, ontology terms, food composition, iNaturalist observations, weather, station observations, and Wikidata alignment. The only real pair that could be confused is taxonomy_ncbi_search vs taxonomy_gbif_search, but the descriptions name their backbones explicitly. Weather-related tools (open_meteo_weather_observation vs noaa_ghcnd_daily) are also distinguishable by source and granularity.
Most tools follow a domain_entity_action shape (taxonomy_ncbi_search, gbif_occurrence_search, fdc_food_search), but the ordering of tokens varies (taxonomy_ncbi_* vs gbif_occurrence_*), and two tools drop the verb entirely (open_meteo_weather_observation, noaa_ghcnd_daily) while one uses _list instead of _search. The pattern is readable but not uniform.
Nine tools is well within a reasonable range for a multi-source reference aggregator, and each maps to a distinct data source rather than being redundant. Slightly over-provisioned on biological occurrence sources (GBIF, iNaturalist) but still coherent.
The surface covers search across all the advertised sources with pagination/cursor support, which is the core of a reference-lookup server. Minor gaps: no fetch-by-identifier for taxa or ontology terms beyond search/paging, and wikidata_alignment_search references a chemical_entity type without a dedicated chemical compound search. These are workaroundable rather than dead ends.