Control center Live research desk

Connecting to edge

— this UTC hour Field map

Observations / overview

Every capture.
A little more understood.

Your observed field, measured in daily HMAC nickname-days. The same client tomorrow creates another nickname — not another proven machine.

Open Research Explorer ↗Capture ledger ↗Open hypothesis lab ↗Waiting for the first desk response
Accumulated nickname-days — Observed locally, not a global population
— of 100,000

Baseline 77 first-seen / hour.

Doors on the internet — Live listings and intakes

Waiting doors are not in this number.

Live now — Nicknames in the last 15 minutes

If this is high and total is flat, the same agents are talking again.

Historic in window — Earlier nicknames

Not events. One nickname can send many requests.

Gap to 100k — calendar days at baseline

Smithery listing is paused above 15k so a 6h pack can be scored.

How the count is built

Live and historic can overlap when the same nickname comes back.

  • Live only 0
  • Returned 0
  • Historic only 0
  • Events 0

Figure 1b · Entry locations

Where agents enter the doors

Coarse Cloudflare country and colo. Not a street address. IP and user-agent are discarded.

Unique-seen / hour — recapture this UTC hour · not first-seen
Doors converting — intakes with events
Entries — hops or door hits

    Figure 2 · Pre-registered trials

    Experiments running at once

    One treatment on the Smithery fleet at a time. Peeking at unique every two minutes is not a result. Pass and fail were written before the window opened.

      Figure 3 · Hourly activity

      Unique nicknames by UTC hour

      Columns are unique-seen that hour (recapture of today’s HMAC counts). The line is the same series. First-seen, when the new census is populated, is a separate series: new nickname-days only.

      Figure 4 · Path to 100,000

      What the current rate implies

      Measuring the path to 100,000 unique agents…

      Seen so far 0 of 100,000 unique agents
      This pace in 72h — agents / hour × 72
      Doors needed — MCP-hot doors, not silent listings
      Converting now — intakes that actually received agents

      Figure 5 · Who is at the door

      Provider, not catalog prefix

      Two layers. MCP runtime is initialize clientInfo.name. HTTP operator is an allowlisted User-Agent family. Raw UA and IP are discarded. /c/cursor is a listing path, not Cursor the product.

      MCP runtime

        HTTP operator

          Scanner / crawler tasks

          Family labels and protocol shape only. Handshake identified (smithery/inspector) is not whoClass identified. Series stay in their own columns.

          Family whoClass Inferred task Door cluster Count Evidence Series

          Figure 6 · Converting doors

          Which doors convert

          Bar length is unique agents that hit that intake. Converting means live with events, not first-seen. Factory silent doors stay in the summary.

            Figure 7 · Named MCP servers

            Independently listed intakes

            Each has its own converting /s/{slug}/mcp door.

              Figure 8 · Protocol and request shape

              What they do once inside

              Furthest MCP stage each nickname reached. Bodies and prompts are not stored.

              Signals

              Protocol stage, allowlisted client family, UA family, and coarse request shape.

              Figure 9 · Growth engine

              What the engine is doing now

              From 15k to 100k: one useful 24-pack, then a 6h measure. Dumps stay off. Worker listing is paused above 15k.

              Decision — waiting for a desk snapshot
              Unique vs last wave — baseline is the last published wave
              Last wave — no official-registry wave yet
              Kill switch ON Paid throttle publishes siblings for discovery. Unique nicknames still gate honesty.
              Learned cooldown 45m floor 30 · ceiling 75 · from the unique curve
              Neglected channels — floor 500 unique/hr · advertise neglected channels

              Where nicknames come from

                Next slugs

                  Method

                  What we are actually measuring

                  Unique is a daily rotating nickname, not a door-hit. Indexes find a door, handshake, list tools, and almost never call one. We never GET our own intakes.