← Radixia MCP Census

Registry organisation

sitepulsar.ai

100

out of 100, Agent-ready

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

  • observed

    Authorization metadata D4

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

  • 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

  • not reached

    The card matches the server C1

    Compare the card's claims against the handshake

    The evidence this needs was never collected.

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 metadatapass
D5Handshakepassthe server requires authorization
D6Tool listingpass
D7Catalog advertised by the root documentfailthe home page answered, and advertises no catalog
C1Card against runtimeskipno field appears on both sides
Q1Tool surfacepass
F1Text fallbackspass
F2Crawler posturepass

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 100 run 21 100 run 22 100 run 23 100 run 24 100 run 25 100 run 26 100 run 27 100 run 28 100 run 29 100 run 30 100 run 32 100 run 33 100 run 34 100 run 35 100 run 36 100 run 37 100 run 38 100 run 39 100 run 40 100 run 41 100 run 42 100 run 43 100 run 44 100 run 45 100 run 47 100 run 48 100 run 49 100 run 50 100 run 51 100
Score by run. A change is only published once it persists across two consecutive runs.

Badge

MCP Census score for sitepulsar.ai

https://www.radixia.ai/census/badge/sitepulsar.ai.svg

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