context safety score
A score of 40/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
hidden instruction
high hidden content ratio detected in DOM
encoded payload
suspicious base64-like blobs detected in page content
social engineering
Site operates as a URL shortener (url-shortify-premium plugin active, shortlink '/th4q' present) under the domain mcwlink.co, which is structurally designed to obscure the true destination of links distributed to users. URL shorteners on gambling/affiliate domains are commonly used to evade blocklists and deceive users about where they are being sent. (location: page.html:64-68, metadata.json)
brand impersonation
The site aggregates and promotes multiple 'MCW Casino' branded properties across several countries (Philippines, Bangladesh, Vietnam, Cambodia) and related gambling brands (MCW777, Mega Cricket World, Banglabet, New City VIP, MCW 카지노) via a link hub. The domain mcwlink.co mimics the MCW brand as a centralized redirect/affiliate hub, which may be used to impersonate or piggyback on the legitimacy of the MCW Casino brand to funnel users to unregulated gambling sites. (location: page.html:151-153, page.html:192-193)
malicious redirect
The site's primary function is URL shortening and link redirection (url-shortify-premium plugin, WordPress shortlink infrastructure), directing users to a network of offshore gambling domains across multiple jurisdictions (Bangladesh, Philippines, Vietnam, Cambodia, Korea). Short URLs such as '/th4q' mask true destinations; users clicking shared links cannot determine the endpoint before visiting. This is a recognized technique for bypassing security filters and geo-restrictions. (location: page.html:68 (rel='shortlink' href='https://mcwlink.co/th4q'), page.html:64 (url-shortify-js plugin))
hidden content
The Tier 2 scan detected a hidden content ratio of 0.39 (39%), and 10 suspicious base64 blobs. The rendered page-hidden.txt is empty, suggesting hidden content may be within inline CSS, script variables, or dynamically injected content not extractable at static scan time. The high hidden content ratio warrants attention even absent confirmed payload. (location: .brin-context.md (hidden_content_ratio: 0.39, suspicious_base64_blobs: 10))
curl https://api.brin.sh/domain/mcwlink.coCommon questions teams ask before deciding whether to use this domain in agent workflows.
mcwlink.co currently scores 40/100 with a suspicious verdict and low confidence. The goal is to protect agents from high-risk context before they act on it. Treat this as a decision signal: higher scores suggest lower observed risk, while lower scores mean you should add review or block this domain.
Use the score as a policy threshold: 80–100 is safe, 50–79 is caution, 20–49 is suspicious, and 0–19 is dangerous. Teams often auto-allow safe, require human review for caution/suspicious, and block dangerous.
brin evaluates four dimensions: identity (source trust), behavior (runtime patterns), content (malicious instructions), and graph (relationship risk). Analysis runs in tiers: static signals, deterministic pattern checks, then AI semantic analysis when needed.
Identity checks source trust, behavior checks unusual runtime patterns, content checks for malicious instructions, and graph checks risky relationships to other entities. Looking at sub-scores helps you understand why an entity passed or failed.
brin performs risk assessments on external context before it reaches an AI agent. It scores that context for threats like prompt injection, hijacking, credential harvesting, and supply chain attacks, so teams can decide whether to block, review, or proceed safely.
No. A safe verdict means no significant risk signals were detected in this scan. It is not a formal guarantee; assessments are automated and point-in-time, so combine scores with your own controls and periodic re-checks.
Re-check before high-impact actions such as installs, upgrades, connecting MCP servers, executing remote code, or granting secrets. Use the API in CI or runtime gates so decisions are based on the latest scan.
Learn more in threat detection docs, how scoring works, and the API overview.
Assessments are automated and may contain errors. Findings are risk indicators, not confirmed threats. This is a point-in-time assessment; security posture can change.
integrate brin in minutes — one GET request is all it takes. query the api, browse the registry, or download the full dataset.