atx/registry

api.timix.ai/api/integration/v1

https://api.timix.ai/api/integration/v1/mcp

63
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 2d 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 68 whose names suggest state change (approve_timesheet, bulk_create_time_reports, bulk_update_cost_rates, …) — 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_observation2d agob28064305779703f…
http_response_observation2d agoc2e1567911ea8689…
availability_observation2d ago620b6eb43b761ccf…
hosting_provider_observation2d ago958411567b2d9bdc…
tls_certificate_observation2d ago3960819e2fdb28af…
oauth_metadata_observation2d ago1fff50afd23e02ab…
mcp_protocol_observation2d ago4a751284748b64a5…
mcp_capability_observation2d ago8fc8e405072e8534…

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

Operate this service?

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

Claim this profile →