Proa documentation MCP server
io.github.proa-web/docsproa-webstreamable-httpv1.0.0Scanned
Search and read official Proa Rust framework documentation. Public, read-only, no credentials.
2 tools: 2 only read.
- Reads private data · 2
- Reads text others write · 0
- Can send data out · 0
- No findings
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 Proa documentation MCP server can do
The Proa documentation MCP server is published by the GitHub account proa-web. It has 2 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
2 tools read private data (search_docs and get_doc).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 10, 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.
2 tools
Only reads 2Show 2 read-only tools
get_docRead a complete official Proa documentation page as Markdown with its title, description, and canonical route.Reads private dataNo findings
Why it is in this group
- The name "get_doc" says "get": a word for reading.
What it can reach
- private-dataThe name "get_doc" says "get" and "doc": it reads documents.
Description, as the server wrote it Read a complete official Proa documentation page as Markdown with its title, description, and canonical route. Supply a path returned by search_docs or resources/list. Only published documentation is accessible; arbitrary URLs and filesystem paths are not fetched.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
search_docsSearch official Proa Rust framework documentation by a case-insensitive phrase.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 Search official Proa Rust framework documentation by a case-insensitive phrase. Use this to find current APIs, render patterns, RSJS guidance, and deployment instructions. Returns titles, routes, Markdown URLs, and a pagination cursor; call get_doc with a returned path for the complete page.
Annotations the server declares
- 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.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.
- Reads private data2
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
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 19, 2026, 17:24 UTC, unchanged since Oct 28, 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.
No check matched anything in these tool definitions. That is not a safety guarantee.
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://proa.so/mcpclaude mcp add --transport http docs https://proa.so/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__search_docs",
"mcp__docs__get_doc"
],
"ask": [],
"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 2 rules
- mcp__docs__search_docs private-data
- mcp__docs__get_doc 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.github.proa-web/docs/verify?hash=d683e0508a077d36bc16dc46638b173e2b923f8655b583007a3e417c8dbe1aec" | jq -e '.changed == false'Pinned hash d683e0508a07, from Nov 10, 2026, 00:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.proa-web/docs/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.proa-web/docs)Source: MCP Registry · repository. Synced Oct 28, 2026, 17:17 UTC.
Proa documentation MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Proa documentation MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the Proa documentation MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Proa documentation 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 Proa documentation MCP server have?
- 2 tools: 2 read. search_docs and get_doc.
Does the Proa documentation MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Proa documentation MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Proa documentation MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.