Razi Dev Utilities MCP Server

by razikallayi Your server? Claim it

answering

Razi Dev Utilities is answering right now. Last checked 11 min ago. 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 60 days of history · worst day 0%

60 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

132 ms

Response time

average over 24h

authentication required

Access

streamable-http

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 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

Settings → Connectors → Add custom connector, then paste this address

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

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

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

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	needs auth	91 ms	11 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.

49 installs/wk local only

Devutils

by ofershap

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

81 installs/wk local only

DevUtils MCP Server

by paladini

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

51 installs/wk local only

Base64

by ryudi84

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

local only

Razi Web Tools

by razikallayi

Web and URL utilities over MCP: shorten URLs, screenshot pages, read page metadata, encode URLs.

6 tools answering

ellmos CodeCommander

by ellmos-ai

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

421 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.

81 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

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 91 of 91 checks got a reply (100.0%), average response time 132 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.

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 in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.

Does Razi Dev Utilities need an API key?

Yes. Every time we knock, Razi Dev Utilities answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is Razi Dev Utilities?

It answers our handshake in 132 ms on average, which is faster than 89% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.