Security & Testing

bytescope.dev

An MCP server for security and data-integrity utilities that detects file types, computes hashes and CRCs, reverses CRC models, and decodes X.509 certificates and CSRs.

1 endpoint23 known toolsFirst detected September 30, 2026Last detected September 30, 2026

ENDPOINT 1

https://bytescope.dev/api/mcp

No auth detected

MCP server metadata

Name: bytescope
Version: 0.1.0

Capabilities

toolsresources

Server instructions

ByteScope: offline file analysis and reference lookups. Binary arguments are base64 (default) or hex strings in `data` with `encoding`; file paths are never accepted. lookup_* tools answer only from their tables and return found: false instead of guessing.

Known tools 23

detect_file_type

Identify a file's real type from its leading bytes (magic numbers), with a confidence level, MIME type and usual extensions.

Inferred read-only

hash_bytes

Hash bytes with MD5, SHA-1, SHA-256, SHA-512 and/or CRC-32 (the zip/PNG/Ethernet CRC-32/ISO-HDLC).

Inferred read-only

crc_calculate

Compute a CRC over bytes, either with a named model from the reveng catalogue (113 models, e.g.

Inferred read-only

crc_reverse

Recover the CRC model from known message/checksum pairs: first tries every model in the reveng catalogue, then brute-forces 8- and 16-bit polynomials within a time budget.

Potential side effects

decode_certificate

Decode X.509 certificates and CSRs: subject, issuer, SANs, validity window and status, signature algorithm, public key, key usage, fingerprints.

Inferred read-only

subnet_calc

IPv4/IPv6 subnet calculator: CIDR → network, broadcast (IPv4 only), usable host range, netmask, wildcard, address count and address class/special-range classification.

Inferred read-only

parse_pcap

Parse a pcap or pcapng capture: file summary (format, link types, packet count, time span), a Wireshark-style packet list (protocol, source, destination, info), TCP/UDP stream summaries and protocol hierarchy / conversation statistics.

Inferred read-only

inspect_elf

Inspect an ELF binary (executable, shared object, object file, core): header (class, endianness, machine, type, entry point), program headers, section headers, symbol tables, dynamic section (NEEDED libraries, SONAME), notes (build id) and parse warnings.

Inferred read-only

parse_intel_hex

Map a firmware image: Intel HEX, Motorola S-record or UF2 → contiguous address segments, gaps, start address, record errors (bad checksums, overlaps) and, for UF2, the family ids.

Inferred read-only

decode_hid_descriptor

Decode a USB HID report descriptor: annotated item listing (like the HID Descriptor Tool), collections, and every input/output/feature report with bit offsets, sizes, usages and logical ranges.

Inferred read-only

parse_exif

Read image metadata from a JPEG, PNG or raw TIFF/EXIF block: camera make/model, lens, exposure, ISO, focal length, orientation, capture time, ICC profile presence, plus the list of metadata carriers (EXIF, XMP, ICC, comments, text chunks, trailers) with byte offsets.

Inferred read-only

sqlite_schema

Read a SQLite database file's structure: every table with its CREATE statement, columns (declared type, primary-key position, NOT NULL, default, foreign-key target) and row count, plus indexes (unique, origin, columns), views, triggers, page size, page count, text encoding, user_version, journal mode and the SQLite version that last wrote the file.

Potential side effects

convert_subtitle

Convert subtitles between SRT, WebVTT and ASS/SSA.

Inferred read-only

generate_fixture

Generate a real, standards-conformant test file for unit tests instead of hand-assembling bytes: images, archives (including encrypted, split or deliberately corrupted ZIPs), packet captures, self-signed certificates (valid, expiring in N days, expired or not yet valid), audio/video, SQLite, firmware images and PDFs.

Inferred read-only

lookup_usb_vendor

Look up a USB vendor id (VID) in the linux-usb.org usb.ids database — the same data lsusb uses.

Inferred read-only

lookup_usb_product

Look up a USB product by vendor id and product id (VID:PID) in the linux-usb.org usb.ids database.

Inferred read-only

lookup_ble_uuid

Look up a Bluetooth LE GATT UUID in the Bluetooth SIG assigned-numbers tables (services, characteristics, descriptors) and a list of well-known vendor UUIDs.

Inferred read-only

lookup_hid_usage

Look up a USB HID usage in the HID Usage Tables: usage page + usage id → names.

Inferred read-only

lookup_midi_cc

Look up a MIDI 1.0 Control Change number (0-127) in the MMA controller assignment table, e.g.

Inferred read-only

lookup_midi_manufacturer

Look up a MIDI System Exclusive manufacturer id (the byte(s) after F0): one byte 01-7F (e.g.

Inferred read-only

lookup_port

Look up a TCP/UDP port number in ByteScope's port reference (the well-known service ports developers actually hit: 22, 443, 3306, 5432, 6379, 27017 …): service, transport, whether IANA assigned it, what it is for and its security exposure.

Inferred read-only

lookup_http_status

Look up an HTTP status code in ByteScope's status reference: name, class, defining standard, what it means and how it is confused with its neighbours.

Inferred read-only

lookup_file_signature

Look up which file formats' magic-number signatures match the given leading bytes, using ByteScope's format catalogue.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.bytescope]
url = "https://bytescope.dev/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "bytescope": {
      "type": "http",
      "url": "https://bytescope.dev/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: bytescope
Remote MCP URL: https://bytescope.dev/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "bytescope": {
      "url": "https://bytescope.dev/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "bytescope": {
      "type": "http",
      "url": "https://bytescope.dev/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "bytescope",
  "transport": "streamable-http",
  "url": "https://bytescope.dev/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for bytescope.dev was fetched 2026-10-01T23:12:58.042Z.

Trust status Neutral

bytescope.dev is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.