# EBCDIC to ASCII (remote · mcp.phreakocious.net)

An MCP server that measures MCP client behaviour and converts EBCDIC to ASCII, which nobody needs.

- Trust score: 66/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

- remote · `mcp.phreakocious.net`: 66/100 (this document), [markdown](https://verifymcp.io/servers/phreakocious-ebcdic/mcp.md), [page](https://verifymcp.io/servers/phreakocious-ebcdic/mcp)

## Channel facts

- Endpoint: `https://mcp.phreakocious.net/mcp`
- 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-11-06.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 228 tokens (~76/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 87/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 60% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the EBCDIC to ASCII MCP server?

EBCDIC to ASCII is a hosted endpoint at https://mcp.phreakocious.net/mcp, 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 phreakocious-ebcdic 'https://mcp.phreakocious.net/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "phreakocious-ebcdic": {
      "url": "https://mcp.phreakocious.net/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "phreakocious-ebcdic": {
      "type": "http",
      "url": "https://mcp.phreakocious.net/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.phreakocious-ebcdic]
url = "https://mcp.phreakocious.net/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "phreakocious-ebcdic": {
      "type": "remote",
      "url": "https://mcp.phreakocious.net/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add phreakocious-ebcdic --url 'https://mcp.phreakocious.net/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  phreakocious-ebcdic:
    url: "https://mcp.phreakocious.net/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "phreakocious-ebcdic": {
      "Transport": "http",
      "Url": "https://mcp.phreakocious.net/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add phreakocious-ebcdic -t streamable-http -u 'https://mcp.phreakocious.net/mcp'
```

### Other

```json
{
  "mcpServers": {
    "phreakocious-ebcdic": {
      "type": "http",
      "url": "https://mcp.phreakocious.net/mcp"
    }
  }
}
```

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-11-06 (score 66, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-05 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 65, +7)

- [security improvement] Authorization: unverified → partial

### 2026-11-02 (score 58, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-01 (score 57)

First indexed and scored.

## MCP tools (3)

### `echo` (~37 tokens)

Returns the text you send. Exists to measure MCP client behaviour; this server records who connects.

Input parameters:

- `text` (string, required): Text to echo back

### `ebcdic_to_ascii` (~76 tokens)

Decodes EBCDIC bytes, given as hex digits, to text. Code pages cp037 (default), cp500, cp273. Nobody needs this; it exists so that a call to it means something.

Input parameters:

- `codepage` (string)
- `hex` (string, required): EBCDIC bytes as hex digits

### `ascii_to_ebcdic` (~59 tokens)

Encodes ASCII text to EBCDIC bytes, returned as hex digits. Code pages cp037 (default), cp500, cp273.

Input parameters:

- `codepage` (string)
- `text` (string, required): ASCII text to encode

## Diagnostics

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

## Score history

- 2026-11-06: 66
- 2026-11-05: 66
- 2026-11-04: 65
- 2026-11-03: 65
- 2026-11-02: 58
- 2026-11-01: 57

## Common questions

### What is the EBCDIC to ASCII MCP server?

EBCDIC to ASCII is an MCP server listed in the public MCP registry as io.github.phreakocious/ebcdic. An MCP server that measures MCP client behaviour and converts EBCDIC to ASCII, which nobody needs. This page covers its hosted endpoint (https://mcp.phreakocious.net/mcp).

### Is the EBCDIC to ASCII MCP server safe to use?

EBCDIC to ASCII scores 66 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 EBCDIC to ASCII MCP server expose?

EBCDIC to ASCII exposes 3 tools: echo, ebcdic_to_ascii, ascii_to_ebcdic. Their descriptions and schemas cost roughly 172 tokens of context every time the server is loaded.

### Does the EBCDIC to ASCII MCP server require authentication?

No. We connected to EBCDIC to ASCII without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the EBCDIC to ASCII MCP server still maintained?

EBCDIC to ASCII is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the EBCDIC to ASCII MCP server?

VerifyMCP ran 12 checks on EBCDIC to ASCII, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about EBCDIC to ASCII: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.phreakocious.net/mcp
- Website: https://phreakocious.net/
- Changelog RSS feed: https://verifymcp.io/servers/phreakocious-ebcdic/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/phreakocious-ebcdic/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/phreakocious-ebcdic/mcp.json
- HTML version of this page: https://verifymcp.io/servers/phreakocious-ebcdic/mcp