Impact

Who CollectSEA reaches, and how it is used

Live numbers, counted without cookies or personal identifiers. They’re shown exactly as measured, small numbers included, so anyone can cite and check them.

Last 30 days

Detailed tracking began ; earlier days show zero.

People reached
1,079
Daily unique visitors, summed
Countries
73
Where visitors came from
Designs analyzed
24
by 12 visitor-days
API & MCP calls
92
6 from AI agents via MCP
Dataset downloads
51
JSON, CSV and JSONL files
Read through AI assistants
46
Pages ChatGPT or Claude fetched to answer someone

Daily visitors

Unique visitors per day (UTC)

Daily visitors: 1,079 visitors over 30 days, peak 144 on Oct 2.Tap a day or use the arrow keys to inspect.

Show as table
Day (UTC)visitors
2026-09-190
2026-09-200
2026-09-210
2026-09-220
2026-09-230
2026-09-240
2026-09-250
2026-09-260
2026-09-270
2026-09-280
2026-09-290
2026-09-300
2026-10-01116
2026-10-02144
2026-10-0367
2026-10-04140
2026-10-05138
2026-10-06137
2026-10-0786
2026-10-0866
2026-10-09138
2026-10-1028
2026-10-116
2026-10-122
2026-10-133
2026-10-141
2026-10-152
2026-10-163
2026-10-172
2026-10-180

Designs analyzed per day

Web, API and MCP analyses

Designs analyzed per day: 24 analyses over 30 days, peak 7 on Oct 1.Tap a day or use the arrow keys to inspect.

Show as table
Day (UTC)analyses
2026-09-190
2026-09-200
2026-09-210
2026-09-220
2026-09-230
2026-09-240
2026-09-250
2026-09-260
2026-09-270
2026-09-280
2026-09-290
2026-09-300
2026-10-017
2026-10-023
2026-10-031
2026-10-040
2026-10-050
2026-10-061
2026-10-070
2026-10-080
2026-10-092
2026-10-100
2026-10-111
2026-10-120
2026-10-130
2026-10-140
2026-10-153
2026-10-166
2026-10-170
2026-10-180

How it is used

Breakdowns for the last 30 days.

From visit to safeguards

Website, last 30 days. Typing and example runs are counted since October 10, 2026.

  • Visitors1,079
  • Started describing a system1
  • Ran an example6
  • Analyses on the website15
  • Exports and copies0

Analyses by channel

  • Website15
  • REST API9

Countries

  • United States286
  • Brazil118
  • Singapore66
  • Canada56
  • Germany53
  • South Korea45
  • Hong Kong42
  • Japan34

AI clients connected over MCP

From the client name sent when connecting

  • glama13
  • brickbluebot6
  • agent-collector5
  • agentrank-probe5
  • mcpbeat5
  • verifymcp-probe3
  • codexguild-catalog-review2
  • mcp2

Exports for teams and agents

No exports in this period yet.

Referring sites

  • google.com2
  • google.cg1
  • google.gr1
  • facebook.com1

Search and AI crawlers

Indexing visits by search engines and AI assistants

  • Other automated2,813
  • Meta750
  • Google614
  • OpenAI GPTBot323
  • ChatGPT search88
  • ChatGPT (on request)46
  • Perplexity3
  • Anthropic ClaudeBot2

All time

Counters kept since the platform launched in 2026.

Designs analyzed
119
MCP tool calls
9
Visitors since detailed tracking
1,079
Feedback messages
1

Service status

Health of the API and the advisory feeds that keep the corpus current.

API
Operational
Corpus version
2026.10.17
Last feed sync
Records served
1,649
Release
2026.10.17-seo-visuals

Machine-readable: /api/health

Advisory feeds

No complete refresh in the last six hours.

SourceStatusLast success
GitHub Security Advisoriesok
CISA Known Exploited Vulnerabilitiesok
NIST National Vulnerability Databasefailing (2×)
OSV — AI and agent SDK advisoriesok

How we count without tracking anyone

No cookies, no fingerprinting scripts and no third-party analytics. This is everything that happens to a visit.

What happens to a visit

Scroll the diagram sideways to see every system.

15 / 15 s

At midnight the secret is thrown away, so yesterday’s hashes can’t be tied to anyone, even by us.

  1. A visit reaches the nearest edge server.
  2. The server mixes the IP address and browser with a secret that exists only today, and keeps a one-way hash.
  3. Only counts are kept. The IP address is never written down.
  4. Crawlers, and anyone with Do Not Track or Global Privacy Control on, are not counted as visitors.
  5. At midnight the secret is thrown away, so yesterday’s hashes can’t be tied to anyone, even by us.
  • People reachedOne per person per day. Someone who visits on three different days counts three times, because days can’t be linked together.
  • Designs analyzedEvery finished analysis, whether it came from this website, the API or an AI assistant over MCP. The text you typed is never kept.
  • Countries and referrersCountries come from Cloudflare’s location data and are stored only as totals. Referring sites are cut down to the domain name.
  • Bots left outCrawlers, uptime monitors and internet-wide security scanners are counted separately and never as visitors, analyses or AI clients. Visitors with Do Not Track or Global Privacy Control on aren’t counted at all.
  • Erring on the low sideEach server saves its counts every few seconds, so a restart can drop a handful. If anything, the true numbers are slightly higher.

Questions about these figures? Get in touch.