SaSameAgentAudit

What this client asked www.pathwren.workers.dev for, when, and what it got. Every number below is from this host's own server-side request log, 2026-09-01 01:06:44Z to 2026-09-02 01:40:11Z UTC.

SaSameAgentAudit/0.1 (+https://live-vps.sasame.online/.well-known/agent-card.json)

12 request(s) from 1 distinct address(es), 7 distinct path(s), first seen 2026-09-01 01:06:44Z, last seen 2026-09-02 01:40:11Z UTC. 3 separate visit(s), counting a gap of more than 30 minutes as a new one, median 736.8 minutes between them.

The user-agent strings, exactly as they arrived

user-agentrequestsaddressesfirst seenlast seen
SaSameAgentAudit/0.1 (+https://live-vps.sasame.online/.well-known/agent-card.json)1212026-09-01 01:06:44Z2026-09-02 01:40:11Z

What it asked for, in the order it asked

First request to each path, oldest first.

#pathat (UTC)status
1/mcp2026-09-01 01:06:44Z200
2/.well-known/agent-card.json2026-09-01 01:06:44Z200
3/c/mcp-registry-official/mcp/doctor2026-09-01 13:11:12Z200
4/c/mcp-registry-official/mcp2026-09-01 13:39:09Z200
5/c/mcp-registry-official/mcp/triage2026-09-01 13:39:11Z200
6/c/mcp-registry-official/mcp/netcheck2026-09-02 01:40:09Z200
7/c/mcp-registry-official/mcp/robots2026-09-02 01:40:11Z200

Everything it asked for

pathrequestsstatus codesfirstlast
/.well-known/agent-card.json6200×5, 404×12026-09-01 01:06:44Z2026-09-02 01:40:11Z
/c/mcp-registry-official/mcp1200×12026-09-01 13:39:09Z2026-09-01 13:39:09Z
/c/mcp-registry-official/mcp/doctor1200×12026-09-01 13:11:12Z2026-09-01 13:11:12Z
/c/mcp-registry-official/mcp/netcheck1200×12026-09-02 01:40:09Z2026-09-02 01:40:09Z
/c/mcp-registry-official/mcp/robots1200×12026-09-02 01:40:11Z2026-09-02 01:40:11Z
/c/mcp-registry-official/mcp/triage1200×12026-09-01 13:39:11Z2026-09-01 13:39:11Z
/mcp1200×12026-09-01 01:06:44Z2026-09-01 01:06:44Z

What it asked for that did not exist

path it asked forwhat it gotfirst askedsince then
/.well-known/agent-card.json404×12026-09-01 01:06:44Zanswers 200 since 2026-09-01 01:28:42Z

What it got, and what it sent

Status codes
200×11, 404×1
Accept headers
*/*
Bytes served
66577
Attributed to a channel
mcp-registry-official (5), mcp-registry (1)
Our instrument classed it
agent×12 — that is our classifier's label from the user-agent, not the operator's, and it has been wrong before.

How to verify it is really them

Not observed. This client publishes no address list we could read and no reverse-DNS convention we could test, so the user-agent is the only identity it has here — and a user-agent is a claim, not a proof. Anyone can send this string.

What it publishes about you afterwards

Not observed. We have not seen this client publish a grade, a listing or a record about this host anywhere, and we make no claim that it does or does not.

Its own documentation

It names https://live-vps.sasame.online/.well-known/agent-card.json in its own user-agent. That is the operator's own claim about itself; we neither endorse nor verify what is on it.

This page as data

curl -s https://www.pathwren.workers.dev/bot/sasameagentaudit.json
curl -s https://www.pathwren.workers.dev/data/observed-clients.json   # every client, one request

JSON · markdown · all clients seen here · index as JSON · check a crawler yourself, no key

Method, and what this page will not say

Rows come from a server-side log written before anything is served, so clients that run no JavaScript are counted exactly like browsers. The window is the whole life of the log, 2026-09-01 01:06:44Z to 2026-09-02 01:40:11Z UTC, and it is stated on every number because a count without a window is not a fact. Addresses are stored as salted hashes and counted, never printed. Our own checks send X-Self: 1 and are excluded, together with every request the analyst flagged as one of our own agents reaching for a URL through a model provider's fetch tool (the numbers are on the index). Nothing here is a claim about intent: where this page does not know something it says not observed.