A credential no platform can revoke.
Every entry is signed, self-hosted on the graduate's own domain, and federated. Verify it from the command line. Click one — it runs.
A credential no
platform can revoke.
Every entry is signed, self-hosted on the graduate’s own domain, and federated. Verify it from the command line. Click one — it runs.
--BEGIN MCS CREDENTIAL-- holder: Dana Okafor degree: M. Agent Operations track: B · cohort MMXXVI-1 capstone: ledgerloop.app [200 OK] gate: CONFERRED · score 94 key: 9F2A 4C71 … E0B3 --END MCS CREDENTIAL--
Credential questions
How do I verify a credential?
From the command line: $ mcs verify <name>.cert. The credential is a signed artifact on the graduate's own domain — you're verifying their signature, not ours. We publish the public key; graduates sign with their private key. If the domain disappears, the key fingerprint is still in the register.
What if the graduate's domain goes offline?
The key fingerprint and gate record are permanently in the register at moderncoding.school/register. The credential is also syndicated to the webring and verifiable against the register's record. Domain loss reduces verifiability to the key fingerprint only — which is still cryptographic proof of the gate.
Can employers verify without a CLI tool?
Yes. Every entry in the register has a public verification page. The CLI tool (mcs verify) is FOSS and installable in 30 seconds — we'd prefer employers use it, but the web interface exists for the rest.
What is the webring?
Every graduate who self-hosts their credential is invited to join the MCS webring. The webring links graduate sites, projects, and credentials. It's an ironic nod to the 2000s web and a practical credentialing network. Navigate it with prev/random/next.