runtime MCP server
com.formatho/runtimeformatho.comstreamable-httpv0.3.0Scanned
Self-hosted MCP server: 26 deterministic dev, security, and EVM tools.
26 tools: 2 do something that can't be undone, 20 change things and 4 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 2
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here do something that can't be undone. 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 runtime MCP server can do
The runtime MCP server is published by formatho.com, a domain the MCP Registry verified. It has 26 tools. It can do things that cannot be undone, such as sending, paying or publishing (case.convert and evm.unit_convert) and create or change data (20 tools: base64.encode, base64.decode, url.encode, url.decode and 16 more), but cannot delete data. 4 tools only read.
2 tools can send data out of your system (case.convert and evm.unit_convert).
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 13, 2026, version 0.3.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.
26 tools
Can't be undone 2Claude Code: ask
case.convertConvert an identifier between camelCase, snake_case, kebab-case, CONSTANT_CASE, and Title Case.Can send data outNo findings
Why it is in this group
- The name "case.convert" says "convert": a word for a change.
- The input addresses people (input.to): what it sends cannot be taken back.
What it can reach
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Description, as the server wrote it Convert an identifier between camelCase, snake_case, kebab-case, CONSTANT_CASE, and Title Case. [dev · v1.0.0 · deterministic: true · permissions: none]
evm.unit_convertConvert EVM amounts between wei, gwei, and ether with exact BigInt math.Can send data outNo findings
Why it is in this group
- The name "evm.unit_convert" says "convert": a word for a change.
- The input addresses people (input.to): what it sends cannot be taken back.
What it can reach
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Description, as the server wrote it Convert EVM amounts between wei, gwei, and ether with exact BigInt math. [web3 · v1.0.0 · deterministic: true · permissions: none]
Changes things 20Claude Code: ask
base64.decodeBase64-decode to 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 Base64-decode to text. [data · v1.0.0 · deterministic: true · permissions: none]
base64.encodeBase64-encode text (standard alphabet).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 Base64-encode text (standard alphabet). [data · v1.0.0 · deterministic: true · permissions: none]
erc4626.mathExact EIP-4626 vault math in BigInt: convert assets to shares (round down) and shares to assets (round down), with optional virtual offsets.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 Exact EIP-4626 vault math in BigInt: convert assets to shares (round down) and shares to assets (round down), with optional virtual offsets. [defi · v1.0.0 · deterministic: true · permissions: none]
evm.checksum_addressEIP-55 checksum an Ethereum address, or verify a checksummed one.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 EIP-55 checksum an Ethereum address, or verify a checksummed one. [web3 · v1.0.0 · deterministic: true · permissions: none]
evm.create2_addressCompute the deterministic CREATE2 address: keccak256(0xff ‖ factory ‖ salt ‖ initCodeHash)[12:].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 Compute the deterministic CREATE2 address: keccak256(0xff ‖ factory ‖ salt ‖ initCodeHash)[12:]. [web3 · v1.0.0 · deterministic: true · permissions: none]
evm.decode_calldataExtract the 4-byte selector from raw calldata, match it against common signatures, and decode static (word-based) arguments: address, uint256, int256, bytes32, bool.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 Extract the 4-byte selector from raw calldata, match it against common signatures, and decode static (word-based) arguments: address, uint256, int256, bytes32, bool. [web3 · v1.0.0 · deterministic: true · permissions: none]
evm.function_selectorCompute the 4-byte function selector from a canonical signature, with reverse lookup against common signatures.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 Compute the 4-byte function selector from a canonical signature, with reverse lookup against common signatures. [web3 · v1.0.0 · deterministic: true · permissions: none]
evm.keccak256Keccak-256 (Ethereum flavor, NOT NIST SHA3-256) of arbitrary hex or 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 Keccak-256 (Ethereum flavor, NOT NIST SHA3-256) of arbitrary hex or text. [web3 · v1.0.0 · deterministic: true · permissions: none]
evm.storage_slotCompute Solidity storage slots: simple variables, mapping values (keccak(key ‖ p)), and dynamic array elements (keccak(p) + index).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 Compute Solidity storage slots: simple variables, mapping values (keccak(key ‖ p)), and dynamic array elements (keccak(p) + index). [web3 · v1.0.0 · deterministic: true · permissions: none]
evm.v4_hook_permissionsUniswap v4 hook permissions: compute the 14-bit permission field from hook-call names, or decode the field from a hook address (bits live in the LOW 14 bits: address & 0x3FFF).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 Uniswap v4 hook permissions: compute the 14-bit permission field from hook-call names, or decode the field from a hook address (bits live in the LOW 14 bits: address & 0x3FFF). [web3 · v1.0.0 · deterministic: true · permissions: none]
hash.textHash text with md5/sha1/sha256/sha384/sha512 (hex output).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 Hash text with md5/sha1/sha256/sha384/sha512 (hex output). MD5/SHA1 are for compatibility checks only, not security. [security · v1.0.0 · deterministic: true · permissions: none]
hex.encodeEncode text to hex, or decode hex (with or without 0x) to 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 Encode text to hex, or decode hex (with or without 0x) to text. [data · v1.0.0 · deterministic: true · permissions: none]
jwt.decodeDecode a JWT (JWS compact serialization) header and claims WITHOUT verifying the signature.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 (JWS compact serialization) header and claims WITHOUT verifying the signature. Reports expiry status from the exp claim. [security · v1.0.0 · deterministic: true · permissions: none]
random.stringGenerate a cryptographically random alphanumeric string.No findings
Why it is in this group
- The description's first verb is "generate": a word for a change.
Description, as the server wrote it Generate a cryptographically random alphanumeric string. [security · v1.0.0 · deterministic: false · permissions: none]
regex.testTest a regular expression against text: match result plus all capture groups.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 Test a regular expression against text: match result plus all capture groups. [dev · v1.0.0 · deterministic: true · permissions: none]
slug.generateConvert text to a URL-safe kebab-case slug.No findings
Why it is in this group
- The name "slug.generate" says "generate": a word for a change.
Description, as the server wrote it Convert text to a URL-safe kebab-case slug. [dev · v1.0.0 · deterministic: true · permissions: none]
timestamp.convertConvert Unix seconds/milliseconds to ISO 8601 (UTC) and back.No findings
Why it is in this group
- The name "timestamp.convert" says "convert": a word for a change.
Description, as the server wrote it Convert Unix seconds/milliseconds to ISO 8601 (UTC) and back. [dev · v1.0.0 · deterministic: true · permissions: none]
url.decodeDecode percent-encoded 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 percent-encoded text. [network · v1.0.0 · deterministic: true · permissions: none]
url.encodePercent-encode text (component encoding).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 Percent-encode text (component encoding). [network · v1.0.0 · deterministic: true · permissions: none]
uuid.v4Generate random UUID v4 values.No findings
Why it is in this group
- The description's first verb is "generate": a word for a change.
Description, as the server wrote it Generate random UUID v4 values. [security · v1.0.0 · deterministic: false · permissions: none]
Only reads 4Show 4 read-only tools
formatho.registryList every registered Formatho tool with version, category, deterministic flag, permissions, and Formatho Verified status.No findings
Why it is in this group
- The description's first verb is "list": a word for reading.
Description, as the server wrote it List every registered Formatho tool with version, category, deterministic flag, permissions, and Formatho Verified status. [meta · v1.0.0 · deterministic: true · permissions: none]
json.formatValidate and pretty-print JSON with a configurable indent level.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 pretty-print JSON with a configurable indent level. [data · v1.0.0 · deterministic: true · permissions: none]
json.minifyValidate JSON and strip all insignificant whitespace.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 JSON and strip all insignificant whitespace. [data · v1.0.0 · deterministic: true · permissions: none]
json.validateValidate JSON and report the parse error position if invalid.No findings
Why it is in this group
- The name "json.validate" says "validate": a word for reading.
Description, as the server wrote it Validate JSON and report the parse error position if invalid. [data · v1.0.0 · deterministic: true · permissions: none]
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.
- 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 out2
- 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, 18:38 UTC, unchanged since Oct 22, 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
- 22
- 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
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 22 tools that change things (2 irreversible, 20 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.formatho.com/mcp: tools/list returned 26 tools to an anonymous client, including case.convert (irreversible), evm.unit_convert (irreversible), base64.encode (write), base64.decode (write), url.encode (write) and 17 more
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.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.3.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http runtime https://mcp.formatho.com/mcpclaude mcp add --transport http runtime https://mcp.formatho.com/mcpRun 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__runtime__json_format",
"mcp__runtime__json_minify",
"mcp__runtime__json_validate",
"mcp__runtime__formatho_registry"
],
"ask": [
"mcp__runtime__base64_encode",
"mcp__runtime__base64_decode",
"mcp__runtime__url_encode",
"mcp__runtime__url_decode",
"mcp__runtime__slug_generate",
"mcp__runtime__hash_text",
"mcp__runtime__uuid_v4",
"mcp__runtime__random_string",
"mcp__runtime__jwt_decode",
"mcp__runtime__evm_keccak256",
"mcp__runtime__evm_function_selector",
"mcp__runtime__evm_create2_address",
"mcp__runtime__evm_storage_slot",
"mcp__runtime__evm_decode_calldata",
"mcp__runtime__evm_v4_hook_permissions",
"mcp__runtime__erc4626_math",
"mcp__runtime__timestamp_convert",
"mcp__runtime__regex_test",
"mcp__runtime__case_convert",
"mcp__runtime__hex_encode",
"mcp__runtime__evm_checksum_address",
"mcp__runtime__evm_unit_convert"
],
"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 runtime. Review it before you use it.
Capability tags behind 2 rules
- mcp__runtime__case_convert outbound
- mcp__runtime__evm_unit_convert outbound
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/com.formatho/runtime/verify?hash=f629c39a2cf388db8f033953f69cd3f807c38e5116c8bf72bd482b43e9842a36" | jq -e '.changed == false'Pinned hash f629c39a2cf3, from Nov 13, 2026, 07:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.formatho/runtime/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.formatho/runtime)Source: MCP Registry. Synced Oct 21, 2026, 17:55 UTC.
runtime MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the runtime MCP server safe?
- No scan can promise that. What its definitions show: 26 tools, 22 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 runtime MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the runtime MCP server do things that cannot be undone?
- Yes. 2 tools can send, pay, publish or merge: case.convert and evm.unit_convert.
What tools does the runtime MCP server have?
- 26 tools: 2 irreversible, 20 write, 4 read. case.convert, evm.unit_convert, base64.encode, base64.decode, url.encode, url.decode, slug.generate, hash.text and 18 more.
Does the runtime MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the runtime MCP server send data to outside services?
- 2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): case.convert and evm.unit_convert.
Has the runtime MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 13, 2026.