Skip to content

EBCDIC to ASCII MCP server

io.github.phreakocious/ebcdicphreakociousstreamable-httpv1.0.0Scanned

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

4 tools: 2 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 2 write, 2 read.
  • Reads private data · 1
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 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.
Govern this server →

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 EBCDIC to ASCII MCP server can do

The EBCDIC to ASCII MCP server is published by the GitHub account phreakocious. It has 4 tools. It can create or change data (2 tools: ebcdic_to_ascii and ascii_to_ebcdic), but cannot delete data. 2 tools only read.

1 tool reads private data (ebcdic_ref_06182cbd1a).

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, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 14, 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.

4 tools

Changes things 2Claude Code: ask
  • ascii_to_ebcdicEncodes ASCII text to EBCDIC bytes, returned as hex digits.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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Encodes ASCII text to EBCDIC bytes, returned as hex digits. Code pages cp037 (default), cp500, cp273.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • ebcdic_to_asciiDecodes EBCDIC bytes, given as hex digits, 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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
Only reads 2Show 2 read-only tools
  • ebcdic_ref_06182cbd1aReturns EBCDIC reference table 06182cbd1a.Reads private dataNo findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "return" and "table": it reads databases.
    Description, as the server wrote it
    Returns EBCDIC reference table 06182cbd1a. Exists to measure which directories republish this tool list.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • echoReturns the text you send.No findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.
    Description, as the server wrote it
    Returns the text you send. Exists to measure MCP client behaviour; this server records who connects.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false

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 untrusted-input or outbound.

Reads private data1
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.

Tools listed without sign-in

Looked at Nov 16, 2026, 14:22 UTC, unchanged since Nov 2, 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
2
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 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.phreakocious.net/mcp: tools/list returned 4 tools to an anonymous client, including ebcdic_to_ascii (write), ascii_to_ebcdic (write)

    What this check looks for

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.

  1. Tools1 added, 3 changed.+1 added~3 changedView diff

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http ebcdic https://mcp.phreakocious.net/mcp
claude mcp add --transport http ebcdic https://mcp.phreakocious.net/mcp

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

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__ebcdic__echo",
      "mcp__ebcdic__ebcdic_ref_06182cbd1a"
    ],
    "ask": [
      "mcp__ebcdic__ebcdic_to_ascii",
      "mcp__ebcdic__ascii_to_ebcdic"
    ],
    "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 ebcdic. Review it before you use it.

Capability tags behind 1 rule
  • mcp__ebcdic__ebcdic_ref_06182cbd1a private-data

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.phreakocious/ebcdic/verify?hash=b759930bb6aa3117e0ea4716060e8360e1f57e4afa71bb2a5fd2f1911e0da2ae" | jq -e '.changed == false'

Pinned hash b759930bb6aa, from Nov 14, 2026, 02: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.phreakocious/ebcdic/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.phreakocious/ebcdic
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.phreakocious/ebcdic.svg)](https://radar.anlyon.com/servers/io.github.phreakocious/ebcdic)

Source: MCP Registry. Synced Nov 1, 2026, 04:17 UTC.

EBCDIC to ASCII MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the EBCDIC to ASCII MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 2 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 EBCDIC to ASCII MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the EBCDIC to ASCII 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 EBCDIC to ASCII MCP server have?

4 tools: 2 write, 2 read. ebcdic_to_ascii, ascii_to_ebcdic, echo and ebcdic_ref_06182cbd1a.

Does the EBCDIC to ASCII MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the EBCDIC to ASCII MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the EBCDIC to ASCII MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 14, 2026. Every change is on this page and in its Atom feed.