atx/registry

mcp.meet.bot

https://mcp.meet.bot/

49
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 2d ago

Why this score

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

Findings (3)

mediumCapabilities are listable without authentication, including 2 whose names suggest state change (delete_webhook, set_webhook) — inferred from tool names, not confirmed
mcp.unauthenticated_consequential_tools @ 1.0.0
lowNo Strict-Transport-Security header
headers.missing_hsts @ 1.0.0
infoCORS allows any origin
cors.wildcard_origin @ 1.0.0

Evidence (8)

TypeObservedSHA-256
dns_resolution_observation2d agoc804411ac55dffd1…
http_response_observation2d agobfde4c680c5515a0…
availability_observation2d ago12e1b74c05a800a4…
hosting_provider_observation2d agof6ca63562d443d49…
tls_certificate_observation2d agocd38355e4fe325d9…
oauth_metadata_observation2d ago6e3b4ab0d3f9fe1b…
mcp_protocol_observation2d agoa8bf8619359a147e…
mcp_capability_observation2d agoa40230e8ca790ae7…

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

Operate this service?

Prove control of mcp.meet.bot to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.

Claim this profile →