Razi Dev Utilities MCP server
io.github.razikallayi/razi-devrazikallayistreamable-httpv1.0.0Scanned
Developer utilities over MCP: Base64 encode and decode, decode JWTs, format JSON, do percentages.
5 tools: 4 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
4 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Razi Dev Utilities MCP server can do
The Razi Dev Utilities MCP server is published by the GitHub account razikallayi. It has 5 tools. It can create or change data (4 tools: encode_base64, decode_base64, decode_jwt and calculate_percentage), but cannot delete data. 1 tool only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 20, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Changes things 4Claude Code: ask
calculate_percentageRun one of four percentage calculations on two numbers.No findings
Why it is in this group
- The description's first verb is "run": a word for a change.
Description, as the server wrote it 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.
decode_base64Decode a Base64 string back to UTF-8 text.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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_jwtDecode a JWT's header and payload for inspection.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
encode_base64Encode 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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Only reads 1Show 1 read-only tool
format_jsonValidate and re-print a JSON string.No findings
Why it is in this group
- The description's first verb is "validate": a word for reading.
Description, as the server wrote it 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.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:10 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 4
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://www.razi.pro/api/mcp/dev: tools/list returned 5 tools to an anonymous client, including encode_base64 (write), decode_base64 (write), decode_jwt (write), calculate_percentage (write)
Posture changes
- Nov 13, 2026
- HTTP status of an anonymous initialize: 402 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 4
- Protocol version: none to 2025-06-18
- Nov 6, 2026
- HTTP status of an anonymous initialize: 200 to 402
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 4 to 0
- Protocol version: 2025-06-18 to none
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. HTTP status of an anonymous initialize: 402 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 4 (and 1 more).View diff
- HTTP status of an anonymous initialize: 402 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 4
- Protocol version: none to 2025-06-18
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 402; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 4 -> 0 (and 1 more).View diff
- HTTP status of an anonymous initialize: 200 to 402
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 4 to 0
- Protocol version: 2025-06-18 to none
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http razi-dev https://www.razi.pro/api/mcp/devclaude mcp add --transport http razi-dev https://www.razi.pro/api/mcp/devRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__razi-dev__format_json"
],
"ask": [
"mcp__razi-dev__encode_base64",
"mcp__razi-dev__decode_base64",
"mcp__razi-dev__decode_jwt",
"mcp__razi-dev__calculate_percentage"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as razi-dev. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.razikallayi/razi-dev/verify?hash=604ad56c476ef3b38a202a55bf05bfbaadccac4725a237a74f5355e4bee82146" | jq -e '.changed == false'Pinned hash 604ad56c476e, from Nov 20, 2026, 09:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.razikallayi/razi-dev/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.razikallayi/razi-dev)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:45 UTC.
Razi Dev Utilities MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Razi Dev Utilities MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Razi Dev Utilities MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Razi Dev Utilities MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Razi Dev Utilities MCP server have?
- 5 tools: 4 write, 1 read. encode_base64, decode_base64, decode_jwt, calculate_percentage and format_json.
Does the Razi Dev Utilities MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Razi Dev Utilities MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Razi Dev Utilities MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.