porkbun-mcp-server
Provides an MCP (Model Context Protocol) server over stdio that exposes Porkbun API (v3) capabilities as MCP tools for managing domains, DNS records, DNSSEC records, SSL/key retrieval, nameservers, and URL forwarding, plus domain availability checks.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
The server requires Porkbun API key/secret provided via environment variables or .env (reducing risk vs hardcoding, but secrets must be protected on the host). No evidence is provided for fine-grained authorization, audit logging, request signing separation, or explicit rate-limit handling. SSL bundle retrieval exposes private key material, so tool access should be tightly controlled.
⚡ Reliability
Best When
You have an MCP-compatible client (e.g., Claude Desktop) and want AI-assisted domain/DNS operations against a Porkbun account using a local stdio MCP server.
Avoid When
You cannot securely handle API secrets on the machine running the MCP server, or you need strong guardrails to prevent destructive DNS/SSL changes.
Use Cases
- • Automating DNS record management (CRUD for A/CNAME/MX/TXT/etc.) via an AI assistant
- • Updating nameservers and URL forwarding rules through MCP clients
- • Querying DNS records and DNSSEC records for a domain
- • Testing Porkbun API connectivity/auth with a ping tool
- • Assisting with domain verification workflows (domain availability/pricing checks)
Not For
- • Unattended/production automation without careful access control and audit logging
- • Use cases requiring fine-grained authorization per domain/operation
- • Clients that require a REST/GraphQL/HTTP interface instead of MCP stdio transport
Interface
Authentication
Uses Porkbun API credentials (API key/secret). No OAuth flow; likely a single set of credentials for all operations.
Pricing
No pricing information for the MCP server itself; costs would primarily be whatever Porkbun charges for the underlying API/account operations (not specified here).
Agent Metadata
Known Gotchas
- ⚠ Destructive tools (delete/edit DNS records, delete DNSSEC, delete URL forwards) can cause irreversible configuration changes if called with wrong parameters.
- ⚠ Pagination only described for list_domains via a start index; no cursor-based guidance or explicit page size is documented.
- ⚠ TTL minimums and required parameters (e.g., prio for MX/SRV) are mentioned, but the safety of parameter validation/error handling is not evidenced in the README.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for porkbun-mcp-server.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.