MCP VerifyThe rating layer for AI agents

52f4eaq2q8ee.hostc.app/mcp

UNGRADED by MCP Verify under grade/v1 in snapshot REL-SNAP-077: not observed long enough to grade. Recorded reachable in 0 of 1 observations since 20 October 2026.

Too little history to publish. This endpoint has been observed 1 time; the threshold for publication is 3. The page stays available and is excluded from search indexes until the record is long enough to say anything useful. The endpoint exists. We simply have not looked at it enough times.

The record behind itOne mark per snapshot, and every grade sealed along the way.

grade/v1
checked in REL-SNAP-077

Sealed grades: UNGRADED at REL-SNAP-077.

  • Reachable
  • Reachable, asked to sign in or pay
  • Not reachable
  • Not observed
Transport
streamable-http
Tools listed
none
Tool schema fingerprint
none
Name reported by the server
Not reported.self-reported, never used as identity
Registry names (not anchored)
sh.surge.unlockbot/onchain-intelas the registry listed it; not covered by the chain
First and last observed
20 Oct 2026 to 20 Oct 2026

Observations

Newest first. Each row is a separate look, not a summary.

Observed (UTC)SnapshotRecorded asLatencyToolsTool schema
2026-10-20 11:02REL-SNAP-077HTTP_4XXnonenonenone

Checking this record

Each observation above is a leaf of the merkle root published with its snapshot. A proof shows a record is in the archive. It does not show the measurement is correct.

Latest root, REL-SNAP-084

ed182ac44848117a98c9536eabbd63d33a756c4db072812094c742e3fa1fdef6

Published at

gist.github.com/181cc5f4834e0a4f812acde9a5efdb95

Is 52f4eaq2q8ee.hostc.app/mcp reliable?
It is UNGRADED: it has not been observed long enough to grade. So far it has been recorded reachable in 0 of 1 observations.
When was it last checked?
20 October 2026, in snapshot REL-SNAP-077, where it was recorded as HTTP_4XX.
Has its tool list changed?
Not yet known. None of its 1 observation recorded a tool list.