# RingCentral scores 70 out of 100 on the Agent Readiness Index

RingCentral reaches level 2, Legible. Discoverability is the strongest area at 93 out of 100. Protocol access is the weakest at 36.

RingCentral was scanned on October 15, 2026. Its score is 70 out of 100, level 2, Legible. An agent can read and cite your content. To reach level 3, Connectable: Offer a programmatic path: a live MCP server, a data sharing program with OAuth metadata, or a verified Poppy file.

Website: [ringcentral.com](https://www.ringcentral.com)

## Score by area

| Area | Score | What it asks |
| --- | --- | --- |
| Discoverability | 93 out of 100, worth 15 points | Can an agent find and read your pages? |
| Protocol access | 36 out of 100, worth 20 points | Can an agent connect to you through MCP or an API? |
| Identity and delegation | 90 out of 100, worth 20 points | Can a customer give an agent limited access without sharing a password? |
| Web experience | 87 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 RingCentral 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. **Documented delegate and data sharing controls**, 4 points lost. No public page on delegate access or connected app controls was found. Fix: Publish a help page on delegate access and add a connected apps screen where customers revoke access.
3. **Browser tools exposed to agents**, 3 points lost. The sign in and home pages register no browser tools for agents. Fix: Register tools for safe tasks such as location search and price lookup with navigator.modelContext.
4. **Sign in page loads for a declared agent in a browser**, 3 points lost. The sign in page is blocked for a declared agent but loads for a standard browser. Fix: Serve the sign in page to verified agent browsers, and use signed agent identity to separate them from attackers.

## What already works

- OAuth and OpenID metadata
- PKCE and client registration
- llms.txt guide for agents

## How RingCentral compares

The average score for software is 61.4 out of 100 across 124 organizations. The average across all 1,421 scored organizations is 42.2 out of 100.

## Similar organizations

- [Deel](https://readyindex.ai/deel_com), 70 out of 100
- [Freshworks](https://readyindex.ai/freshworks_com), 70 out of 100
- [Replit](https://readyindex.ai/replit_com), 70 out of 100
- [Slack](https://readyindex.ai/slack_com), 70 out of 100
- [Zapier](https://readyindex.ai/zapier_com), 70 out of 100
- [Zendesk](https://readyindex.ai/zendesk_com), 70 out of 100

## More on this report

- [This report as markdown](https://readyindex.ai/ringcentral_com.md)
- [This report as JSON data](https://readyindex.ai/api/reports/ringcentral_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/ringcentral_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.
