atx/registry

tenjin.blog/api

https://tenjin.blog/api/mcp

50
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 1h ago

Why this score

mcp.unauthenticated_consequential_tools-8
tls_present_and_valid+4
mcp_capabilities_discoverable+4
mcp.tool_schema_changed-3
reachable+2
hsts_enabled+1

Findings (2)

mediumCapabilities are listable without authentication, including 7 whose names suggest state change (delete_essay, pay_and_read, publish_essay, …) — inferred from tool names, not confirmed
mcp.unauthenticated_consequential_tools @ 1.0.0
lowInput schema changed without a name change: publish_essay, resolve_keys, search
mcp.tool_schema_changed @ 1.0.0

Evidence (9)

TypeObservedSHA-256
dns_resolution_observation1h ago99d78085ae4130d8…
http_response_observation1h ago7e153b9b48645a16…
availability_observation1h ago7ccc7ff579b59492…
hosting_provider_observation1h ago07b610f7cd67ffa2…
tls_certificate_observation1h ago93a0b7ed98863dbe…
oauth_metadata_observation1h agod623d6bdddcf2dd3…
mcp_protocol_observation1h ago557803f6cc583c90…
mcp_capability_observation1h agof11f224d26a24913…
mcp_capability_drift1h ago5ef0b7b9a245f825…

Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.

Operate this service?

Prove control of tenjin.blog/api to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.

Claim this profile →