Databases

agingresearch.news

An MCP server for searching and retrieving aging biology research papers, related entities, and summaries.

1 endpoint26 known toolsFirst detected October 13, 2026Last detected October 13, 2026

ENDPOINT 1

https://agingresearch.news/api/mcp

No auth detected

MCP server metadata

Name: agingresearch-news
Version: 1.3.0

Capabilities

toolsresourcesextensions.io.modelcontextprotocol/ui.mimeTypes

Server instructions

AgingResearch.News (ARN) reads new papers from PubMed, bioRxiv, medRxiv, arXiv and other sources and judges what each paper's own work shows about human aging. Use these tools for questions about aging and longevity research: papers, ARN's stories about them, the drugs, genes, processes and diseases they study, clinical trials and industry news. Lists hold the papers ARN judged relevant to aging unless you pass min_relevance (0 returns everything it read). Every paper names its study type (human trial, human observational, animal, cells, in silico, review and others): keep animal and cell results apart from human ones when you report them, and say when a paper is a preprint. Cite a paper with its title and url, or site_url for its page on ARN. Page on with cursor, from pagination.next_cursor. Most tools work without an account, within a daily number of lookups. Signing in to AgingResearch.News gives the user their own plan's lookups.

Known tools 26

search_papers

Use this when the user asks what research has found on a question in the biology of aging or an age-related disease, often without the word aging: senescence and senolytics, epigenetic clocks, partial reprogramming, mitochondrial dysfunction, NAD+, inflammaging and immune aging, ovarian aging and menopause, neurodegeneration, cardiovascular and metabolic decline, sarcopenia, regeneration, and long-lived species such as naked mole rats and whales.

Inferred read-only

list_papers

Use this when the user asks what is new: the latest papers in a field (mitochondrial dysfunction, immune aging, senolytics), of a study type such as randomised trials, on a body system, or by one author (author takes a name, or an author_id from get_paper), for example to shortlist a lab's journal club.

Inferred read-only

get_paper

Use this when the user wants one paper in depth: what it did and found, in which species and how many subjects, its caveats, who wrote it and where they work.

Inferred read-only

list_stories

Use this when the user wants a readable round-up of recent findings: what happened this week in aging research, the notable results in a field, or a short list for a journal club.

Inferred read-only

find_entities

Use this to find the type and key of what a question names (a drug, supplement or diet, a gene or protein, a biological process, a disease, a biomarker, an organism, a method or a hallmark of aging) before get_entity, list_claims or list_grants.

Inferred read-only

get_entity

Use this for questions about one drug, supplement, gene, process or disease, such as: is there human evidence for this intervention; has the finding been replicated by independent labs; in which species; what trials test it and how many have posted no results; who funds the work and which companies are tied to it; what the newest papers on it report.

Inferred read-only

list_claims

Use this when the user asks what has been found about a relation: does an intervention extend lifespan, and in which organisms; what lowers a biomarker; what acts on a process.

Inferred read-only

list_trials

Use this when the user asks about clinical trials on aging or an age-related condition: what is recruiting, what changed lately (a new status, a completion, results posted), which trials test a drug, or which companies run them.

Inferred read-only

get_trial

Use this when the user asks about one clinical trial by its registry number (NCT, ISRCTN, ChiCTR, CTRI, CTIS and the rest): its design, outcomes and dates, what changed and when, and which papers cite it.

Inferred read-only

list_news

Use this when the user asks about events in aging research and the longevity industry: company financings and deals, trial readouts, approvals and regulators, policy, conferences.

Inferred read-only

list_grants

Use this when the user asks who funds work on a target, a drug, a process or a lab, how much and since when, or what a funder pays for in aging research.

Inferred read-only

list_conferences

Use this when the user asks which meetings on aging research and age-related disease are coming up, or which have just been held.

Inferred read-only

get_conference

Use this when the user asks about one meeting from list_conferences, or what was presented there.

Inferred read-only

list_assets

Use this when the user asks which drugs or therapies are in development against a target, a mechanism, a hallmark of aging or an age-related disease, who develops them and how far each has got.

Inferred read-only

get_asset

Use this when the user asks about one drug or therapy programme by its name or any code name (ubx1325, UBX-1325, BMS-986278).

Inferred read-only

count_pipeline

Use this when the user asks how many drug and therapy programmes there are, or how a field's pipeline splits.

Inferred read-only

follow

Use this when the user asks to follow a drug, gene, process, disease or other entity on AgingResearch.

Inferred read-only

unfollow

Use this when the user asks to stop following a drug, gene, process or other entity on AgingResearch.

Inferred read-only

list_follows

Use this when the user asks what they follow on AgingResearch.

Inferred read-only

list_questions

Use this when the user asks about questions they asked AgingResearch.

Inferred read-only

open_arn

Use this when the user asks to open AgingResearch.

Inferred read-only

list_feed

The sidebar's feed: For you or Top, as story cards.

Inferred read-only

search_arn

The sidebar's search: entities and papers matching words, as cards.

Inferred read-only

ask_arn

Use this when the user asks a research question on the biology of aging, longevity interventions, age-related disease, or the people and companies of the field (for example: does rapamycin extend lifespan in people, what is known about senolytics for frailty, who works on epigenetic clocks).

Inferred read-only

start_ultradeep

Use this when the user asks for a full review of the evidence on a research question in aging or longevity, beyond a short answer.

Inferred read-only

get_ask_answer

Use this when ask_arn or start_ultradeep said an answer is still being written, or the user wants it again: it reads that question's answer by the question_id they gave: the answer with its numbered sources once it is written, or where it stands while ARN writes it.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.agingresearch-news]
url = "https://agingresearch.news/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "agingresearch-news": {
      "type": "http",
      "url": "https://agingresearch.news/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: agingresearch-news
Remote MCP URL: https://agingresearch.news/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "agingresearch-news": {
      "url": "https://agingresearch.news/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "agingresearch-news": {
      "type": "http",
      "url": "https://agingresearch.news/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "agingresearch-news",
  "transport": "streamable-http",
  "url": "https://agingresearch.news/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.