BlockRazor Docs MCP server
io.blockrazor/docsblockrazor.iostreamable-httpv1.0.1Scanned
Search official BlockRazor docs and API references for sending and receiving transactions faster.
4 tools: 1 do something that can't be undone, 1 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 4
- Can send data out · 2
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- 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 BlockRazor Docs MCP server can do
The BlockRazor Docs MCP server is published by blockrazor.io, a domain the MCP Registry verified. It has 4 tools. It can do things that cannot be undone, such as sending, paying or publishing (sendFeedback) and create or change data (1 tool: askQuestion), but cannot delete data. 2 tools only read.
4 tools bring in text other people can write (searchDocumentation, getPage, askQuestion and 1 more); 2 tools can send data out of your system (getPage and sendFeedback).
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, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 20, 2026, version 1.0.1.
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.
4 tools
Can't be undone 1Claude Code: ask
sendFeedbackReport an issue in the documentation of BlockRazor so the team can fix it.Reads text others writeCan send data outNo findings
Why it is in this group
- The name "sendFeedback" says "send": a word for sending, and what is sent cannot be taken back.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe name "sendFeedback" says "send": it sends or publishes something to other people.
Description, as the server wrote it Report an issue in the documentation of BlockRazor so the team can fix it. Use it whenever, while helping a user, you come across content that is outdated, contradictory, missing information, or otherwise unhelpful. Also use it when the user themselves reports a problem with the docs, even if you could not verify it yourself. If it's your own observation, do a quick sanity check that the issue is real before reporting — no need to exhaustively re-read the page. Send one call per distinct issue and do not report the same issue twice in a conversation. Do not use this tool to confirm that a page is accurate; it is for reporting problems only.
Annotations the server declares
- title: Send feedback
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Changes things 1Claude Code: ask
askQuestionAsk a natural-language question about BlockRazor and get a synthesized answer, with links to the source pages.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Ask a natural-language question about BlockRazor and get a synthesized answer, with links to the source pages. Prefer this over `searchDocumentation` when you want a direct answer to a question rather than a list of matching pages; use `searchDocumentation`/`getPage` when you need to browse or read full pages yourself.
Annotations the server declares
- title: Ask a question
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Only reads 2Show 2 read-only tools
getPageFetch the full markdown content of a specific documentation page from BlockRazor.Reads text others writeCan send data outNo findings
Why it is in this group
- The name "getPage" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- 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 Fetch the full markdown content of a specific documentation page from BlockRazor. Use this when you have a page URL and want to read its content. Accepts full URLs (e.g. https://docs.blockrazor.io/getting-started). Since `searchDocumentation` returns partial content, use `getPage` to retrieve the complete page when you need more details. The content includes links you can follow to navigate to related pages.
Annotations the server declares
- title: Get page content
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
searchDocumentationSearch across the documentation to find relevant information, code examples, API references, and guides.Reads text others writeNo findings
Why it is in this group
- The name "searchDocumentation" says "search": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Search across the documentation to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about BlockRazor, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages.
Annotations the server declares
- title: Search documentation
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
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 private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write4
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out2
- 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 20, 2026, 18:55 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
- 2
- 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
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (1 irreversible, 1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.blockrazor.io/docs: tools/list returned 4 tools to an anonymous client, including sendFeedback (irreversible), askQuestion (write)
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.
Tools1 changed.~1 changedView diff
- Changed:searchDocumentationOnly readsinputSchema
Tools2 changed.~2 changedView diff
- Changed:getPageOnly readsdescription
- Changed:sendFeedbackCan't be undoneinputSchema
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http docs https://mcp.blockrazor.io/docsclaude mcp add --transport http docs https://mcp.blockrazor.io/docsRun 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__searchDocumentation"
],
"ask": [
"mcp__docs__getPage",
"mcp__docs__askQuestion",
"mcp__docs__sendFeedback"
],
"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__searchDocumentation untrusted-input
- mcp__docs__getPage untrusted-input, outbound
- mcp__docs__askQuestion untrusted-input
- mcp__docs__sendFeedback untrusted-input, outbound
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.blockrazor/docs/verify?hash=2debd74c3fc489e43bb628e4c90166cd41131eae1e2a34fc58209533008b14ee" | jq -e '.changed == false'Pinned hash 2debd74c3fc4, from Nov 20, 2026, 03:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.blockrazor/docs/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.blockrazor/docs)Source: MCP Registry. Synced Nov 6, 2026, 03:17 UTC.
BlockRazor Docs MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the BlockRazor Docs MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the BlockRazor 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 BlockRazor Docs MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: sendFeedback.
What tools does the BlockRazor Docs MCP server have?
- 4 tools: 1 irreversible, 1 write, 2 read. sendFeedback, askQuestion, searchDocumentation and getPage.
Does the BlockRazor Docs MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the BlockRazor Docs MCP server send data to outside services?
- 2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): getPage and sendFeedback.
Has the BlockRazor Docs MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.