Security & Testing
boringutils.com
Checks TLS certificate trust, expiry, issuer, chain, and domain registration expiry for domains.
ENDPOINT 1
https://boringutils.com/api/mcp
MCP server metadata
- Name
- boringutils
- Version
- 1.0.0
Read-only checks of a public domain: its TLS certificate (check_certificate) and its registration expiry over RDAP (check_domain_expiry). Results inform; they are not a security or compliance assessment.
Known tools 2
check_certificateConnects to a domain on port 443 and reports its TLS certificate: whether it is trusted and matches the name, the issuer, the expiry date and days left, the lifetime, the chain and the TLS version.
Inferred read-onlycheck_domain_expiryLooks up when a domain registration expires, over RDAP at the registry for its TLD.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.boringutils]
url = "https://boringutils.com/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"boringutils": {
"type": "http",
"url": "https://boringutils.com/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: boringutils
Remote MCP URL: https://boringutils.com/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"boringutils": {
"url": "https://boringutils.com/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"boringutils": {
"type": "http",
"url": "https://boringutils.com/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "boringutils",
"transport": "streamable-http",
"url": "https://boringutils.com/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.