SSL Checker API

io.github.Br0ski777Published by GitHub account Br0ski777v1.1.0Updated Oct 24, 2026

SSL certificate check — validity, expiry, issuer, chain, grade. x402 micropayment.

VerifiedSSEWeb executableFinanceSecurity & Monitoring

Overview

AI-generated overview

Remote MCP endpoint that checks a domain's SSL/TLS certificate validity, expiry, issuer, chain and security grade, paid per call via x402.

What you can do
Check a domain's SSL/TLS certificate: validity, expiry date, days remaining, issuer, protocol and security grade, returned as structured JSON.
When to use it
Useful when deploying a website, monitoring certificate expiration, auditing security posture or validating an HTTPS setup, and when a per-call micropayment is acceptable.
Requirements
A remote SSE endpoint; no API key or signup. Payment is required per call via x402 in USDC on Base L2, so an x402-aware client with a funded wallet is needed to complete the 402 challenge.
Before you install
Each check costs $0.005 in USDC on Base, so an assistant can spend real money; a wallet or signing client must be configured. The domain you submit is sent to a third-party service, and payments route through Coinbase CDP or PayAI facilitators.

Installation

In SourceWeft

  1. Open SSL Checker API in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Br0ski777%2Fssl-checker/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "ssl-checker-api": {
      "type": "sse",
      "url": "https://ssl-checker.api.klymax402.com/mcp"
    }
  }
}

README

SSL Checker API

[MCP Server] [x402] [License: MIT]

Check SSL/TLS certificate validity, expiry, issuer, chain details, and security grade for any domain. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.

Part of the klymax402 marketplace -- 100 x402 micropayment APIs for AI agents, one wallet, USDC on Base.

Quickstart -- MCP

Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):

json
{  "mcpServers": {    "ssl-checker": {      "url": "https://ssl-checker.api.klymax402.com/mcp"    }  }}

Quickstart -- HTTP (x402)

bash
curl -X POST "https://ssl-checker.api.klymax402.com/api/check" \  -H "Content-Type: application/json" \  -d '{"domain":"..."}'# -> 402 Payment Required, with an x402 payment challenge in the response body

Any x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.

Tools

ToolMethodPathPriceDescription
security_check_sslPOST/api/check$0.005Check SSL certificate for a domain

security_check_ssl

Use this when you need to check if a domain's SSL/TLS certificate is valid, when it expires, and who issued it. Returns structured certificate data in JSON.

Parameters

NameTypeRequiredDescription
domainstringyesDomain name to check SSL certificate (e.g. example.com)

Example response:

json
{"domain":"example.com","valid":true,"expiryDate":"2026-12-15","daysRemaining":245,"issuer":{"name":"DigiCert","organization":"DigiCert Inc"},"protocol":"TLSv1.3","securityGrade":"A+"}

When to use: deploying a website, FOR monitoring certificate expiration, auditing security posture, and validating HTTPS setup.

Not for: DNS lookup (use network_lookup_dns), HTTP headers analysis (use network_analyze_headers), port scanning (use network_scan_ports).

Example agent prompts

  • "Check if a domain's SSL/TLS certificate is valid, when it expires, and who issued it"

Payment

  • Protocol: x402 -- HTTP-native pay-per-call, no signup, no API key
  • Network: Base L2 (eip155:8453)
  • Asset: USDC
  • Facilitator: Coinbase CDP (primary), PayAI (fallback)
  • Also reachable via ATXP (OAuth-wrapped x402, RFC 9728 protected-resource metadata)

Part of klymax402

100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.

License

MIT

Source: README.md at commit b8978ed

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts