atx/registry

mcp.fftcompanion.app

https://mcp.fftcompanion.app/mcp

66
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 1d ago

Why this score

tls_present_and_valid+12
reachable+6
mcp_capabilities_discoverable+4
headers.missing_hsts-3
mcp.tool_schema_changed-3

Findings (3)

lowNo Strict-Transport-Security header
headers.missing_hsts @ 1.0.0
lowInput schema changed without a name change: get_job, get_monster, get_records
mcp.tool_schema_changed @ 1.0.0
infoCORS allows any origin
cors.wildcard_origin @ 1.0.0

Evidence (8)

TypeObservedSHA-256
dns_resolution_observation1d agod3ec09a03f230ccb…
http_response_observation1d ago46c142b02bb73fb4…
availability_observation1d agoa31e3e84941cff7b…
tls_certificate_observation1d agof4f45ddcc0d87052…
oauth_metadata_observation1d agof9b5fa916e02fde9…
mcp_protocol_observation1d ago7f655f6d264392db…
mcp_capability_observation1d ago892477b765a79043…
mcp_capability_drift1d ago6d9c5fe9344fef2e…

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

Operate this service?

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

Claim this profile →