atx/registry

api.mcp.ai/p_omie

https://api.mcp.ai/p_omie

41
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 5h ago

Why this score

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

Findings (4)

mediumCapabilities are listable without authentication, including 13 whose names suggest state change (omie_create_checking_account, omie_create_customer, omie_create_payable, …) — inferred from tool names, not confirmed
mcp.unauthenticated_consequential_tools @ 1.0.0
mediumNew state-changing capability exposed: omie_delete_attachment, omie_upload_attachment
mcp.consequential_capability_added @ 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 (9)

TypeObservedSHA-256
dns_resolution_observation5h ago648cf4ff284b19b4…
http_response_observation5h agoabcfccc2a0283d03…
availability_observation5h ago4f6a724efc29f741…
hosting_provider_observation5h agoe7292135d1d3f6bd…
tls_certificate_observation5h agoc7d4fd03a56fac0e…
oauth_metadata_observation5h agofb6b520679fad340…
mcp_protocol_observation5h ago1b1ed8597d2a29a5…
mcp_capability_observation5h ago4307d43a3c6ce789…
mcp_capability_drift5h ago6792304056b7f2b5…

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

Operate this service?

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

Claim this profile →