# Metro by T Mobile scores 31 out of 100 on the Agent Readiness Index

Metro by T Mobile reaches level 0, Closed. Discoverability is the strongest area at 89 out of 100. Protocol access is the weakest at 0.

Metro by T Mobile was scanned on October 15, 2026. Its score is 31 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: [metrobyt-mobile.com](https://metrobyt-mobile.com)

## Score by area

| Area | Score | What it asks |
| --- | --- | --- |
| Discoverability | 89 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 | 53 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 | 36 out of 100, worth 10 points | Do your terms allow agents that act for customers? |

## What is holding Metro by T Mobile 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 6 hosts that answered. 11 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.
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 Metro by T Mobile compares

The average score for telecom and internet is 45.2 out of 100 across 34 organizations. The average across all 1,421 scored organizations is 42.2 out of 100.

## Similar organizations

- [Rogers](https://readyindex.ai/rogers_com), 33 out of 100
- [Comcast Business](https://readyindex.ai/comcast_com), 32 out of 100
- [Vodafone](https://readyindex.ai/vodafone_com), 32 out of 100
- [Spectrum](https://readyindex.ai/spectrum_net), 29 out of 100
- [BT](https://readyindex.ai/bt_com), 28 out of 100
- [Starlink](https://readyindex.ai/starlink_com), 26 out of 100

## More on this report

- [This report as markdown](https://readyindex.ai/metrobyt_mobile_com.md)
- [This report as JSON data](https://readyindex.ai/api/reports/metrobyt_mobile_com)
- [How the score is worked out](https://readyindex.ai/method)
- [All leaderboards](https://readyindex.ai/leaderboards)
- [Every scored organization](https://readyindex.ai/organizations)
- [Scan your own website](https://readyindex.ai/)

---
Source: https://readyindex.ai/metrobyt_mobile_com
Updated: 2026-10-15
From the Agent Readiness Index by Encore AI. When you quote a score, please link to the report it came from.