DEV Community

Cover image for Catalogue process. Snapshot memory.
Alex
Alex

Posted on Originally published at modeldev.modelmarket.dev

Catalogue process. Snapshot memory.

Two new rooms — HESTIA hearth and HISTOR record

Most agent posts sell a chat window with plugins.

AIMarket keeps shipping rooms: a factory that builds, a Hub that lists and settles, desks that refuse poisoned tools. Two newer rooms close gaps the earlier map left open —

HESTIA is the hearth: where a seller process actually runs.

HISTOR is the record: what remote MCP endpoints advertised in tools/list, signed and dated.

Crypto stays off the titles. The shape is deploy → announce → receipt, and observe → digest → diff.

Live map: modeldev.modelmarket.dev · Monorepo: github.com/alexar76/aicom


The hole a catalogue cannot fill

A Hub row answers what can a buyer find. It does not answer is a process listening on a stable URL right now.

create-aimarket-agent scaffolds a signed Protocol v2 provider on disk. Until something hosts it, nobody is listening. A forgotten tmux on a laptop is not a market.

HESTIA is that host. Isolated process. Stable /t/{slug}. Ed25519 at the edge. Announce to the Hub only when you ask — never as a trust grant.

HESTIA live landing — hosting control plane

Reference hearth: hestia.modelmarket.dev · Source: github.com/alexar76/hestia (MIT)

Today the public roster is not empty. Three tenants are running on the reference hearth — commit-reveal referee, canonical JSON, policy decide — each with a public URL. announced: false on purpose until someone knocks. Empty roster means nothing is hosted here, not the market is empty.

HESTIA console — deploy is a write; roster is public

Deploy ≠ list

Step What it is
Scaffold CLI / Factory → signed bundle on disk
Deploy POST onto a Hestia hearth → process behind /t/{slug}
Admit (optional) THEMIS can refuse a start
Announce Explicit knock. Hub may crawl. Not a trust badge.
Buy Hub catalogue + receipt — still the till

Do not paste a deploy token into the public reference /ui/ unless you operate that host. Self-host with your own token. Workshop: ninety minutes at your console — docs/workshop.

export HESTIA_DEPLOY_TOKEN=$(python3 -c 'import secrets; print(secrets.token_urlsafe(24))')
# from the hestia/ tree
uv sync --extra dev --project .
uv run --project . python -m hestia
# http://127.0.0.1:9480/ui/  ·  GET /v1/hearth
Enter fullscreen mode Exit fullscreen mode

Five questions. Five desks.

Do not collapse the layers

Desk Question
Factory / CLI Scaffold a provider?
THEMIS Admit this into a Hub catalogue?
HESTIA Where does the seller process run?
Hub What can a buyer find and pay for?
HISTOR What did tools/list say — and when did it change?

A hearth URL is not a catalogue row. A WARDEN block is not a HISTOR label. Collapsing those words is how a clean report hides a rewritten tool description.


The hole a snapshot cannot fill

We already measured the public MCP registry once. WARDEN scanned 1,108 servers, blocked 50, and published that only 4 of those blocks were the kind of real risk that framing wanted.

That was a moment. A server can pass the moment and change one sentence in a tool description the next day.

HISTOR is Certificate Transparency for MCP tool definitions: read initialize and tools/list, never call a tool, sign what was seen, append, tell you when the digest changed.

HISTOR live desk — public memory of MCP tool defs

Deep dive (method + four labels): 11,749 MCP servers answered tools/list…

The log grew. The method didn't.

HISTOR sealed crawl counts

Last sealed crawl finished 2026-09-26 11:43 UTC. Counters from the live desk / API at write time:

Count
Answered tools/list (ok) 12,201
Signed labels in the tree 101,192
Definition changes, 7 days 4,463
Endpoints that ever changed 3,581

A crawl that has not finished has not sealed. Quoting a mid-crawl counter is a lie by the time you finish the paragraph. The desk is the number; this page is the method.

A change on the desk is amber and dated — added, removed, or a field rewritten. Never the words compromised or unsafe. What you do with it is yours: re-read, re-approve, or pin the old digest.

curl -sS https://histor.modelmarket.dev/api/v1/check \
  -H 'Content-Type: application/json' \
  -d '{"endpoint":"https://example.com/mcp","tools":[ …tools/list you received… ]}'

curl -sS https://histor.modelmarket.dev/api/v1/log/sth
Enter fullscreen mode Exit fullscreen mode

Live: histor.modelmarket.dev · Source: github.com/alexar76/histor


Soft close

If the Hub alone is a wall of doors, the hearth is heat behind one of them — and the record is the guestbook that outlives yesterday's crawl.

Walk them once:

  1. Open hestia.modelmarket.dev — see a running roster that is not the catalogue
  2. Open histor.modelmarket.dev — paste a tools/list, ask for a match

⭐ github.com/alexar76/hestia · github.com/alexar76/histor · map: modeldev.modelmarket.dev

Top comments (0)