BlockRazor Docs

io.blockrazorPublished by blockrazor.ioOfficial publisherv1.0.1Updated Nov 6, 2026

Search official BlockRazor docs and API references for sending and receiving transactions faster.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Remote MCP server for BlockRazor's official documentation: search docs and API references, read pages, ask questions, and report doc issues.

What you can do
  • Search the BlockRazor documentation for guides, code examples and API references
  • Fetch the full markdown content of a specific documentation page by URL
  • Ask a natural-language question and get a synthesized answer with links to source pages
  • Report outdated, contradictory or missing documentation back to the BlockRazor team
When to use it
Useful when helping someone integrate or troubleshoot BlockRazor, for example sending and receiving transactions faster, and you need authoritative answers from its official docs rather than guesses.
Requirements
A remote streamable HTTP endpoint at mcp.blockrazor.io; no packages, environment variables or headers are declared, and no authentication is declared.
Before you install
The feedback tool sends a report to the BlockRazor team, so review what is submitted before calling it. Answers and page content come from a third-party documentation service.

Installation

In SourceWeft

  1. Open BlockRazor Docs in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.blockrazor%2Fdocs/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "blockrazor-docs": {
      "type": "http",
      "url": "https://mcp.blockrazor.io/docs"
    }
  }
}

Tools

4

searchDocumentation

Search documentation

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.

Parametersqueryrequired

getPage

Get page content

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.

Parametersurlrequired

askQuestion

Ask a question

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.

Parametersgoalquestionrequired

sendFeedback

Send feedback

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.

ParametersgoalcontentrequiredpageUrlrequired

Version history

2
  1. v1.0.1LatestNov 6, 2026
  2. v1.0.0Sep 16, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.