CanAgentUse tools

UCP Suite

Validate Universal Commerce Protocol discovery, then test product search, carts, checkout links, and merchant handoff flows.

MCP Playground

Connect to remote MCP servers, inspect tools and resources, test prompts, auth, headers, notifications, and JSON-RPC responses.

A2A Playground

Inspect Agent Cards, validate advertised endpoints, and prepare safe requests for agent-to-agent workflows.

Agent Website Viewer

Enter a public URL and see the roles, names, landmarks, controls, and blockers that shape how AI agents understand the page.

SCANNED
Jul 15, 2026, 8:40 AM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
66/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability68%Agent Easeof Use57%Security& Trust70%GEO, AIO, AEO65%SEO92%Performance94%Accessibility51%
  • AI Discoverability 68 out of 100
  • Agent Ease of Use 57 out of 100
  • Security & Trust 70 out of 100
  • GEO, AIO and AEO 65 out of 100
  • SEO 92 out of 100
  • Performance 94 out of 100
  • Accessibility 51 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

TechNexus Venture Collaborative — Corporate Innovation Meets Startup Investment favicon

TechNexus Venture Collaborative — Corporate Innovation Meets Startup Investment

TechNexus builds venture ecosystems connecting Fortune 1000 corporations with high-growth startups — 150+ portfolio companies, $4B+ value since 2007.

Open Agent View

Next step

Turn this report into a fix workflow

2 failed checks are ready to move into MCP or CLI remediation. Generate a repair prompt, connect the scanner to your coding agent, or open the integration docs before your next rescan.

Fix with MCP / CLI
Detailed report scores grouped by capability area
MetricScoreStatusPassedFailedWarningEvidence
AI Discoverability
68
Needs work3100
Discoverability
67
Needs work800
Content Readiness
75
Mostly ready2000
Bot Access Control
63
Needs work300
Agent Ease of Use
57
Needs work300
Auth
43
Priority fix100
Google Agentic Browsing
100
Strong200
GEO, AIO and AEO
65
Needs work700
GEO Readiness
Not Applicable
Not Applicable200
AIO Readiness
Not Applicable
Not Applicable300
AEO Readiness
Not Applicable
Not Applicable200
SEO
92
Strong900
SEO
92
Strong900
Security & Trust
70
Needs work1620View details
Security & Trust
70
Needs work1620View details
Performance
94
Strong1510View details
Performance
94
Strong1510View details

Prioritized recommendations

Issues ranked by score impact

3 items need attention

Security & TrustSecurity & TrustEstablished

Content-Security-Policy

Content-Security-Policy failed at "Find enforcing CSP delivery".

30 Fail

Needs attention

Content-Security-Policy

Failed check
01

Issue

Only Content-Security-Policy-Report-Only is present; report-only policies are not enforced.

Details

02

Why it matters

Content Security Policy reduces the impact of injection bugs by limiting where scripts, styles, frames, forms, and other browser resources can load or execute.

Check name

Content-Security-Policy

Score

40/100

Status

fail

Category

Security & Trust

Maturity

Established

Goal

Constrain browser resource loading and script execution with an enforcing Content-Security-Policy header.

Result

Content-Security-Policy failed at "Find enforcing CSP delivery".

Validation steps

  1. Find enforcing CSP delivery

    Only Content-Security-Policy-Report-Only is present; report-only policies are not enforced.

    Enforcing Content-Security-Policy header is missing
Evidence log1 step · 4 lines
Find enforcing CSP delivery [fail]! Only Content-Security-Policy-Report-Only is present; report-only policies are not enforced.INFOFind enforcing CSP deliveryINFORead CSP delivery headers enforcingHeader="missing" reportOnlyHeader="default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://cdn.jsdelivr.net https://www.googletagmanager.com https://www.google-analytics.com https://js.hs-scripts.com https://js.hs-analytics.net https://js.hs-banner.com https://js.usemessages.com https://js.hsadspixel.net https://js.hscollectedforms.net https://www.google.com https://www.gstatic.com https://*.technexus.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com https://cdn.jsdelivr.net; font-src 'self' d" metaPolicyCount=0 legacyHeadersPresent=[]FAILRequire enforcing Content-Security-Policy header actual="missing" expected="present" issue="Only Content-Security-Policy-Report-Only is present; report-only policies are not enforced."FAILOnly Content-Security-Policy-Report-Only is present; report-only policies are not enforced.

Security & TrustSecurity & TrustEstablished

Frame protection

Frame protection failed at "Validate CSP frame-ancestors".

20 Fail

Needs attention

Frame protection

Failed check
01

Issue

frame-ancestors appears only in Content-Security-Policy-Report-Only, so it is not enforced.

Details

02

Why it matters

Frame protection blocks hostile sites from embedding pages in deceptive frames, reducing clickjacking and UI redressing risk.

Check name

Frame protection

Score

61/100

Status

fail

Category

Security & Trust

Maturity

Established

Goal

Prevent unwanted framing with an enforcing CSP frame-ancestors directive or a valid X-Frame-Options fallback.

Result

Frame protection failed at "Validate CSP frame-ancestors".

Validation steps

  1. Validate CSP frame-ancestors

    frame-ancestors appears only in Content-Security-Policy-Report-Only, so it is not enforced.

    CSP frame-ancestors is missing or ineffective
Evidence log1 step · 4 lines
Validate CSP frame-ancestors [fail]! frame-ancestors appears only in Content-Security-Policy-Report-Only, so it is not enforced.INFOValidate CSP frame-ancestorsINFORead CSP frame-ancestors signals enforcingHeaderPresent=false reportOnlyHeaderPresent=true metaFrameAncestors=false policyCount=0 duplicateDirectives=[]FAILCompare effective frame-ancestors directive actual="missing" expected="valid restrictive enforcing frame-ancestors" issue="frame-ancestors appears only in Content-Security-Policy-Report-Only, so it is not enforced."FAILframe-ancestors appears only in Content-Security-Policy-Report-Only, so it is not enforced.

PerformancePerformanceBrowser audit

Forced reflow

100 Fail

Check name

Forced reflow

Score

0/100

Status

fail

Device

desktop

Category

Performance

Fix guidance

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about [forced reflows](https://developer.chrome.com/docs/performance/insights/forced-reflow) and possible mitigations.

Evidence
{
  "description": "A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about [forced reflows](https://developer.chrome.com/docs/performance/insights/forced-reflow) and possible mitigations."
}

Sign in to see 32 other issues and the full report

Create a free account to unlock every issue, evidence details, exports, and higher free limits.

Fix with MCP or CLI

Use this report as the handoff into remediation. Generate a coding-agent prompt with the failing checks attached, or jump to the MCP and CLI setup docs before your next rescan.

Fix with MCP / CLI

Score history