Burroughts MCP (Master Control Program)

Field	Description
OS Name	MCP (Master Control Program)
Developer	Originally Burroughs Corporation (now Unisys)
First Released	1961 (for B5000)
Latest Version	Unisys ClearPath MCP (2025)
License Type	Proprietary (Unisys commercial systems)
Supported Platforms	Burroughs large systems, Unisys ClearPath MCP series
Still Active?	✅ Yes, still maintained by Unisys

Kernel & Architecture

Kernel Type: Stack-oriented OS, process control at hardware level

Based On: Designed specifically for the Burroughs B5000 hardware architecture

Architecture Support: Stack machine CPUs, later Unisys ClearPath MCP systems

Notable: Entire hardware+software stack designed together — no assembly, no general registers

Compiling: Entire OS, compilers, and apps written in high-level languages (not assembly)

Key Features

One of the first OSes to support virtual memory & multiprocessing

Designed around ALGOL-like languages (strong typing, recursion)

Integrated database management (DMSII)

Built-in security & audit trails from the beginning

High-level, stack-based instruction set — prevented many modern bugs (buffer overruns)

Transaction processing & record locking natively supported

Up to 99.999% uptime on mission-critical systems

Version History & Important Milestones ✅

Milestone	Year	Description
MCP on B5000	1961	First commercial OS written in a high-level language
B6500, B7000 series	1960s–70s	Extended stack machine & MCP capabilities
DMSII database	1972	Integrated high-availability DB system
Unisys formed	1986	Merger of Burroughs & Sperry, continued MCP line
ClearPath MCP systems	1990s–2020s	Modern CMOS hardware running MCP
MCP 21.x±	2025	Still running mission-critical banking & telco workloads

Target Audience & Use Cases

Large enterprises & governments: Banking, insurance, tax processing

Mission-critical workloads: Where 24x7 uptime is required

Database-heavy applications: Integrated with DMSII for decades

Organizations that value strong audit + security compliance

Pros & Cons

Pros	Cons
Extremely stable & reliable (99.999% uptime)	Proprietary, tied to Unisys hardware
Advanced from its inception (security, audit)	Hard for general devs to get hands-on
Written entirely in high-level language	Expensive — targeted at big enterprises
Very secure stack architecture prevents many bugs	Less modern app ecosystem compared to Linux/Windows

UI Demo & Visuals

MCP is primarily command-driven, often accessed via terminal

Screens of CANDE (Command AND Edit) — classic MCP command environment

Database queries via native DMSII tools

Modern ClearPath MCP can also have web admin dashboards

Show hardware rack images of Unisys ClearPath systems

Ecosystem & App Support

Runs ALGOL-based, COBOL, and later modern compilers

Native transaction processing systems tied into DMSII

Proprietary app stacks for banking, insurance, large-scale transaction engines

Supported by specialized Unisys tools & monitoring systems

Security & Updates

Security integrated at the language & OS level (type-safe from the start)

Strong audit logs & process accountability — decades ahead of time

MCP updates & patches delivered via Unisys under maintenance contracts

Hardware-level separation prevents many classes of exploits

Community, License & Development

License: Fully proprietary — requires Unisys hardware & support contracts

Maintained by Unisys with dedicated enterprise clients

Tiny open community, mostly internal or specialized consulting firms

Still actively developed for niche mission-critical environments

MCP & stack architecture often studied in computer science history for pioneering ideas