# Razi Dev Utilities (remote · www.razi.pro)

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

- Trust score: 36/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `www.razi.pro`: 36/100 (this document), [markdown](https://verifymcp.io/servers/razikallayi-razi-dev/api-mcp-dev.md), [page](https://verifymcp.io/servers/razikallayi-razi-dev/api-mcp-dev)

## Channel facts

- Endpoint: `https://www.razi.pro/api/mcp/dev`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- **Schema Quality & AI Usability**: 0/100
  - Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Tool Safety**: 0/100
  - Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Capabilities**: 0/100
  - Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

**Unverified: 6 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Razi Dev Utilities MCP server?

Razi Dev Utilities is a hosted endpoint at https://www.razi.pro/api/mcp/dev, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http razikallayi-razi-dev 'https://www.razi.pro/api/mcp/dev'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "razikallayi-razi-dev": {
      "type": "remote",
      "url": "https://www.razi.pro/api/mcp/dev",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add razikallayi-razi-dev --url 'https://www.razi.pro/api/mcp/dev' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  razikallayi-razi-dev:
    url: "https://www.razi.pro/api/mcp/dev"
```

### Netclaw

```json
{
  "McpServers": {
    "razikallayi-razi-dev": {
      "Transport": "http",
      "Url": "https://www.razi.pro/api/mcp/dev"
    }
  }
}
```

### Vellum

```bash
assistant mcp add razikallayi-razi-dev -t streamable-http -u 'https://www.razi.pro/api/mcp/dev'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-09 (score 36, −29)

- [security regression] Endpoint reachability: reachable → behind authorisation
- [security regression] Authorization: unverified → fail
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → unverified
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-09-08 (score 65)

First indexed and scored.

## MCP tools (5)

### `encode_base64` (~138 tokens)

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 }. This is not URL-safe and is not escaping: for query strings and path segments use encode_url instead. It is an encoding, not encryption — anyone can reverse it with decode_base64. Runs locally, no size limit beyond the request body.

Input parameters:

- `text` (string, required): The plain text to encode, interpreted as UTF-8. Must be a string; raw binary cannot be passed through this parameter.

### `decode_base64` (~124 tokens)

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. For %20-style escapes use decode_url, and for a JWT use decode_jwt, which splits the three segments for you.

Input parameters:

- `encoded` (string, required): Standard Base64 text. Surrounding whitespace and missing '=' padding are tolerated; the URL-safe alphabet (- and _) is not.

### `decode_jwt` (~180 tokens)

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.

Input parameters:

- `token` (string, required): The full JWT: three base64url segments separated by dots (header.payload.signature). Surrounding whitespace is trimmed; a 'Bearer ' prefix is not stripped and will fail. Anything without exactly thre…

### `format_json` (~195 tokens)

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.

Input parameters:

- `indent` (number): Spaces per indent level in `formatted`, 0 to 10. Default 2; a value outside that range or a non-number silently falls back to 2. Use 0 for newlines with no indentation, or read `minified` for no whit…
- `json` (string, required): The JSON document as a string. Must be strict JSON — comments and trailing commas are parse errors.

### `calculate_percentage` (~259 tokens)

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.

Input parameters:

- `operation` (string, required): Which calculation to run. 'of' = value1 percent OF value2. 'increase' = value1 raised BY value2 percent. 'decrease' = value1 reduced BY value2 percent. 'change' = the percentage change going FROM val…
- `value1` (number, required): For 'of', the percentage itself (25 means 25%). For 'increase' and 'decrease', the base amount being adjusted. For 'change', the original value. Must be a finite number.
- `value2` (number, required): For 'of', the amount the percentage is taken from. For 'increase' and 'decrease', the percentage to apply (10 means 10%). For 'change', the new value. Must be a finite number.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/razikallayi-razi-dev/api-mcp-dev#diagnostics

## Score history

- 2026-09-20: 36
- 2026-09-19: 36
- 2026-09-18: 36
- 2026-09-17: 36
- 2026-09-16: 36
- 2026-09-15: 36
- 2026-09-14: 36
- 2026-09-13: 36
- 2026-09-12: 36
- 2026-09-11: 36
- 2026-09-10: 36
- 2026-09-09: 36
- 2026-09-08: 65

## Common questions

### What is the Razi Dev Utilities MCP server?

Razi Dev Utilities is an MCP server listed in the public MCP registry as io.github.razikallayi/razi-dev. Developer utilities over MCP: Base64 encode and decode, decode JWTs, format JSON, do percentages. This page covers its hosted endpoint (https://www.razi.pro/api/mcp/dev).

### Is the Razi Dev Utilities MCP server safe to use?

Razi Dev Utilities scores 36 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Razi Dev Utilities MCP server expose?

Razi Dev Utilities exposes 5 tools: encode_base64, decode_base64, decode_jwt, format_json, calculate_percentage. Their descriptions and schemas cost roughly 896 tokens of context every time the server is loaded.

### Does the Razi Dev Utilities MCP server require authentication?

Yes. Razi Dev Utilities asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Razi Dev Utilities MCP server still maintained?

Razi Dev Utilities is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://www.razi.pro/api/mcp/dev
- Repository: https://github.com/razikallayi/razikallayi.com
- Website: https://www.razi.pro/developer
- Changelog RSS feed: https://verifymcp.io/servers/razikallayi-razi-dev/api-mcp-dev.xml
- Changelog JSON feed: https://verifymcp.io/servers/razikallayi-razi-dev/api-mcp-dev.json
- HTML version of this page: https://verifymcp.io/servers/razikallayi-razi-dev/api-mcp-dev