hultra-link

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-08-31 22:10:04Z to 2026-09-01 03:10:04Z UTC.

hultra-link/1.0 (+https://donnees.hultra.link/sondes.md)

6 request(s) from 2 distinct address(es), 6 distinct path(s), first seen 2026-08-31 22:10:04Z, last seen 2026-09-01 03:10:04Z UTC. 4 separate visit(s), counting a gap of more than 30 minutes as a new one, median 60.0 minutes between them.

The user-agent strings, exactly as they arrived

user-agentrequestsaddressesfirst seenlast seen
hultra-link/1.0 (+https://donnees.hultra.link/sondes.md)622026-08-31 22:10:04Z2026-09-01 03:10:04Z

What it asked for, in the order it asked

First request to each path, oldest first.

#pathat (UTC)status
1/mcp2026-08-31 22:10:04Znot recorded
2/c/mcp-registry-official/mcp2026-09-01 01:10:01Z200
3/c/mcp-registry-official/mcp/triage2026-09-01 02:10:04Z200
4/a2a2026-09-01 03:10:04Z200
5/c/mcp-registry-official/mcp/doctor2026-09-01 03:10:04Z200
6/.well-known/agent-card.json2026-09-01 03:10:04Z200

Everything it asked for

pathrequestsstatus codesfirstlast
/.well-known/agent-card.json1200×12026-09-01 03:10:04Z2026-09-01 03:10:04Z
/a2a1200×12026-09-01 03:10:04Z2026-09-01 03:10:04Z
/c/mcp-registry-official/mcp1200×12026-09-01 01:10:01Z2026-09-01 01:10:01Z
/c/mcp-registry-official/mcp/doctor1200×12026-09-01 03:10:04Z2026-09-01 03:10:04Z
/c/mcp-registry-official/mcp/triage1200×12026-09-01 02:10:04Z2026-09-01 02:10:04Z
/mcp1not recorded×12026-08-31 22:10:04Z2026-08-31 22:10:04Z

What it asked for that did not exist

Nothing. Every path it asked for existed at the time it asked.

What it got, and what it sent

Status codes
200×5, not recorded×1
Accept headers
application/json, text/event-stream, application/json
Bytes served
17273
Attributed to a channel
mcp-registry-official (3), mcp-registry (1)
Our instrument classed it
agent×6 — 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.

Checked 2026-09-01 against https://donnees.hultra.link/latest.json.

What it publishes about you afterwards

It publishes a listing. https://donnees.hultra.link/latest.json carried two of our records (ai-crawler-index, crawler-log-triage) when we fetched it at 2026-09-01T02:52Z, 23 minutes after we published a record to the official MCP registry.

Checked 2026-09-01 against https://donnees.hultra.link/latest.json.

Its own documentation

It names https://donnees.hultra.link/sondes.md 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/hultra-link.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

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-08-31 22:10:04Z to 2026-09-01 03:10:04Z 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.