Porkbun DNS ๐ท
๐ท MCP server for Porkbun DNS API - manage domains, DNS records, DNSSEC, and SSL certificates
Is Porkbun DNS ๐ท safe? Promising trust profile, but some evidence still deserves review.
Compare Porkbun DNS ๐ท
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: Porkbun DNS ๐ท scores 61.9/100 (Grade C), ranked #575 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 4.9/10; 53% of recent commits are signed; last pushed 2026-06-01. Every point is earned from checkable signals โ never paid placement. How scoring works โ
How Porkbun DNS ๐ท compares in MCP Servers
- #324 Rootly MCP Server 61.9 ±0
- #325 Apollo MCP Server 61.9 ±0
- #326 Porkbun DNS ๐ท 61.9 this agent
- #327 Agent360 Browser MCP 61.9 ±0
- #328 Bagel 61.8 −0.1
Bars show each HVTrust score; the tick marks Porkbun DNS ๐ท’s 61.9.
Where the 61.9 comes from
HVTrust dimensions vs the MCP Servers average
61.9 / 100 ยท 100.0% confidencePorkbun DNS ๐ท MCP Servers average (775 agents)
Quick Trust Read
How to read this: HVTrust (0โ100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A โฅ 80, B โฅ 65, C โฅ 50, D < 50. Evidence coverage B is separate โ it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology โ
Rank Trend
Activity & Reach
Analysis
Activity Inputs
18.6 / 100Supply Chain Trust
Common questions about Porkbun DNS ๐ท
Does Porkbun DNS ๐ท publish package provenance?
Does Porkbun DNS ๐ท have an OpenSSF Scorecard?
Is Porkbun DNS ๐ท actively maintained?
What license does Porkbun DNS ๐ท use?
Are Porkbun DNS ๐ท's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
MCP, providers, tool surface
These runtime-trust fields โ detected from public repo docs and manifests โ contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology โ Compare this surface across every listed agent in the capability matrix โ
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Porkbun DNS ๐ท's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different โ a genuinely changed capability, or better evidence of an existing one.
Maintain Porkbun DNS ๐ท?
For maintainers
HVTrust scores Porkbun DNS ๐ท from public signals only โ we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers โ
For maintainers
[](https://hvtracker.net/agents/porkbun-dns)
<a href="https://hvtracker.net/agents/porkbun-dns"><img src="https://hvtracker.net/badge/porkbun-dns.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) ยท PyPI / pypistats (downloads, provenance) ยท OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 ยท Raw JSON