MCP servers › news.agingresearch › agingresearch-news

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

news.agingresearch/agingresearch-news

Search aging research papers, evidence, trials and grants; follow topics through Sign in with ARN. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-10-23Pricing: freemium · AI-classifiedversion 1.3.0streamable HTTP26 tools

Summary

news.agingresearch/agingresearch-news is a remote MCP server listed in the official MCP registry at version 1.3.0. On 2026-10-23 ProtocolProbe connected to it in read-only mode and read its inventory: 26 tools, 3 resources and 0 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

met: Registry entry is active and says how to run it
not met: Source repository link opens
not applicable: Repository is not archived
not applicable: Code pushed to the repository in the 90 days before our check
not applicable: Repository publishes a security policy (SECURITY.md)
not applicable: Package names its licence with a standard (SPDX) identifier
not applicable: The version the registry lists can be installed and is not withdrawn
not applicable: npm package carries build provenance (attestation)
not applicable: No known critical or high advisory in the package or its dependencies

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs: remote (hosted by the publisher)
Transport: streamable HTTP
Sign-in: none needed to open a session
Tools: 26
Described as changing data: 2 of 26 toolsAI-classified
Pricing: freemiumAI-classified
Last tested: 2026-10-23

Add to your client

Observed fact

This server accepted a session without any credential and lists 1 tool whose name or declaration suggests it changes data (unfollow). That is our reading of the names; we did not call it. Source: our connection, 2026-10-23.

Worth knowing before you connect it

2 tools are described as changing something (follow, unfollow): our AI model's reading of the descriptions, not something we tested, and the server opened a session without any credential. We did not call them.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested: yes, a real session (not a text-only review)
Last tested: 2026-10-23
Mode: read-only (no tool calls)
Latest version: 1.3.0, published 2026-10-12 (registry, as of the 2026-10-23 snapshot)
First listed version: 2026-10-12 (earliest version still in the registry; older removed versions would be earlier)
Registry data: snapshot 2026-10-23
Package and repository: checked 2026-10-23
Engine: mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 1.3.0 (published 2026-10-12).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory

26tools

3resources

0prompts

2 of 26 tools are described as changing something (creating, editing, deleting, sending or running). For 3 the reading was uncertain, so no mark is shown.

search_paperson 30 other serversreads or searches
“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, partia…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
12 inputs, 1 required
- qstringrequired“Search terms.”
- sincestring“Only papers added on or after this UTC date (YYYY-MM-DD; a full ISO timestamp is cut to its date).”
- untilstring“Only papers added on or before this UTC date (YYYY-MM-DD).”
- min_relevancenumber“How closely papers must bear on aging, 0 to 3.”
- study_typearray“Main source of evidence.”
- categoryarray“Category slug.”
- systemarray“Body system key (see `systems`).”
- age_linkarray“How the work itself connects to aging.”
- preprintboolean“`true` for preprints only, `false` for peer-reviewed papers only.”
- authorstring“Papers by an author.”
- cursorstring“Opaque cursor from `pagination.next_cursor` of the previous page.”
- limitinteger“Results per page, 1 to 25.”
list_paperson 2 other serversreads or searches
“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 randomized trials, on a body system, or by one aut…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
12 inputs
- sincestring“Only papers added on or after this UTC date (YYYY-MM-DD; a full ISO timestamp is cut to its date).”
- untilstring“Only papers added on or before this UTC date (YYYY-MM-DD).”
- min_relevancenumber“How closely papers must bear on aging, 0 to 3.”
- study_typearray“Main source of evidence.”
- categoryarray“Category slug.”
- systemarray“Body system key (see `systems`).”
- age_linkarray“How the work itself connects to aging.”
- preprintboolean“`true` for preprints only, `false` for peer-reviewed papers only.”
- authorstring“Papers by an author.”
- qstring“Full-text filter over title and abstract.”
- cursorstring“Opaque cursor from `pagination.next_cursor` of the previous page.”
- limitinteger“Results per page, 1 to 25.”
get_paperon 21 other serversreads or searches
“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.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
- idstringrequired“Paper id, e.g.”
list_storieson 9 other serversreads or searches
“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.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
7 inputs
- sincestring“Only stories published on or after this UTC date (YYYY-MM-DD).”
- untilstring“Only stories published on or before this UTC date (YYYY-MM-DD).”
- categoryarray“Category slug.”
- systemarray“Body system key (see `systems`).”
- study_typearray“Main source of evidence.”
- cursorstring“Opaque cursor from `pagination.next_cursor` of the previous page.”
- limitinteger“Results per page, 1 to 25.”
find_entitieson 6 other serversreads or searches
“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) …”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
4 inputs
- typestring“Entity type, e.g.”
- qstring“Match on name or key, case-insensitive substring.”
- cursorstring“Opaque cursor from `pagination.next_cursor` of the previous page.”
- limitinteger“Results per page, 1 to 25.”
get_entityon 45 other serversreads or searches
“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 spec…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
5 inputs, 2 required
- typestringrequired“Entity type.”
- keystringrequired“Entity key within its type.”
- min_relevancenumber“Lowest aging-relevance score for the papers listed.”
- cursorstring“Opaque cursor from `pagination.next_cursor` of the previous page.”
- limitinteger“Results per page, 1 to 25.”
list_claimson 14 other serversreads or searches
“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.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
7 inputs
- subjectstring“Subject text, entity name or entity key (case-insensitive substring).”
- objectstring“Object text, entity name or entity key (case-insensitive substring).”
- relationstring“Exact relation, e.g.”
- organismstring“Organism, e.g.”
- paper_idstring“Only claims from this paper.”
- cursorstring“Opaque cursor from `pagination.next_cursor` of the previous page.”
- limitinteger“Results per page, 1 to 25.”
list_trialson 1 other serverreads or searches
“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,…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
9 inputs
- qstring“Words that must all appear in the trial's titles, conditions, interventions, keywords or sponsor (case-insensitive).”
- phasearray“Phase: `1` (early phase 1 and phase 1), `2`, `3`, `4`, or `none` for studies with no phase.”
- statusarray“Recruitment status: `recruiting` (recruiting, not yet recruiting or by invitation), `active` (active, not recruiting), `completed`, or `stopped` (terminated, w…”
- focusarray“The trial's main connection to aging (see `focus`).”
- industryboolean“`true` for trials whose lead sponsor is a company, `false` for the rest.”
- sincestring“Only trials the registry updated on or after this date (YYYY-MM-DD).”
- min_relevancenumber“Lowest aging-relevance score to include (0 to 3, see `relevance`).”
- cursorstring“Opaque cursor from `pagination.next_cursor` of the previous page.”
- limitinteger“Results per page, 1 to 25.”
get_trialon 2 other serversreads or searches
“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 cit…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
- nct_idstringrequired“The trial's registry number, e.g.”
list_newson 11 other serversreads or searches
“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.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
5 inputs
- qstring“Words that must all appear in the story's headline or summary (case-insensitive).”
- kindstring“Only stories of this kind.”
- sincestring“Only stories with coverage on or after this UTC date (YYYY-MM-DD).”
- cursorstring“Opaque cursor from `pagination.next_cursor` of the previous page.”
- limitinteger“Results per page, 1 to 25.”
list_grantsreads or searches
“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.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
8 inputs
- qstring“Words of the grant's title ("quoted phrases", OR and -exclusions work).”
- entitystring“Only grants whose titles name this entity, as `type:key` (see /entities), e.g.”
- funderstring“Only grants from this funder, by its organization key or name, e.g.”
- holderstring“Only grants held by this organization (its key) or investigator (`person:` and their key), e.g.”
- sincestring“Only grants awarded on or after this date (YYYY-MM-DD).”
- untilstring“Only grants awarded on or before this date (YYYY-MM-DD).”
- cursorstring“Opaque cursor from `pagination.next_cursor` of the previous page.”
- limitinteger“Results per page, 1 to 25.”
list_conferenceson 2 other serversreads or searches
“Use this when the user asks which meetings on aging research and age-related disease are coming up, or which have just been held.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.

Show 14 more tools

get_conferenceon 2 other serversreads or searches
“Use this when the user asks about one meeting from list_conferences, or what was presented there.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
5 inputs, 1 required
- idstringrequired“Conference id from list_conferences, e.g.”
- editionstring“An edition from `editions`, e.g.”
- min_visibilitystring“With `edition`: which abstracts to list, from the most to the least worth reading: `core`, `visible`, `searchable`, `matchable`, `out`.”
- cursorstring“Opaque cursor from `pagination.next_cursor` of the previous page.”
- limitinteger“Results per page, 1 to 25.”
list_assetson 32 other serversreads or searches
“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.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
11 inputs
- targetstring“A target: a gene symbol or key (`GLP1R`, `bcl2l1`) or a process key (`mtor`, `cellular-senescence`).”
- mechanismstring“Words that must all appear in the asset's mechanism line (case-insensitive).”
- modalitystring“The kind of therapy (see `modality`).”
- hallmarkstring“A hallmark of aging the asset acts on.”
- indicationstring“A disease, by name or entity key (`idiopathic pulmonary fibrosis`, `alzheimer-disease`).”
- stagestring“Stage: with `indication`, the stage for that indication; otherwise the asset's furthest stage.”
- countrystring“The developer's country, ISO 3166 alpha-2 (`US`, `GB`, `CH`).”
- organisationstring“An organization key: the assets it develops, partners on or licensed out.”
- qstring“Letters and digits in any of the asset's names or code names (`UBX1325` matches UBX-1325).”
- cursorstring“Opaque cursor from `pagination.next_cursor` of the previous page.”
- limitinteger“Results per page, 1 to 25.”
get_asseton 28 other serversreads or searches
“Use this when the user asks about one drug or therapy program by its name or any code name (ubx1325, UBX-1325, BMS-986278).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
- keystringrequired“The asset's key or a code name.”
count_pipelinereads or searches
“Use this when the user asks how many drug and therapy programs there are, or how a field's pipeline splits.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
11 inputs
- bystring“What to group by.”
- targetstring“A target: a gene symbol or key (`GLP1R`, `bcl2l1`) or a process key (`mtor`, `cellular-senescence`).”
- mechanismstring“Words that must all appear in the asset's mechanism line (case-insensitive).”
- modalitystring“The kind of therapy (see `modality`).”
- hallmarkstring“A hallmark of aging the asset acts on.”
- indicationstring“A disease, by name or entity key (`idiopathic pulmonary fibrosis`, `alzheimer-disease`).”
- stagestring“Stage: with `indication`, the stage for that indication; otherwise the asset's furthest stage.”
- countrystring“The developer's country, ISO 3166 alpha-2 (`US`, `GB`, `CH`).”
- organisationstring“An organization key: the assets it develops, partners on or licensed out.”
- qstring“Letters and digits in any of the asset's names or code names (`UBX1325` matches UBX-1325).”
- limitinteger“Results per page, 1 to 25.”
followon 7 other serverscreates or changes datadescribed as changing data
“Use this when the user asks to follow a drug, gene, process, disease or other entity on AgingResearch.News, so its new papers reach them.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
2 inputs, 2 required
- typestringrequired“The entity's type, as find_entities or get_entity gives it.”
- keystringrequired“The entity's key within its type, such as rapamycin.”
unfollowon 3 other serversdeletesdescribed as changing data
“Use this when the user asks to stop following a drug, gene, process or other entity on AgingResearch.News.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
2 inputs, 2 required
- typestringrequired“The entity's type, as find_entities or get_entity gives it.”
- keystringrequired“The entity's key within its type, such as rapamycin.”
list_followson 3 other serversreads or searches
“Use this when the user asks what they follow on AgingResearch.News.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
list_questionson 10 other serversreads or searches
“Use this when the user asks about questions they asked AgingResearch.News (Ask) before.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
- limitinteger“How many, 1 to 25.”
open_arncontrols a browser or desktop
“Use this when the user asks to open AgingResearch.News or to see their feed, follows and recent questions in one place.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
- tabstring“Which feed to open on.”
list_feedon 2 other serversreads or searches
“The sidebar's feed: For you or Top, as story cards.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
- tabstring
search_arnreads or searches
“The sidebar's search: topics and papers matching words, as cards.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
- qstringrequired
ask_arngenerates content
“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 lif…”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
2 inputs, 1 required
- questionstringrequired“The research question in the user's words, in any language; the answer is written in the question's language.”
- conversation_idstring“To ask a follow-up in a conversation this tool or ask_arn started: its `conversation.id`.”
start_ultradeepgenerates content
“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.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
2 inputs, 1 required
- questionstringrequired“The research question in the user's words, in any language; the answer is written in the question's language.”
- conversation_idstring“To ask a follow-up in a conversation this tool or ask_arn started: its `conversation.id`.”
get_ask_answeron 1 other serverreads or searches
“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 …”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
- question_idintegerrequired“The question_id ask_arn or start_ultradeep gave.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does: 100% of 26 tools
Says what it returns: 92% of 26 tools
States limits, defaults or errors: 71% of 24 tools
Says when to use it: 100% of 26 tools
Items covered per tool: 3.6 of 4 on average

Counted from the listing

Parameters with a description: 98% of 112
Tools with a description: 100% of 26
Typical description length: 490 characters

The tool set

Counted from the listing

Tools: 26
Size of the list: about 11,889 tokens for an agent to load (characters ÷ 4)
Naming: 24 of 26 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 26 of 26 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-23 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai

Settings → Connectors → Add custom connector, then paste:
https://agingresearch.news/api/mcp

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

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

VS Code · .vscode/mcp.json

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

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"agingresearch-news","type":"http","url":"https://agingresearch.news/api/mcp"}'

Claude Code

claude mcp add --transport http agingresearch-news https://agingresearch.news/api/mcp

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 --server-url https://agingresearch.news/api/mcp --transport http

The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Remote endpoint agingresearch.news/api/mcp	Session opened	matches	our test · 2026-10-23
No credential declared as required	Opened a session without any credential	matches	our test · 2026-10-23

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: no public GitHub repository

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
Not metSource repository link opensThe registry entry gives no repository link.
Does not applyRepository is not archivedNo public GitHub repository to read.
Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about news.agingresearch/agingresearch-news

Answered from the data above

Is news.agingresearch/agingresearch-news safe to install?

We do not rate servers as safe or unsafe. 1 of its 2 applicable record checks are met (facts from public records, each listed on this page). What the records show: 2 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Is news.agingresearch/agingresearch-news free to use?

Its website (agingresearch.news/connect) describes a freemium pricing model. This is an AI-classified reading of the page on 2026-10-23, so check the page itself before relying on it.

Does news.agingresearch/agingresearch-news need an API key or sign-in?

It opened a session without any credential on 2026-10-23. The registry entry declares no required credential; no declaration is not a guarantee.

Has news.agingresearch/agingresearch-news been security tested?

Partly. 4 of the 15 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security verdict is published before verification.

What can news.agingresearch/agingresearch-news do?

It lists 26 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search, create or change data, delete, control a browser or desktop and generate content. We did not call any tool, so this describes the text, not the behaviour.

Can news.agingresearch/agingresearch-news change or delete data?

2 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: exercised
Fake assistant turns: not applicable
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not run · our policy
Consent handling: not testable from outside
Sign-in metadata: exercised

4 exercised11 not run (reason given)3 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 4 of the 15 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 4

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
12Hidden content
audience-hidingChecks resources that hide content from the user.exercised
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.exercised

Not run, with the reason · 11

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside

Does not apply to this server · 3

13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted a read-only session with the server's remote endpoint
581 msConnected after 0 redirects. No credential was sent or needed.
Read the inventory: 26 tools, 3 resources, 0 prompts.
4,880 msFinished: 4 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

no value

No value: the two AI models (Gemini and Claude) disagreed, so neither answer is shown.

Pricing modelAI-classified

freemium

read from agingresearch.news/connect · 2026-10-23

“Free Unlimited reading, 3 questions a day to Ask AgingResearch.News, 3 follows, 100 lookups a day in assistants.”

Programming language

does not apply

no existing GitHub repository (server declares no repository link, so there is nothing to fetch)

Hosting type

remote (hosted by the publisher)

registry · 2026-10-23

MCP capability

resources, tools, extensions

our test · 2026-10-23

Transport

streamable HTTP

registry · 2026-10-23

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

does not apply

remote-only server: no package is shipped, so there is no package registry

Freshness

0–30 days

registry updatedAt · 2026-10-23

Lifecycle status

active

registry · 2026-10-23

License class

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Integrity hash

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Signature / provenance

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Dependency advisories

does not apply

ships no package, so there are no dependencies to audit

Popularity

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Publisher signals

not stated

no readable GitHub owner to describe

Maintenance

does not apply

server declares no repository link, so there is nothing to fetch

Environment

the publisher's infrastructure

where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “news.agingresearch/agingresearch-news: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/news.agingresearch/agingresearch-news

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/news.agingresearch/agingresearch-news)](https://protocolprobe.com/mcp/servers/news.agingresearch/agingresearch-news)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology