io.github.Philongevity/phi-longevity-prism (/mcp)
MCP server · philongevity.com · found in a public list · checked since 2026-10-17
Live, handshake completed · latest check
https://philongevity.com/mcp MCP endpoint (Streamable HTTP)The name is the registry's label, not ours. Not reviewed by a person. See 4 endpoints from philongevity.com.
Our checks
An unpaid request weekly, from eastern North AmericaLast 3 checks, oldest to newest; room for 27 more
3 passed, 0 failed, 27 not run.
Checked weekly. Weekly: fewer than 5 payers, or no usage figure.
Details
Tools listed by the server
analyze_biomarkerscheck_care_gapsfull_prism_reportget_methodologyhow_to_get_started_for_my_ownerlist_supported_biomarkersquick_checksample_prism_report
- Tools
- 8
- This list since
- 2026-10-20
- First listed to us
- 2026-10-20
- List changes, 90 days
- 0
Names as the server reported them at our latest completed handshake (mcp-handshake/2); a listed tool is not a tested one. Definitions
Access
- Our latest check
- Nothing asked
- Stated
- not stated
- Payment model
- not known
- Currency
- not known
"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions
Listing
In the capability tree: Other (not placed in a branch yet) (primary). Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/3, tree/3) on 2026-10-18. Wrong place? Tell us.
In the index only: does not meet every one of our listing criteria (listing-criteria/6): ✗ what it does is unclear to our placement; ✓ its latest check passed. One other listing has the same address apart from a tracking parameter, a trailing slash or a similar detail; it stays in the index with its own checks: https://philongevity.com/mcp?src=awesome.
Recent probes
| When | Result | Time to headers |
|---|---|---|
cloudflare:EWR |
Live, handshake completed HTTP 200 | 539 ms |
cloudflare:MIA |
Live, MCP endpoint answered HTTP 405 | 1002 ms |
cloudflare:MIA |
Live, MCP endpoint answered HTTP 405 | 384 ms |
What these figures do not show
- A passing check means the server completed the MCP handshake with us (initialize, then tools/list, with no credentials; mcp-handshake/2) or asked for credentials first (HTTP 401). It does not show that the server's tools work or what they return. Tool names are as the server listed them.
- Listed in the Official MCP Registry; this data comes from the Official MCP Registry. Its listing's description is not republished.
- Limited evidence: monitored for 5 days (less than 30).
Something wrong here?
Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.
Machine-readable: /api/v1/services/cand_f75dbca88688a3f8