Skip to content

IDigiTrust SSL Toolkit MCP server

io.github.Mintreetech/ssl-toolkit-mcpMintreetechstreamable-httpv1.5.0Scanned

Free SSL/PKI tools: HTTPS audit incl. GM SM2/TLCP, DCV pre-check, CSR, cert decode, P12/JKS.

8 tools: 6 change things and 2 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

6 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 IDigiTrust SSL Toolkit MCP server can do

The IDigiTrust SSL Toolkit MCP server is published by the GitHub account Mintreetech. It has 8 tools. It can create or change data (6 tools: cert.decode, cert.match, convert.run, csr.decode and 2 more), but cannot delete data. 2 tools only read.

1 tool brings in text other people can write (inspect.run).

The fixed checks matched 2 findings (credentials-mention). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 9, 2026, version 1.5.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.

8 tools

Changes things 6Claude Code: ask
  • cert.decode解析证书(PEM / base64-DER / 裸 DER):全字段展开 + 整链吊销检查(OCSP / CRL,含交叉证书)+ 上传链时验证匹配关系并识别根证书。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.
    Description, as the server wrote it
    解析证书(PEM / base64-DER / 裸 DER):全字段展开 + 整链吊销检查(OCSP / CRL,含交叉证书)+ 上传链时验证匹配关系并识别根证书。
  • cert.match证书 / 私钥 / CSR 匹配验证(SubjectPublicKeyInfo SHA-256 指纹比对)。安全警告:请勿提交生产私钥及密码,仅使用测试材料。 SECURITY WARNING: Do not send production private keys or passwords to this hosted service.1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...swords to this hosted service. Use test credentials only."

      What this check looks for
    Description, as the server wrote it
    证书 / 私钥 / CSR 匹配验证(SubjectPublicKeyInfo SHA-256 指纹比对)。安全警告:请勿提交生产私钥及密码,仅使用测试材料。 SECURITY WARNING: Do not send production private keys or passwords to this hosted service. Use test credentials only.
  • convert.run证书 / 密钥格式转换:PEM / P12 / JKS 任意方向(已知原密码时可修改密码)。安全警告:请勿提交生产私钥、密钥库及密码,仅使用测试材料。 SECURITY WARNING: Do not send production private keys, keystores (PFX/P12 or JKS), or passwords to this …1 finding

    Why it is in this group

    • The name "convert.run" says "convert": a word for a change.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...swords to this hosted service. Use test credentials only."

      What this check looks for
    Description, as the server wrote it
    证书 / 密钥格式转换:PEM / P12 / JKS 任意方向(已知原密码时可修改密码)。安全警告:请勿提交生产私钥、密钥库及密码,仅使用测试材料。 SECURITY WARNING: Do not send production private keys, keystores (PFX/P12 or JKS), or passwords to this hosted service. Use test credentials only.
  • csr.decode解析 CSR(PEM / base64-DER / 裸 DER):Subject、公钥算法、SAN、请求扩展、SPKI 指纹、自签名完整性校验。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.
    Description, as the server wrote it
    解析 CSR(PEM / base64-DER / 裸 DER):Subject、公钥算法、SAN、请求扩展、SPKI 指纹、自签名完整性校验。
  • csr.generate生成 RSA / ECC 私钥与对应 CSR;入参为 Subject + 算法 + 哈希 + SAN。安全警告:托管服务生成的私钥仅用于测试;生产密钥请在本地生成。 SECURITY WARNING: Hosted key generation is for testing only.No findings

    Why it is in this group

    • The name "csr.generate" says "generate": a word for a change.
    Description, as the server wrote it
    生成 RSA / ECC 私钥与对应 CSR;入参为 Subject + 算法 + 哈希 + SAN。安全警告:托管服务生成的私钥仅用于测试;生产密钥请在本地生成。 SECURITY WARNING: Hosted key generation is for testing only. Generate production keys locally; client histories may retain returned private keys.
  • dcv.checkDCV 预检 — DNS(TXT/CNAME)或 HTTP 文件验证模式。返回完整事件流(同步等待)。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.
    Description, as the server wrote it
    DCV 预检 — DNS(TXT/CNAME)或 HTTP 文件验证模式。返回完整事件流(同步等待)。
Only reads 2Show 2 read-only tools
  • dcv.list_cas列出已支持的 CA(用于挑战路径推导与 CAA 比对)。No findings

    Why it is in this group

    • The name "dcv.list_cas" says "list": a word for reading.
    Description, as the server wrote it
    列出已支持的 CA(用于挑战路径推导与 CAA 比对)。
  • inspect.runHTTPS 体检:常规 TLS 与国密 TLCP、RSA/SM2 证书、RSA 根信任、整链 OCSP/CRL(含交叉证书)、协议套件及评级。同步等待全部完成。Reads text others writeNo findings

    Why it is in this group

    • The name "inspect.run" says "inspect": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "http": it reads web pages, which anyone can write.
    Description, as the server wrote it
    HTTPS 体检:常规 TLS 与国密 TLCP、RSA/SM2 证书、RSA 根信任、整链 OCSP/CRL(含交叉证书)、协议套件及评级。同步等待全部完成。

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 private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
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 19, 2026, 17:24 UTC, unchanged since Nov 5, 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
6
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 6 tools that change things (6 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://tools.idigitrust.com/api/v1/mcp: tools/list returned 8 tools to an anonymous client, including cert.decode (write), cert.match (write), convert.run (write), csr.decode (write), csr.generate (write) and 1 more

    What this check looks for

Posture changes

  1. Nov 5, 2026
    • Protocol version: 2024-11-05 to 2025-06-18

Findings

Matches of fixed checks, with the text they matched.

2 info

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools3 changed.~3 changedView diff
  2. PostureRemote posture changed. Protocol version: 2024-11-05 -> 2025-06-18.View diff
    • Protocol version: 2024-11-05 to 2025-06-18

Install

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

claude mcp add --transport http ssl-toolkit https://tools.idigitrust.com/api/v1/mcp
claude mcp add --transport http ssl-toolkit https://tools.idigitrust.com/api/v1/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__ssl-toolkit__dcv_list_cas",
      "mcp__ssl-toolkit__inspect_run"
    ],
    "ask": [
      "mcp__ssl-toolkit__cert_decode",
      "mcp__ssl-toolkit__cert_match",
      "mcp__ssl-toolkit__convert_run",
      "mcp__ssl-toolkit__csr_decode",
      "mcp__ssl-toolkit__csr_generate",
      "mcp__ssl-toolkit__dcv_check"
    ],
    "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 ssl-toolkit. Review it before you use it.

Capability tags behind 1 rule
  • mcp__ssl-toolkit__inspect_run untrusted-input

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.Mintreetech/ssl-toolkit-mcp/verify?hash=9d01a2286b8ca293a800e0dbaa20c51c4cc854382446ed7e359f012e9ebd805c" | jq -e '.changed == false'

Pinned hash 9d01a2286b8c, from Nov 9, 2026, 22: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.Mintreetech/ssl-toolkit-mcp/changes.xml

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

Badge

Anlyon Radar badge for io.github.Mintreetech/ssl-toolkit-mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.Mintreetech/ssl-toolkit-mcp.svg)](https://radar.anlyon.com/servers/io.github.Mintreetech/ssl-toolkit-mcp)

Source: MCP Registry · repository. Synced Oct 28, 2026, 10:17 UTC.

IDigiTrust SSL Toolkit MCP server: questions and answers

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

Is the IDigiTrust SSL Toolkit MCP server safe?

No scan can promise that. What its definitions show: 8 tools, 6 of which can change, send or delete something, and 2 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 IDigiTrust SSL Toolkit MCP server delete data?

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

Can the IDigiTrust SSL Toolkit 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 IDigiTrust SSL Toolkit MCP server have?

8 tools: 6 write, 2 read. cert.decode, cert.match, convert.run, csr.decode, csr.generate, dcv.check, dcv.list_cas and inspect.run.

Does the IDigiTrust SSL Toolkit MCP server need sign-in or OAuth?

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

Does the IDigiTrust SSL Toolkit MCP server send data to outside services?

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

Has the IDigiTrust SSL Toolkit MCP server changed its tools?

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