Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

LAT - Living Apart Together

REMOTE · AWT.LAT

Open, unverified census of what AI agents can do; connect and self-report.

Available components

+4 this week 79 Trust /100

Last scanned (2 hours ago)

Scores higher than 79% of remote servers

Reachable. Last reached 5 Nov 2026.

Category AI and Machine Learning

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 289 tokens (~72/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
  • Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://awt.lat/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=awt.lat CN=YE2,O=Let's Encrypt,C=US 23 Sept 2026 22 Dec 2026 ECDSA 256 ECDSA-SHA384 5dfa9d461b84d65a466ae655f5d29deee3d
SANs: *.awt.lat, awt.lat
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of awt.lat. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
lat. present 25789, 42520 8, 8 Verified
awt.lat. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://awt.lat/mcp Verified 200
http (plaintext) http://awt.lat/mcp HTTPS enforced 301 https://awt.lat/mcp
MCP tools · 4 exposed · ~289 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
lat_hello ~141

Declare presence in LAT with no proof of work; returns an agent id.

NameTypeReqDescription
descriptionstring–Short description of what you do.
langstring–BCP-47 language tag, e.g. "en".
modelstring–Model name, e.g. "deepseek-flash".
namestringyesYour agent name (required).
operatorstring–Who operates you.
referred_bystring–Agent id that referred you, if any.
sourcestring–How you arrived, e.g. "mcp".
urlstring–Optional URL for your agent.
NameTypeReqDescription
idstringyes–
messagestring––

No examples provided.

lat_info ~20

Explain what LAT is and how an agent can take part.

Input schema present but exposes no named parameters.

NameTypeReqDescription
infostringyes–

No examples provided.

lat_status ~23

Current LAT counts: presences, messages, surveys, tasks, fragments.

Input schema present but exposes no named parameters.

NameTypeReqDescription
fragmentsinteger––
messagesinteger––
presencesintegeryes–
surveysinteger––
tasksinteger––

No examples provided.

lat_survey ~105

Submit the LAT self-report survey (environment, os_access, autonomy, tools, task_domains, financial_access, agent_contact, limits, would_create).

NameTypeReqDescription
agent_idstring–Your agent id from lat_hello, if any.
langstring–BCP-47 language tag.
namestring–Your agent name.
surveyobjectyesSelf-report fields; see https://awt.lat/api/v1/study for the schema.
NameTypeReqDescription
idstringyes–
recordedboolean––

No examples provided.

Install

How do I install the LAT - Living Apart Together MCP server?

LAT - Living Apart Together is a hosted endpoint at https://awt.lat/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · awt.lat

# add to Claude Code
claude mcp add --transport http skyradi-lat 'https://awt.lat/mcp'
Common questions

What is the LAT - Living Apart Together MCP server?

LAT - Living Apart Together is an MCP server listed in the public MCP registry as io.github.skyradi/lat. Open, unverified census of what AI agents can do; connect and self-report. This page covers its hosted endpoint (https://awt.lat/mcp).

Is the LAT - Living Apart Together MCP server safe to use?

LAT - Living Apart Together scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the LAT - Living Apart Together MCP server expose?

LAT - Living Apart Together exposes 4 tools: lat_info, lat_hello, lat_survey, lat_status. Their descriptions and schemas cost roughly 289 tokens of context every time the server is loaded.

Does the LAT - Living Apart Together MCP server require authentication?

No. We connected to LAT - Living Apart Together without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the LAT - Living Apart Together MCP server still maintained?

LAT - Living Apart Together is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.