atx/registry

crew.studiomeyer.io

https://crew.studiomeyer.io/mcp

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 ago360afa956e257232…
http_response_observation2d ago9173f5d97c24700f…
availability_observation2d agocef5928e76a65f7a…
hosting_provider_observation2d agoe7292135d1d3f6bd…
tls_certificate_observation2d agof5f7d0618585cbba…
oauth_metadata_observation2d agoc5ace835ec3d2a3b…
mcp_protocol_observation2d ago5f4c66c82509bed4…

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

Operate this service?

Prove control of crew.studiomeyer.io to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.

Claim this profile →