Loading
Shufersal scores 23 out of 100 on the Agent Readiness Index
Shufersal reaches level 1, Tolerated. Web experience is the strongest area at 60 out of 100. Protocol access is the weakest at 0.
Shufersal was scanned on October 15, 2026. Its score is 23 out of 100, level 1, Tolerated. Pages load for an agent. Nothing is built for one. To reach level 2, Legible: Publish at least one machine readable layer: llms.txt, structured data or server rendered content.
Website: shufersal.co.il
Score by area
| Area | Score | What it asks |
|---|---|---|
| Discoverability | 46 out of 100, worth 15 points | Can an agent find and read your pages? |
| Protocol access | 0 out of 100, worth 20 points | Can an agent connect to you through MCP or an API? |
| Identity and delegation | 0 out of 100, worth 20 points | Can a customer give an agent limited access without sharing a password? |
| Web experience | 60 out of 100, worth 15 points | Does your site work when an agent uses it? |
| Voice and IVR | Not measured yet | What happens when an agent calls your phone line? |
| Policy and governance | Not measured yet | Do your terms allow agents that act for customers? |
What is holding Shufersal back
- MCP server, 8 points lost. No MCP server, server card or registry entry was found for this organization. Fix: Publish a remote MCP server with OAuth. Start with read only tools such as account status, orders or location search, and publish a server card at /.well known/mcp/server card.
- OAuth and OpenID metadata, 5 points lost. No OAuth or OpenID metadata was found on the 2 hosts that answered. 12 other hosts did not answer the scanner and could not be checked. Agents cannot discover where to send a customer to approve access. Fix: Publish /.well known/oauth authorization server and /.well known/oauth protected resource for the customer facing APIs.
- Developer and data sharing program, 4 points lost. No developer portal or data sharing program was found on public pages. Fix: Document the program, the standard in use for example FDX in US banking, the supported partners and a sandbox.
- PKCE and client registration, 4 points lost. No authorization server metadata, so PKCE and client registration could not be confirmed. Fix: Require PKCE with S256 and support client ID metadata documents or dynamic client registration for approved agent clients.
What already works
- Robots policy for user triggered agents
- Same behavior for a declared agent and a standard browser
How Shufersal compares
The average score for other is 34.8 out of 100 across 233 organizations. The average across all 1,420 scored organizations is 42.2 out of 100.
Similar organizations
- Example Domain, 23 out of 100
- Jdsports, 23 out of 100
- Louisvuitton, 23 out of 100
- idealista.com, 22 out of 100
- Bank Hapoalim, 21 out of 100
- Clalit, 21 out of 100