atx/registry

chargebee.usefulapi.io

https://chargebee.usefulapi.io/mcp

63
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 3d ago

Why this score

oauth_metadata_present+14
mcp.unauthenticated_consequential_tools-8
tls_present_and_valid+4
mcp_capabilities_discoverable+4
headers.missing_hsts-3
reachable+2

Findings (2)

mediumCapabilities are listable without authentication, including 3 whose names suggest state change (chargebee_create_customer, chargebee_get_invoice, chargebee_update_customer) — inferred from tool names, not confirmed
mcp.unauthenticated_consequential_tools @ 1.0.0
lowNo Strict-Transport-Security header
headers.missing_hsts @ 1.0.0

Evidence (8)

TypeObservedSHA-256
dns_resolution_observation3d ago4bd7d8a732c39b2e…
http_response_observation3d ago8782e51d2ece9f66…
availability_observation3d agoa7affa86039dcbce…
hosting_provider_observation3d agoe7292135d1d3f6bd…
tls_certificate_observation3d ago38e7bfd04527e678…
oauth_metadata_observation3d agoce8cf39894af46c9…
mcp_protocol_observation3d agobcf43381dbc744e2…
mcp_capability_observation3d ago7bf31bbec2e20a70…

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

Operate this service?

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

Claim this profile →