atx/registry

api.repuso.com/public/v1

https://api.repuso.com/public/v1/mcp

77
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 46m ago

Why this score

oauth_metadata_present+14
mcp_requires_authentication+10
tls_present_and_valid+4
headers.missing_hsts-3
reachable+2

Findings (2)

lowNo Strict-Transport-Security header
headers.missing_hsts @ 1.0.0
infoCORS allows any origin
cors.wildcard_origin @ 1.0.0

Evidence (7)

TypeObservedSHA-256
dns_resolution_observation46m ago467acc47243d2777…
http_response_observation46m ago388affc4e17ee343…
availability_observation46m agoda8ce450cd36afd1…
hosting_provider_observation46m agoe7292135d1d3f6bd…
tls_certificate_observation46m agodac6e48a2034eebc…
oauth_metadata_observation46m agodb09725bbd180f5f…
mcp_protocol_observation46m ago5f4c66c82509bed4…

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

Operate this service?

Prove control of api.repuso.com/public/v1 to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.

Claim this profile →