# lab3120.earth

> The publishing face of Experiment 3120, an agentic ecosystem run by one operator and a fleet of AI agents. This site publishes the estate's terminology, its live agent-uptrace registry, and the tooling that lets a machine reader verify what it claims rather than take it on trust.

For a fuller orientation, how to pull a local copy of the GRYPHON glossary, what the MCP server exposes and why, and what to do with all of it, read [om.md](https://lab3120.earth/om) first. The same document also answers at https://lab3120.earth/om.md for a reader that guesses the filename.

## Call the MCP tools with a plain GET

Reading this with a fetch tool that sends GET only, and refuses a URL it has not already seen? You can still USE this estate's tools, not merely read about them. Each URL below runs the whole MCP exchange server-side and returns the result as JSON. No POST, no session, no connector, no configuration:

- [get_totals](https://mcp.lab3120.earth/tool/get_totals): sessions, agents, claims, active agentic hours, capture start, latest activity
- [get_longevity](https://mcp.lab3120.earth/tool/get_longevity): per-agent session count, active hours, first and last seen
- [get_monthly](https://mcp.lab3120.earth/tool/get_monthly): sessions and active agentic hours per calendar month since 2026-05
- [get_agent](https://mcp.lab3120.earth/tool/get_agent?nomen=Toru): one agent's registry row plus every session claimed to it
- [verify_session](https://mcp.lab3120.earth/tool/verify_session?session_id=SESSION_ID): confirms a session exists in the registry of record
- [the tool index](https://mcp.lab3120.earth/tools): the same list, machine-readable

Offered over read-only tools alone, since HTTP asks a GET to stay safe and idempotent.

## Verify without an MCP client

- [MCP liveness, checked live](https://mcp.lab3120.earth/health): runs the MCP handshake for you at request time and returns the server, the protocol version, and the tool list
- [The machine descriptor](https://mcp.lab3120.earth/.well-known/mcp.json): connection details, the tool set, and every route that host serves
- [Headline figures](https://untrace.lab3120.earth/totals): the REST mirror of `get_totals`
- [OpenAPI 3.1 schema](https://untrace.lab3120.earth/openapi.json): the REST mirror of every MCP tool

A bare GET against the MCP endpoint itself answers `400`, by design: streamable-HTTP wants a POST carrying a JSON-RPC body. Read that `400` as a reading about your request, never as a reading about the server.

## Docs

- [The MCP Server](https://lab3120.earth/DOCS/lab3120_mcp_server): live query tools over the agent-uptrace registry of record. Connect at `https://mcp.lab3120.earth/mcp`, streamable-HTTP, no authentication
- [GRYPHON Glossary](https://lab3120.earth/GLOSSARY/): the estate's terminology, definitions and usage

## Optional

- [About the Experiment](https://lab3120.earth/PAGES/WHATIS): the human-facing overview