OpenVidu Docs MCP server
io.openvidu/docsopenvidu.iostreamable-httpv1.0.0Scanned
The official OpenVidu documentation, per version, for coding agents.
7 tools: 7 only read.
- Reads private data · 4
- Reads text others write · 2
- Can send data out · 1
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the OpenVidu Docs MCP server can do
The OpenVidu Docs MCP server is published by openvidu.io, a domain the MCP Registry verified. It has 7 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
4 tools read private data (list_doc_sections, get_doc_page, search_docs and 1 more); 2 tools bring in text other people can write (list_doc_sections and get_doc_page); 1 tool can send data out of your system (get_doc_page). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
The fixed checks matched 1 finding (credentials-mention). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 18, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
7 tools
Only reads 7Show 7 read-only tools
get_changelogReturns the release notes / changelog page(s) already indexed for a version (e.g.Reads private dataNo findings
Why it is in this group
- The name "get_changelog" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "return" and "note": it reads notes.
Description, as the server wrote it Returns the release notes / changelog page(s) already indexed for a version (e.g. 'OpenVidu Meet release notes', 'OpenVidu Platform release notes'), without having to guess the URL via search_docs or list_doc_sections. A page cut at 'max_chars' carries 'truncated', 'next_offset' and 'headings': pass its 'url' to get_doc_page with that offset to read on, or with one of those headings to read just that release. The response includes 'version_used': always tell the user which documentation version what you're telling them corresponds to. If it also carries 'version_warning', or 'version_sensitive': true on a result or in a page's 'version_note', the page changes between versions: say so explicitly and explain how to specify a different one. The index has no notion of edition or product, so if the answer depends on either, say which one you assumed.
Annotations the server declares
- title: Get release notes
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_doc_pageReturns the content of a page of the OpenVidu documentation (openvidu.io) for a specific version, or of several pages at once with 'urls' (one round trip instead of several).Reads private dataReads text others writeCan send data outNo findings
Why it is in this group
- The name "get_doc_page" says "get": a word for reading.
What it can reach
- private-dataThe name "get_doc_page" says "get" and "doc": it reads documents.
- untrusted-inputThe description's first sentence says "return" and "url": it reads web pages, which anyone can write.
- untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Claude Code: ask, because it is tagged outbound.
Description, as the server wrote it Returns the content of a page of the OpenVidu documentation (openvidu.io) for a specific version, or of several pages at once with 'urls' (one round trip instead of several). Pass exactly one of 'url' and 'urls'. A URL ending in a #anchor, as search_docs returns for a match under a heading, returns only that heading's section, subsections included; 'heading' does the same by name, and comes with the page's 'intro' and 'headings': when the answer may also depend on setup or context described elsewhere, read those sections too, or drop the anchor to read the whole page. A page longer than 'max_chars' comes back cut: 'truncated' is true, 'total_chars' is its full length, 'next_offset' is the 'offset' that reads the next chunk, and 'headings' lists its sections and their sizes, so you can read only the one you need. Every URL returned is the page as a person opens it: link those in answers. list_doc_sections with 'section' gives valid URLs; so does search_docs. The response includes 'version_used': always tell the user which documentation version what you're telling them corresponds to. If it also carries 'version_warning', or 'version_sensitive': true on a result or in a page's 'version_note', the page changes between versions: say so explicitly and explain how to specify a different one. The index has no notion of edition or product, so if the answer depends on either, say which one you assumed.
Annotations the server declares
- title: Get a documentation page
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_pricing_infoReturns the content of OpenVidu's pricing page (editions, plans, cost model).No findings
Why it is in this group
- The name "get_pricing_info" says "get": a word for reading.
Description, as the server wrote it Returns the content of OpenVidu's pricing page (editions, plans, cost model). Not versioned: pricing is the same across every indexed documentation version, so this tool takes no 'version' argument. When cut at 'max_chars' it carries 'truncated', 'next_offset' and 'headings': pass its 'url' to get_doc_page with that offset to read on, or with a heading to read just that section.
Annotations the server declares
- title: Get pricing information
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_doc_sectionsBrowses the indexed documentation of a version.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "list_doc_sections" says "list": a word for reading.
What it can reach
- private-dataThe name "list_doc_sections" says "list" and "doc": it reads documents.
- untrusted-inputThe description's first sentence says "browse": it reads web pages, which anyone can write.
Description, as the server wrote it Browses the indexed documentation of a version. Without arguments it returns an overview: every section and how many pages it holds. With 'section' it returns that section's pages, with their URLs and descriptions. Use it to find out what exists before requesting a specific page. The response includes 'version_used': always tell the user which documentation version what you're telling them corresponds to. If it also carries 'version_warning', or 'version_sensitive': true on a result or in a page's 'version_note', the page changes between versions: say so explicitly and explain how to specify a different one. The index has no notion of edition or product, so if the answer depends on either, say which one you assumed.
Annotations the server declares
- title: List documentation sections
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_versionsLists the available documentation versions and the default one, plus where to look for the user's version-edition-product.No findings
Why it is in this group
- The name "list_versions" says "list": a word for reading.
Description, as the server wrote it Lists the available documentation versions and the default one, plus where to look for the user's version-edition-product. Use it if you don't know what value to pass for 'version'. It does NOT establish the user's deployment: for the procedure that does, and for the snippet that pins the result in their AGENTS.md/CLAUDE.md, call 'resolve_openvidu_version_edition_product'.
Annotations the server declares
- title: List documentation versions
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
resolve_openvidu_version_edition_productAnswers "which OpenVidu version, edition and product does this project use?".1 finding
Why it is in this group
- The name "resolve_openvidu_version_edition_product" says "resolve": a word for reading.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...et, locating the deployment URL and its credentials, querying the endpoint that reports ver..."
Description, as the server wrote it Answers "which OpenVidu version, edition and product does this project use?". Called with NO arguments, it returns the full procedure a coding agent follows to find out from the deployment itself: telling OpenVidu Platform (LiveKit SDKs) from OpenVidu Meet, locating the deployment URL and its credentials, querying the endpoint that reports version and edition, the fallbacks when that endpoint is unavailable, and the security rules that apply throughout. Use it before answering anything version-, edition- or product-dependent, unless the project's AGENTS.md/CLAUDE.md already pins it. Called WITH 'livekit_version', it additionally translates a LiveKit Server version (as printed in OpenVidu LiveKit Server's startup log) into the OpenVidu version(s) built on it — the fallback path of the procedure for deployments before 3.9.0, which cannot report their own version. Called with 'commands': true, it returns the exact commands that ask a deployment for its version and edition, keeping its credentials out of sight. Never infer any of the three facts from the project's client SDK dependency versions.
Annotations the server declares
- title: Resolve version, edition and product
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
search_docsSearches for a term in the indexed documentation of a version.Reads private dataNo findings
Why it is in this group
- The name "search_docs" says "search": a word for reading.
What it can reach
- private-dataThe name "search_docs" says "search" and "doc": it reads documents.
Description, as the server wrote it Searches for a term in the indexed documentation of a version. Applies stemming and domain synonyms, so morphological variants and synonyms also match. Pass exactly one of 'query' and 'queries' — the latter runs several searches in one call, each under 'searches'. When 'truncated' is true, 'next_page' is the value of 'page' for the next results. A match under a heading names it in 'heading', and its 'url' ends in that section's #anchor: get_doc_page on that URL reads just the section. May also return a `livekit` block: pointers to LiveKit's SDK documentation, which is NOT OpenVidu documentation and carries its own version caveat — read that block's own guidance before using it. The response includes 'version_used': always tell the user which documentation version what you're telling them corresponds to. If it also carries 'version_warning', or 'version_sensitive': true on a result or in a page's 'version_note', the page changes between versions: say so explicitly and explain how to specify a different one. The index has no notion of edition or product, so if the answer depends on either, say which one you assumed.
Annotations the server declares
- title: Search the documentation
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
8 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.
- Reads private data4
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__docs__get_doc_page"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:13 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
Findings
Matches of fixed checks, with the text they matched.
The description mentions "credentials".
What this check looks forMatched text
description: "...et, locating the deployment URL and its credentials, querying the endpoint that reports ver..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http docs https://docs-mcp.openvidu.io/mcpclaude mcp add --transport http docs https://docs-mcp.openvidu.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__docs__resolve_openvidu_version_edition_product",
"mcp__docs__list_versions",
"mcp__docs__list_doc_sections",
"mcp__docs__search_docs",
"mcp__docs__get_changelog",
"mcp__docs__get_pricing_info"
],
"ask": [
"mcp__docs__get_doc_page"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as docs. Review it before you use it.
Capability tags behind 4 rules
- mcp__docs__list_doc_sections private-data, untrusted-input
- mcp__docs__get_doc_page private-data, untrusted-input, outbound
- mcp__docs__search_docs private-data
- mcp__docs__get_changelog private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.openvidu/docs/verify?hash=d68043ecbb25bfd8fdc9764d19239d8d15934389382a3ace1188d22a9ed9e1e2" | jq -e '.changed == false'Pinned hash d68043ecbb25, from Nov 18, 2026, 13:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.openvidu/docs/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.openvidu/docs)Source: MCP Registry. Synced Oct 21, 2026, 18:52 UTC.
OpenVidu Docs MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the OpenVidu Docs MCP server safe?
- No scan can promise that. What its definitions show: 7 tools, all of which only read, and 1 finding from fixed checks. Read-only tools can still pass private data to a model.
Can the OpenVidu Docs MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the OpenVidu Docs MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the OpenVidu Docs MCP server have?
- 7 tools: 7 read. resolve_openvidu_version_edition_product, list_versions, list_doc_sections, get_doc_page, search_docs, get_changelog and get_pricing_info.
Does the OpenVidu Docs MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the OpenVidu Docs MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): get_doc_page.
Has the OpenVidu Docs MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.