Loading

Serviceseeking scores 23 out of 100 on the Agent Readiness Index

Serviceseeking reaches level 0, Closed. Discoverability is the strongest area at 84 out of 100. Protocol access is the weakest at 0.

Serviceseeking was scanned on October 22, 2026. Its score is 23 out of 100, level 0, Closed. Declared agents are blocked from the public website. To reach level 1, Tolerated: The home page must load for a declared agent and robots.txt must not block every agent.

Website: serviceseeking.com.au

Score by area

AreaScoreWhat it asks
Discoverability84 out of 100, worth 12 pointsCan an agent find and read your pages?
Protocol access0 out of 100, worth 16 pointsCan an agent connect to you through MCP or an API?
Identity and delegation0 out of 100, worth 16 pointsCan a customer give an agent limited access without sharing a password?
Web experience13 out of 100, worth 12 pointsDoes your site work when an agent uses it?
Voice and IVRNot measured yetWhat happens when an agent calls your phone line?
Policy and governance36 out of 100, worth 8 pointsDo your terms allow agents that act for customers?

What is holding Serviceseeking back

  1. 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.
  2. OAuth and OpenID metadata, 5 points lost. No OAuth or OpenID metadata was found on the 15 hosts that answered. 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.
  3. 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.
  4. 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

  • Content available without running scripts

How Serviceseeking compares

The average score for other is 33.8 out of 100 across 300 organizations. The average across all 1,503 scored organizations is 41.6 out of 100.

Similar organizations

More on this report