Razi Dev Utilities

io.github.razikallayi由 GitHub 帳號 razikallayi 發布v1.0.0更新於 Oct 24, 2026

Developer utilities over MCP: Base64 encode and decode, decode JWTs, format JSON, do percentages.

已驗證Streamable HTTP可網頁執行開發者工具

概覽

AI 產生的概覽

遠端 MCP 端點,提供 Base64 編解碼、JWT 解碼、JSON 格式化與百分比計算等小型開發工具。

可以做什麼
  • 將 UTF-8 文字編碼為標準 Base64,並在嚴格驗證後解碼回文字
  • 解碼 JWT 的標頭與內容以供檢視,並回傳到期資訊
  • 驗證 JSON 並重新輸出為縮排或壓縮後的字串
  • 對兩個數字執行四種百分比計算,採精確運算
適用情境
適合需要快速、可預期轉換或檢查的情境:檢視權杖中的宣告、把文字安全地放進 JSON 或請求標頭、整理 JSON,或進行百分比計算,而不必在本機執行程式碼。
執行需求
遠端 streamable HTTP 端點,不需本機執行環境或安裝套件。選用的 Authorization 標頭(形式為 'Bearer rz_...')可提高速率限制並歸屬用量。
安裝前請注意
選用的 Authorization 標頭會攜帶祕密權杖。JWT 簽章從不驗證,解出的宣告不應視為可信。Base64 輸出並非 URL 安全,用於查詢字串前需轉義。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Razi Dev Utilities,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.github.razikallayi%2Frazi-dev/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "razi-dev-utilities": {
      "type": "http",
      "url": "https://www.razi.pro/api/mcp/dev"
    }
  }
}

README

該儲存庫沒有 README。

工具

5

encode_base64

Encode UTF-8 text as standard Base64 (padded, A-Z a-z 0-9 + /), for embedding binary-unsafe content in JSON, data URIs, HTTP headers or Basic auth. Returns JSON { encoded }. The output uses the standard alphabet, so it is NOT URL-safe: '+' and '/' must still be percent-escaped before they go in a query string or path segment, and this tool does not do that. It is an encoding, not encryption — anyone can reverse it with decode_base64. Runs locally, no size limit beyond the request body.

輸入參數text必填

decode_base64

Decode a Base64 string back to UTF-8 text. Returns JSON { decoded }. Input is verified by re-encoding, so anything that is not genuine Base64 is rejected with an error instead of returning plausible garbage; binary payloads that are not valid UTF-8 will also fail. It handles Base64 and nothing else: a string of %20-style percent escapes is not Base64 and will be rejected rather than unescaped. For a JWT use decode_jwt, which splits the three segments and handles their base64url padding for you.

輸入參數encoded必填

decode_jwt

Decode a JWT's header and payload for inspection. Returns JSON { header, payload, signatureVerified, note, expiresAt, isExpired } — structured objects, not a rendered table. The signature is NEVER verified: that needs the issuer's key, which this service does not have, so signatureVerified is always false and the claims must be treated as untrusted, attacker-controllable input. Expiry is computed from the `exp` claim and is null when the token has none. Use decode_base64 for a bare Base64 string; this tool additionally splits the three segments and handles base64url padding.

輸入參數token必填

format_json

Validate and re-print a JSON string. Returns JSON { valid, formatted, minified } — the indented form and the whitespace-free form as plain strings, with no syntax highlighting or colour. Invalid JSON is rejected with the parser's own error message rather than returned as valid:false, so a successful call is proof the input parses. Round-tripping through the parser normalises the document: key order is kept but comments, trailing commas and duplicate keys are lost, and large integers lose precision.

輸入參數json必填indent

calculate_percentage

Run one of four percentage calculations on two numbers. Returns JSON { operation, result } (plus unit: 'percent' for the 'change' operation). The meaning of value1 and value2 depends on the operation, so read their descriptions before calling. Exact arithmetic, no model involved, no rounding applied. Ratios and general expressions are not supported.

輸入參數value1必填value2必填operation必填

版本歷史

1
  1. v1.0.0最新Sep 16, 2026

評分

已滿足適用檢查項的 75%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分

    請宣告包含 README 的 GitHub 儲存庫,或在 OAuth 受保護資源後設資料中提供 resource_documentation。

  • 授權條款10 分

    請在儲存庫或註冊中心條目中宣告授權條款。