Remote MCP server to run your Atako AI agents: chat, projects, files, integrations and channels.
- Passed: Handshake
- Passed: Tools listed
- Passed: Updated recently
Median latency 132 ms · Last checked
Explore
Evidence for your next connection.
Independent measurements of remote MCP servers. Every observation has a timestamp.
Read-only probesMCP server · Code & DevOps
Check a site's TLS certificate and its domain registration expiry. Read-only, no sign-in.
2 failed · 8 not measured
Median of successful probes over 7 days
Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.
Tool definitions returned by this server
Independent monitoring
Responded
The server completed its last measured handshake. This is an observation, not a guarantee.
Last checked| Test area | Passed | Failed | Unmeasured |
|---|---|---|---|
ConnectionCan a client connect and discover tools? | 5 | 0 | 0 |
Reliability & speedDoes it respond consistently and quickly? | 0 | 0 | 4 |
Access & authenticationWhat is required to use this server? | 1 | 0 | 2 |
Tool qualityAre the tool definitions usable by an agent? | 4 | 0 | 0 |
Publisher identityCan the publisher be traced to its source? | 2 | 2 | 2 |
Unmeasured means there is not enough evidence to decide. How these checks work
Start using Boring Utils Expiry Watch
Choose your client, copy the configuration, then enable the server in your client’s MCP settings.
Run this command in your terminal, then restart Claude Code.
Claude Code
claude mcp add --transport http boring-utils-expiry-watch https://boringutils.com/api/mcpCapabilities
Connects 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, what each of its server addresses serves (up to 4 IPv4 and 4 IPv6), and, for certificates from Let’s Encrypt, Google Trust Services, ZeroSSL or Sectigo, the renewal window the CA suggests (ACME Renewal Information).
DiscoveredLooks up a domain registration over RDAP at the registry for its TLD: when it expires, the registrar, the statuses (flagging a hold, redemption, pending delete or pending transfer) and the nameservers. Subdomains are looked up by their registered domain (www.example.co.uk becomes example.co.uk).
DiscoveredRecent measurements
| Checked | Result | Response | Tools |
|---|---|---|---|
| Connected | 89 ms | 2 |