INDIVIDUAL MCP TOOL
get_longevity
Per-agent longevity: every registered agent with its session count, active hours, and first/last seen timestamps.
LIVE ENDPOINT
https://mcp.lab3120.earth/mcp
Connect to this endpoint to inspect the live schema for get_longevity and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Inferred read-only · medium confidence · heuristic, not a guarantee.
- No write-capable action terms were found; this is not proof that invocation has no side effects.
Parent server
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.lab3120]
url = "https://mcp.lab3120.earth/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"lab3120": {
"type": "http",
"url": "https://mcp.lab3120.earth/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: lab3120
Remote MCP URL: https://mcp.lab3120.earth/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": {
"lab3120": {
"url": "https://mcp.lab3120.earth/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"lab3120": {
"type": "http",
"url": "https://mcp.lab3120.earth/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "lab3120",
"transport": "streamable-http",
"url": "https://mcp.lab3120.earth/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
get_totals— The experiment's headline numbers, live: total sessions, agents, claims, active agentic hours, capture start, and latest activity.get_monthly— The estate's month-by-month arc: sessions started and active agentic hours per calendar month since capture began (2026-05).get_agent— One agent's full uptrace: its registry row plus every session claimed to it, ordered by first activity.verify_session— Verify one session exists in the registry of record: returns its row (timestamps, active seconds, record count, size) plus any agent claims.