CanAgentUse

CanAgentUse products

MCP ServerInstall CanAgentUse in your coding agent so scan findings become repo-ready fixes.View product WooCommerce PluginPublish UCP discovery and agent-ready commerce signals from WooCommerce without rebuilding checkout.View product Shopify PluginAdd UCP discovery, storefront metadata checks, and controlled cart-to-checkout flows for shopping agents.View product AgentReady CIScan commits and PRs, publish reports, and choose which agent-readiness failures should block merges.View product

CanAgentUse tools

UCP Suite

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

UCP ValidatorUCP Playground

MCP Playground

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

MCP Playground

A2A Playground

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

A2A Playground

Agent Website Viewer

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

Agent Website Viewer
New Scan
https://mg.co.za/
SCANNED
Jul 2, 2026, 9:50 PM
VISIBILITY
Public
SUITE2026.06.10
Rescan Report
Share Report
Copy Report Link
Export Report
52/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability71%Agent Easeof Use56%Security& Trust50%GEO, AIO, AEO64%SEO100%Performance59%Accessibility0%
  • AI Discoverability 71 out of 100
  • Agent Ease of Use 56 out of 100
  • Security & Trust 50 out of 100
  • GEO, AIO and AEO 64 out of 100
  • SEO 100 out of 100
  • Performance 59 out of 100
  • Accessibility 0 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

The Mail & Guardian | Africa's Better Future favicon

The Mail & Guardian | Africa's Better Future

The Mail & Guardian is a quality investigative and comment news publication, based on a culture of editorial independence and excellence.

Open Agent View

Next step

Turn this report into a fix workflow

1 failed check is 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
71
Needs work2900
Discoverability
100
Strong1000
Content Readiness
53
Needs work1600
Bot Access Control
63
Needs work300
Agent Ease of Use
56
Needs work1120View details
API
75
Mostly ready810View details
Auth
48
Priority fix100
Skill Discovery
54
Needs work100
Google Agentic Browsing
50
Needs work110View details
GEO, AIO and AEO
64
Needs work800
GEO Readiness
Not Applicable
Not Applicable200
AIO Readiness
Not Applicable
Not Applicable300
AEO Readiness
Not Applicable
Not Applicable300
SEO
100
Strong1000
SEO
100
Strong1000
Security & Trust
50
Needs work700
Security & Trust
50
Needs work700
Performance
59
Needs work1700
Performance
59
Needs work1700
Accessibility
0
Priority fix010View details
Accessibility
0
Priority fix010View details

Prioritized recommendations

Issues ranked by score impact

3 items need attention

Agent Ease of UseAPIEstablished

API Catalog

API Catalog failed at "Validate API catalog targets".

17 Fail

Needs attention

API Catalog

Failed check
01

Issue

API catalog target https://mg.co.za/v1/site.get (item) returned HTTP 500 instead of a 2xx/3xx response.

Details

02

Why it matters

API catalogs help agents find API endpoints, service descriptions, documentation, status resources, auth metadata, and related machine-readable contracts without guessing entry points.

Check name

API Catalog

Score

83/100

Status

fail

Category

API

Maturity

Established

Goal

Publish an API catalog for automated public API discovery using RFC 9727 when this origin exposes public APIs.

Result

API Catalog failed at "Validate API catalog targets".

Validation steps

  1. Validate API catalog targets

    API catalog target https://mg.co.za/v1/site.get (item) returned HTTP 500 instead of a 2xx/3xx response.

    API catalog targets are unreachable or media types mismatch
Evidence log1 step · 13 lines
Validate API catalog targets [fail]! API catalog target https://mg.co.za/v1/site.get (item) returned HTTP 500 instead of a 2xx/3xx response.INFOValidate API catalog targetsINFOFetch same-origin API catalog targets and record same-site/external skipsFAILAPI catalog target failed validation rel="item" href="https://mg.co.za/v1/site.get" statusCode=500 contentType="application/json" typeMatches=trueFAILAPI catalog target failed validation rel="item" href="https://mg.co.za/v1/site.route" statusCode=500 contentType="application/json" typeMatches=trueFAILAPI catalog target failed validation rel="item" href="https://mg.co.za/v1/article.list" statusCode=500 contentType="application/json" typeMatches=trueFAILAPI catalog target failed validation rel="item" href="https://mg.co.za/v1/creator.list" statusCode=500 contentType="application/json" typeMatches=trueFAILAPI catalog target failed validation rel="item" href="https://mg.co.za/v1/sponsor.list" statusCode=500 contentType="application/json" typeMatches=truePASSAPI catalog target is reachable rel="service-doc" href="https://mg.co.za/sitemap.xml" statusCode=200 contentType="application/xml; charset=utf-8"PASSAPI catalog target is reachable rel="service-doc" href="https://mg.co.za/rss/" statusCode=200 contentType="application/rss+xml"PASSAPI catalog target is reachable rel="service-doc" href="https://mg.co.za/atom/" statusCode=200 contentType="application/atom+xml"PASSAPI catalog target is reachable rel="service-doc" href="https://mg.co.za/robots.txt" statusCode=200 contentType="text/plain"FAILCompare API catalog target failure count actual=5 expected=0FAILAPI catalog target https://mg.co.za/v1/site.get (item) returned HTTP 500 instead of a 2xx/3xx response.

AccessibilityAccessibilityBrowser audit

Accessibility audit

100 Fail

Check name

Accessibility audit

Score

0/100

Status

fail

Device

desktop

Category

Accessibility

Fix guidance

Make sure the page can load in Chrome and run Accessibility checks.

Evidence
{
  "error": "__name is not defined"
}

Agent Ease of UseGoogle Agentic BrowsingBrowser audit

Accessibility tree is not well-formed

100 Fail

Check name

Accessibility tree is not well-formed

Score

0/100

Status

fail

Device

desktop

Category

Google Agentic Browsing

Fix guidance

A well-formed [accessibility tree](http://goo.gle/lighthouse-agentic-a11y) helps AI agents to navigate and interact with the page.

Evidence
{
  "description": "A well-formed [accessibility tree](http://goo.gle/lighthouse-agentic-a11y) helps AI agents to navigate and interact with the page."
}

Sign in to see 36 other issues and the full report

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

Email code

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

Public scan score over time

Public reports for this website origin. Select any point or report link to open that canonical report.

1 reports
Public score history report links
Scan dateScoreReadinessReport
52/100Level 3, Bot-AwareCurrent report