Is io.github.bowenerchen/cipherhub up? Live MCP status
Yes, it is up. It answered an MCP initialize with no credential and negotiated protocol 2025-03-26.
A stock client connected with no credential and negotiated 2025-03-26. Use it.
| Outcome | usable |
|---|---|
| HTTP status | 200 |
| Protocol version | 2025-03-26 |
| Server says it is | cipherhub-mcp 1.11.0 |
| Answered in | 1339 ms |
| Endpoint checked | https://tools.cipherhub.cloud/cipherhub/mcp |
| Checked |
One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.
Live status every few hours: Wellknown
Email me when this server changes
That was one look. To hear when it stops answering or its tools change, leave an address.
Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.
Monthly census, 6 October 2026
The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).
Agent discovery documents at this origin
| A2A agent card | Not published (HTTP 404)./.well-known/agent-card.json |
|---|---|
| MCP server card (SEP-2127) | Not published (HTTP 404).https://tools.cipherhub.cloud/cipherhub/mcp/server-card |
| MCP server card (SEP-1649 location) | Not published (HTTP 404)./.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026 |
| Web Bot Auth key directory | Not published (HTTP 404)./.well-known/http-message-signatures-directory |
Read at https://tools.cipherhub.cloud with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.
Tool changes between snapshots
In the 2026-10 snapshot it listed 55 tools: asn1_parse, block_cipher, cbor_decode, cbor_encode, cert_parse, cert_verify, cms_enveloped_decrypt, cms_enveloped_encrypt, cms_enveloped_parse, cms_signed_sign, cms_signed_verify, cose_sign1_parse, cose_sign1_sign, cose_sign1_verify, ctr_cipher, data_padding, der_encode, ecc_key_exchange, ecc_key_sign, ecc_key_verify, generate_ecc, generate_random_data, generate_rsa, generate_sm2, generate_sm9, hash_sum, hello, hmac_sum, hybrid_kex, key_derivation, ml_dsa_compute_mu, ml_dsa_keygen, ml_dsa_sign, ml_dsa_verify, ml_kem_decap, ml_kem_encap, ml_kem_keygen, rsa_decryption, rsa_encryption, rsa_sign, rsa_verify, sm2_decryption, sm2_encryption, sm2_private_key_structure_parse, sm2_public_key_to_hex, sm2_sign, sm2_verify, sm9_decryption, sm9_encryption, sm9_extract_key, sm9_sign, sm9_verify, stream_cipher, xts_cipher, zuc_cipher.
Its tools changed between 2026-09 and 2026-10:
- Added (13):
asn1_parse,cbor_decode,cbor_encode,cms_enveloped_decrypt,cms_enveloped_encrypt,cms_enveloped_parse,cms_signed_sign,cms_signed_verify,cose_sign1_parse,cose_sign1_sign,cose_sign1_verify,der_encode,xts_cipher
Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.
The listing
| Registry name | io.github.bowenerchen/cipherhub |
|---|---|
| Title | CipherHUB Cryptography Toolkit |
| Description | Production-grade cryptography toolkit with 31 MCP tools for classical, PQC, and KMS workflows. |
| Endpoint | https://tools.cipherhub.cloud/cipherhub/mcp |
| Publisher repository | https://github.com/bowenerchen/CipherHUB-MCP-Server |
| Version | 1.9.4 |
| Listing updated |
Also
The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt