Razi Dev Utilities MCP Server

by razikallayi Your server? Claim it

not responding

Razi Dev Utilities is listed as active in the registry but did not answer our last check. It exposes 5 tools.

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

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 14 days of history · worst day 0%

14 days agonow

0.0%

Uptime 24h

0 of 91 checks

Tools

read from the server

837 ms

Response time

average over 24h

open, no key

Access

streamable-http

Razi Dev Utilities does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add razi-dev --transport http https://www.razi.pro/api/mcp/dev

~/Library/Application Support/Claude/claude_desktop_config.json

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

~/.codex/config.toml

[mcp_servers.razi-dev]
url = "https://www.razi.pro/api/mcp/dev"

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

decode

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.

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.

calculate

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.

encode

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.

format

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.

Endpoints

URL	Transport	State	Latency	Checked
https://www.razi.pro/api/mcp/dev	streamable-http	answering	837 ms	5 min ago

Alternatives to Razi Dev Utilities

same job, measured the same way

Textavia MCP

by catorch

Local-first MCP server for text, JSON, Base64, CSV, regex, and developer utilities.

33 installs/wk local only

Devutils

by ofershap

Developer utilities MCP: base64, UUID, hash, JWT decode, cron, timestamps.

30 installs/wk local only

DevUtils MCP Server

by paladini

36 local developer utilities for AI agents. Hash, encoding, UUID, JWT, JSON, network, text.

36 installs/wk local only

Base64

by ryudi84

MCP server for Base64, URL, and HTML encoding/decoding

local only

ellmos CodeCommander

by ellmos-ai

Developer MCP server: code analysis, JSON repair, imports, diffs, regex, format conversion.

261 installs/wk local only

Agent Toolkit

by white-hat-lab

Pay-per-call developer utilities and npm supply-chain security tools for coding agents, over x402.

45 installs/wk local only

Developer Tools

by programmes

65+ free in-browser developer tools (JSON, Base64, JWT, hash, regex…) callable over MCP.

59 tools answering

Devtools

by kira-autonoma

23 developer utilities — base64, JWT, UUID, hash, QR, regex, timestamps. No API keys.

31 installs/wk local only

Razi Dev Utilities — questions

Answers built from our own checks of this server.

What can Razi Dev Utilities do?

It exposes 5 tools, read directly from the server on our last check. Among them: calculate_percentage, decode_base64, decode_jwt, encode_base64, format_json. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Razi Dev Utilities working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 837 ms. The bar chart above shows every period we have measured.

Is Razi Dev Utilities still maintained?

The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.

The registry lists Razi Dev Utilities as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect Razi Dev Utilities?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Razi Dev Utilities need an API key?

No. Razi Dev Utilities completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.