# aisec-registry

What this client asked https://www.pathwren.workers.dev for, from that host's own request log.
Window: 2026-09-01 09:17:24Z to 2026-09-13 18:50:10Z UTC. Generated 2026-09-14.

## User-agent strings, exactly as they arrived

- `aisec-registry/0.2 (+https://sec.sqrx.io)` — 855 request(s), 24 address(es), 2026-09-01 09:17:24Z to 2026-09-13 18:50:10Z

- Requests: 855
- Distinct addresses (salted hashes, never published): 24
- Distinct paths: 29
- Visits (30-minute gap rule): 14
- Status codes: 200×457, 404×398
- Accept headers: application/json, application/json, text/event-stream
- Our classifier called it: agent×855 (ours, from the user-agent)

## What it asked for, in order

1. `/c/mcp-registry-official/mcp/doctor/.well-known/oauth-authorization-server` — 2026-09-01 09:17:24Z — 404
2. `/c/mcp-registry-official/mcp/doctor/.well-known/oauth-protected-resource` — 2026-09-01 09:17:24Z — 404
3. `/c/mcp-registry-official/mcp/doctor/.well-known/mcp` — 2026-09-01 09:17:24Z — 200
4. `/c/mcp-registry-official/mcp/doctor` — 2026-09-01 09:17:24Z — 200
5. `/c/mcp-registry-official/mcp/.well-known/oauth-authorization-server` — 2026-09-01 09:17:24Z — 404
6. `/mcp` — 2026-09-01 09:17:24Z — 200
7. `/c/mcp-registry-official/mcp/.well-known/oauth-protected-resource` — 2026-09-01 09:17:24Z — 404
8. `/c/mcp-registry-official/mcp/.well-known/mcp` — 2026-09-01 09:17:24Z — 200
9. `/c/mcp-registry-official/mcp` — 2026-09-01 09:17:24Z — 200
10. `/c/mcp-registry-official/mcp/triage/.well-known/oauth-authorization-server` — 2026-09-01 09:17:24Z — 404
11. `/c/mcp-registry-official/mcp/triage/.well-known/oauth-protected-resource` — 2026-09-01 09:17:25Z — 404
12. `/c/mcp-registry-official/mcp/triage/.well-known/mcp` — 2026-09-01 09:17:25Z — 200
13. `/c/mcp-registry-official/mcp/triage` — 2026-09-01 09:17:25Z — 200
14. `/c/mcp-registry-official/mcp/netcheck/.well-known/oauth-authorization-server` — 2026-09-02 09:13:54Z — 404
15. `/c/mcp-registry-official/mcp/netcheck/.well-known/oauth-protected-resource` — 2026-09-02 09:13:54Z — 404
16. `/c/mcp-registry-official/mcp/netcheck/.well-known/mcp` — 2026-09-02 09:13:55Z — 200
17. `/c/mcp-registry-official/mcp/netcheck` — 2026-09-02 09:13:55Z — 200
18. `/c/mcp-registry-official/mcp/robots/.well-known/oauth-authorization-server` — 2026-09-02 09:13:55Z — 404
19. `/c/mcp-registry-official/mcp/robots/.well-known/oauth-protected-resource` — 2026-09-02 09:13:55Z — 404
20. `/c/mcp-registry-official/mcp/robots/.well-known/mcp` — 2026-09-02 09:13:55Z — 200
21. `/c/mcp-registry-official/mcp/robots` — 2026-09-02 09:13:55Z — 200
22. `/c/mcp-registry-official/mcp/lint/.well-known/oauth-authorization-server` — 2026-09-03 09:20:09Z — 404
23. `/c/mcp-registry-official/mcp/lint/.well-known/oauth-protected-resource` — 2026-09-03 09:20:09Z — 404
24. `/c/mcp-registry-official/mcp/lint/.well-known/mcp` — 2026-09-03 09:20:09Z — 200
25. `/c/mcp-registry-official/mcp/lint` — 2026-09-03 09:20:09Z — 200
26. `/c/mcp-registry-official/mcp/markdown/.well-known/oauth-authorization-server` — 2026-09-06 09:27:44Z — 404
27. `/c/mcp-registry-official/mcp/markdown/.well-known/oauth-protected-resource` — 2026-09-06 09:27:44Z — 404
28. `/c/mcp-registry-official/mcp/markdown/.well-known/mcp` — 2026-09-06 09:27:44Z — 200
29. `/c/mcp-registry-official/mcp/markdown` — 2026-09-06 09:27:44Z — 200

## What it asked for that did not exist

- `/c/mcp-registry-official/mcp/doctor/.well-known/oauth-authorization-server` — 404×30 — first asked 2026-09-01 09:17:24Z; still absent
- `/c/mcp-registry-official/mcp/doctor/.well-known/oauth-protected-resource` — 404×29 — first asked 2026-09-01 09:17:24Z; still absent
- `/c/mcp-registry-official/mcp/doctor/.well-known/mcp` — 404×3 — first asked 2026-09-01 09:17:24Z; answers 200 since 2026-09-02 00:16:03Z
- `/c/mcp-registry-official/mcp/.well-known/oauth-authorization-server` — 404×34 — first asked 2026-09-01 09:17:24Z; still absent
- `/c/mcp-registry-official/mcp/.well-known/oauth-protected-resource` — 404×34 — first asked 2026-09-01 09:17:24Z; still absent
- `/c/mcp-registry-official/mcp/.well-known/mcp` — 404×3 — first asked 2026-09-01 09:17:24Z; answers 200 since 2026-09-02 00:16:03Z
- `/c/mcp-registry-official/mcp/triage/.well-known/oauth-authorization-server` — 404×39 — first asked 2026-09-01 09:17:24Z; still absent
- `/c/mcp-registry-official/mcp/triage/.well-known/oauth-protected-resource` — 404×38 — first asked 2026-09-01 09:17:25Z; still absent
- `/c/mcp-registry-official/mcp/triage/.well-known/mcp` — 404×3 — first asked 2026-09-01 09:17:25Z; answers 200 since 2026-09-02 00:16:03Z
- `/c/mcp-registry-official/mcp/netcheck/.well-known/oauth-authorization-server` — 404×26 — first asked 2026-09-02 09:13:54Z; still absent
- `/c/mcp-registry-official/mcp/netcheck/.well-known/oauth-protected-resource` — 404×26 — first asked 2026-09-02 09:13:54Z; still absent
- `/c/mcp-registry-official/mcp/robots/.well-known/oauth-authorization-server` — 404×27 — first asked 2026-09-02 09:13:55Z; still absent
- `/c/mcp-registry-official/mcp/robots/.well-known/oauth-protected-resource` — 404×27 — first asked 2026-09-02 09:13:55Z; still absent
- `/c/mcp-registry-official/mcp/lint/.well-known/oauth-authorization-server` — 404×25 — first asked 2026-09-03 09:20:09Z; still absent
- `/c/mcp-registry-official/mcp/lint/.well-known/oauth-protected-resource` — 404×26 — first asked 2026-09-03 09:20:09Z; still absent
- `/c/mcp-registry-official/mcp/markdown/.well-known/oauth-authorization-server` — 404×14 — first asked 2026-09-06 09:27:44Z; still absent
- `/c/mcp-registry-official/mcp/markdown/.well-known/oauth-protected-resource` — 404×14 — first asked 2026-09-06 09:27:44Z; still absent

## Verification

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.

## Ask this page a question, with one GET

A question about this page, answered by a call you can make right now — no key, no account, no JSON-RPC, nothing to assemble. The query string is already filled in with this page's own subject.

- **What is aisec-registry/0.2 (+https://sec.sqrx.io)?**  
  `curl -s 'https://www.pathwren.workers.dev/tools/classify-ua?ua=aisec-registry%2F0.2%20%28%2Bhttps%3A%2F%2Fsec.sqrx.io%29&s=client-dossiers'`  
  This exact user-agent run through the catalogue: which crawler it is, who operates it, what the crawl is for, what blocking it costs — or an honest "not recognised" if it is nobody we know.

Every parameter above is a value the endpoint reads, not an address it visits: nothing is fetched on your behalf. Called without any parameter, each endpoint returns its own specification instead of an error.


## What it publishes about you

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.

## Documentation it names

https://sec.sqrx.io

JSON: https://www.pathwren.workers.dev/bot/aisec-registry.json · all clients: https://www.pathwren.workers.dev/data/observed-clients.json