MCP servers › io.github.Servosity › domain-cert-tracker-mcp
MCP server · registry snapshot 2026-11-12 · last checked 2026-11-12
domain-cert-tracker-mcp MCP server
Registry name io.github.Servosity/domain-cert-tracker-mcp
Domain and Certificate Tracker MCP — the publisher's title
by Servosity · GitHub account (the registry's namespace rule)repository: same ownerSource ↗
Every client's domains and certificates in one inventory: what expires, unlocks or changes. — the publisher's description
Summary
io.github.Servosity/domain-cert-tracker-mcp is a local MCP server listed in the official MCP registry at version 0.1.4, under the namespace of the GitHub account Servosity. Its linked repository, github.com/servosity/msp-skills, belongs to the same GitHub account.
Record checks
5 of 5 record checks met · 4 do not apply
- met: Registry entry is active and says how to run it
- met: Source repository link opens
- met: Repository is not archived
- met: Code pushed to the repository in the 90 days before our check
- met: Repository publishes a security policy (SECURITY.md)
- not applicable: Package names its licence with a standard (SPDX) identifier
- not applicable: The version the registry lists can be installed and is not withdrawn
- not applicable: npm package carries build provenance (attestation)
- not applicable: No known critical or high advisory in the package or its dependencies
- Not ranked by downloads: not an npm or PyPI package
- #1,087 of 28,859 repositories by GitHub stars, tied with 3 others (repository shared with 107 other registry entries)
From public records, not a safety rating. Each check with its reason · Is it safe to install?
Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it
Key facts
- Runs
- local package
- Transport
- standard input/output
- Your own values
- none declared (not a guarantee)
- Package
- MCP bundle
- Repository
- public
- Last tested
- not tested
Tool list
Not read: It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's. So there is no tool-list size and no result from the three APIs.
How fresh this is
- Live-tested
- no
- Last tested
- not tested
- Latest version
- 0.1.4, published 2026-11-12 (registry, as of the 2026-11-12 snapshot)
- First listed version
- 2026-11-06 (earliest version still in the registry; older removed versions would be earlier)
- Version history
- 5 versions listed, 2026-11-06 to 2026-11-12; 5 in the 90 days before the 2026-11-12 snapshot.(versions still listed in the registry only)
Most recent 5 versions
0.1.4· 2026-11-120.1.3· 2026-11-110.1.2· 2026-11-100.1.1· 2026-11-090.1.0· 2026-11-06
- Registry data
- snapshot 2026-11-12
- Package and repository
- checked 2026-11-12
Dead or stale signals
None found in the records we hold
Looked for and not found: deprecated in the registry; repository link does not open; repository archived; no push in over 365 days. Does not apply: listed version cannot be installed or is withdrawn. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.
Changes since the last refresh
Version 0.1.0 (published 2026-11-06) → 0.1.4 (published 2026-11-12), between the registry lists of 2026-11-09 and 2026-11-12.
The publisher’s GitHub release note for domain-cert-tracker-v0.1.4, published 2026-11-12.
Read the release note (the publisher’s text, shown as plain text)
### Fixed - **`store_status` no longer stays `partial` for good when your token cannot read a resource.** A resource the vendor refuses this token (HTTP 403) is now recorded as skipped. `search` and `sql` report `complete_with_skips` when everything else finished and name what was skipped under `skipped_forbidden`. A resource that failed still leaves the store `partial` and is named under `incomplete_resources`, and the `sync` summary names both. The `sync` exit code is unchanged ([#692](https://github.com/Servosity/msp-skills/issues/692)). - **`sync` progress reports the rate it measured.** `rate_rps` in the `sync_progress` event used to be the request pacer's ceiling. It now carries the measured rows per second over the last 30 seconds, the same value as the new `rows_per_sec`. The ceiling, when one is active, is the new `limiter_ceiling_rps`, and the progress line reads like `[33.0 rows/s, limit 4.9 req/s]` ([#694](https://github.com/Servosity/msp-skills/issues/694)). - **`sync` spends far less CPU on progress output.** Every line the CLI prints goes through the credential check, and that check costs about the same whether the line is long or short. `sync` printed one progress line per page. It now prints the first page's line and then at most one every 5 seconds per resource; each line still carries the measured rate, and the final count still arrives in `sync_complete` and the done line ([#696](https://github.com/Servosity/msp-skills/issues/696)).
Source: the official MCP Registry list on 2026-11-09 and on 2026-11-12; release notes from the GitHub Releases API, checked 2026-11-12.
What it is
How do I add it to my client?
Config from the registry entry
- No config: the MCP bundle is a file to install in a client that supports bundles, not a command.
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
What do the published files and outside lists say?
Read as text · nothing run · no tool called
Package files
- Bundle platforms (MCPB). The bundle lists platforms darwin, linux and win32 (manifest.json compatibility). Source: read 2026-11-12.
- MCP SDK in the package files. Not read yet: added with the next daily run.
- Build workflow. Not read yet: added with the next daily run.
Outside lists
- CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-12. This product uses the NVD API but is not endorsed or certified by the NVD.
- GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-12. GitHub Advisory Database, CC BY 4.0
- Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-12. Source: read 2026-11-12.
- Cline marketplace. Not in the Cline marketplace on 2026-11-12. Source: read 2026-11-12.
Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read
Does the registry listing match what we found?
Feature #6The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Repository github.com/servosity/msp-skills | Opens publicly | matches | api.github.com · 2026-11-12 |
Who made it?
Feature #7 · lineage
Facts about the publisher. We do not turn them into a trust score.
- Namespace
- io.github.Servosity · 108 servers
- GitHub owner
- an organization (Servosity)
- Repository
- github.com/servosity/msp-skills
- Stars
- 74
- Repository age
- 91–180 days
- Last push
- 0–30 days ago
- Archived
- no
- Security policy
- SECURITY.md
Source: the registry entry and api.github.com · 2026-11-12; security policy read from GitHub · 2026-11-07.
Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.
Choosing
Record checks
Public records · not a safety rating5 of 5 record checks met · 4 do not apply
- Not ranked by downloads: not an npm or PyPI package
- #1,087 of 28,859 repositories by GitHub stars, tied with 3 others (repository shared with 107 other registry entries)
- MetRegistry entry is active and says how to run itActive, with a package or a remote address.
- MetSource repository link opensThe linked GitHub repository is public.
- MetRepository is not archivedNot archived.
- MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
- MetRepository publishes a security policy (SECURITY.md)SECURITY.md found.
- Does not applyPackage names its licence with a standard (SPDX) identifierNot an npm or PyPI package.
- Does not applyThe version the registry lists can be installed and is not withdrawnNot an npm or PyPI package.
- Does not applynpm package carries build provenance (attestation)PyPI packages have no npm-style attestation.
- Does not applyNo known critical or high advisory in the package or its dependenciesNot an npm or PyPI package.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-12 (security policy 2026-11-07). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral
Common questions about io.github.Servosity/domain-cert-tracker-mcp
Answered from the data aboveWho publishes io.github.Servosity/domain-cert-tracker-mcp?
The registry ties the namespace io.github.Servosity to the GitHub account Servosity; only its owner can publish under it. Its linked repository, github.com/servosity/msp-skills, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.
Is io.github.Servosity/domain-cert-tracker-mcp safe to install?
We do not rate servers as safe or unsafe. 5 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.
Has io.github.Servosity/domain-cert-tracker-mcp been security tested?
No. It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's.
Does io.github.Servosity/domain-cert-tracker-mcp publish a security policy?
Yes: its repository has a public security policy (github.com/servosity/msp-skills/blob/HEAD/SECURITY.md). That is the publisher's statement, not permission for us to test the server, and we call none of its tools.
Where is the source code of io.github.Servosity/domain-cert-tracker-mcp?
In github.com/servosity/msp-skills, which opens publicly.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
Has it been tested?
Feature #1It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's. — our limit
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “io.github.Servosity/domain-cert-tracker-mcp: MCP server record.” Data checked 2026-11-12. https://protocolprobe.com/mcp/servers/io.github.Servosity/domain-cert-tracker-mcp
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/io.github.Servosity/domain-cert-tracker-mcp)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).
Write to hello@protocolprobe.com · corrections log · methodology