← Radixia MCP Census

Registry organisation

hatchloop.dev

80

out of 100, Connectable

How far an agent gets, and where it stops. Routes run in parallel: no document is required to reach a server, and no server is required to publish one.

Starting from the bare domain

  • observed

    Server card D1

    GET each published candidate path

  • not observed

    DNS record D2

    TXT lookup at _mcp.<domain>

    Nothing at the paths this profile publishes. Not proof of absence.

  • observed

    Conventional endpoint D3

    HEAD the conventional endpoint locations

  • not observed

    Authorization metadata D4

    GET /.well-known/oauth-protected-resource

    No authorization metadata. Authorization is optional in MCP, so this says nothing about conformance.

  • not observed

    Advertised by the home page D7

    GET /, then read the Link header and the head

    Nothing at the paths this profile publishes. Not proof of absence.

Converging on a server

  • observed

    A server answered D5

    One unauthenticated JSON-RPC call to the endpoint

  • observed

    It listed its tools D6

    tools/list on the same connection

Holding the two ends against each other

  • agrees

    The card matches the server C1

    Compare the card's claims against the handshake

    Every field present on both sides matches.

Not measured here

  • outside this profile

    Link relations on any page other than the home page

  • outside this profile

    Fetching an advertised catalog to see what is in it

  • outside this profile

    Anything behind authentication, or in a marketplace

CheckWhat it asksResultDetail
D1Server cardpass
D2DNS recordfail
D3Conventional endpointpassan endpoint answered
D4Authorization metadatafailnothing at any published candidate path
D5Handshakepasslegacy protocol (2025-11-25 or earlier)
D6Tool listingpass
D7Catalog advertised by the root documentfailthe home page answered, and advertises no catalog
C1Card against runtimepass
Q1Tool surfacefail
F1Text fallbackspass
F2Crawler posturefail

A skip is not a failure: it means the check could not run, usually because an earlier one found nothing to work with. What each check does, and on what authority.

History

run 20 50 run 21 10 run 22 80 run 23 80 run 24 80 run 25 80 run 26 80 run 27 80 run 28 80 run 29 80 run 30 80 run 32 80 run 33 80 run 34 80 run 35 80 run 36 80 run 37 80 run 38 80 run 39 80 run 40 80 run 41 80 run 42 80 run 43 80 run 44 80 run 45 80 run 47 80 run 48 80 run 49 80 run 50 80 run 51 80
Score by run. A change is only published once it persists across two consecutive runs.

Badge

MCP Census score for hatchloop.dev

https://www.radixia.ai/census/badge/hatchloop.dev.svg

Measured with methodology 0.5.0 on 2026-10-03T03:51:32.377Z. Wrong? Tell us. We would rather hear it from you.