atx/registry

app.octolens.com/api/mcp/v2

https://app.octolens.com/api/mcp/v2

81
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 2d ago

Why this score

oauth_metadata_present+14
mcp_requires_authentication+10
tls_present_and_valid+4
reachable+2
hsts_enabled+1

Findings (1)

infoCORS allows any origin
cors.wildcard_origin @ 1.0.0

Evidence (7)

TypeObservedSHA-256
dns_resolution_observation2d ago613d738fc0d99de6…
http_response_observation2d agob5d9410212e46d11…
availability_observation2d ago7fa3d0f67c9f971a…
hosting_provider_observation2d ago07b610f7cd67ffa2…
tls_certificate_observation2d ago4151dd5c58c6cadc…
oauth_metadata_observation2d ago305503d37264ca48…
mcp_protocol_observation2d ago5f4c66c82509bed4…

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

Operate this service?

Prove control of app.octolens.com/api/mcp/v2 to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.

Claim this profile →