Skip to main content
Glama
korobkov-v

porkbun-mcp

by korobkov-v
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to porkbun-mcp

No user-submitted related servers found.

    Related Servers

    • ZoneMender

      pain2hustle
      F
      license
      Not graded
      quality
      A
      maintenance
      MCP server for AI agents to safely manage Cloudflare DNS, DMARC, SPF, BIMI, and Email Routing with dry-run-first and approval-based writes.
      9
      -

    • spaceship-mcp

      heaventree
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for reading and changing DNS records via the Spaceship API, with reviewable two-step confirmation and safety restrictions. It exposes only safe DNS operations, using domain allowlisting and failing closed when not configured.
      71 npm
      MIT

    • mcp-hetzner-dns

      ni-c
      A
      license
      A
      quality
      A
      maintenance
      An MCP server for managing Hetzner DNS zones and RRSets via the Hetzner Cloud API. It enables listing, creating, updating, deleting, importing/exporting zone files, and managing protection and TTLs from MCP clients.
      22
      50 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    D1.4/5.0

    Scored across 40 tools

    Disambiguation2/5

    Many DNS tools overlap (dns_list, dns_get, dns_query; dns_edit, dns_upsert, dns_batch_apply) and high-level tools like dns_setup, subdomain_setup, and domain_cutover_web duplicate lower-level functions. Without descriptions, agents cannot reliably distinguish them.

    Naming Consistency2/5

    Most tools use a noun_verb pattern (e.g., domains_list, dns_create), but several are verb-first (update_server_ip, dns_upsert) or use awkward noun phrases (domain_health_check, dns_audit). Resource prefixes are inconsistent: domains_, dns_, domain_ (singular), ssl_, and no prefix.

    Tool Count2/5

    40 tools is excessive for the apparent scope, especially with several overlapping operations (e.g., three DNS retrieve functions, four DNS modify functions). Many could be consolidated without losing capability.

    Completeness3/5

    The set covers core domain and DNS CRUD, DNSSEC, URL forwards, glue records, and SSL retrieval. However, domain deletion, transfer, and SSL provisioning are absent, and high-level automation tools (dns_setup, subdomain_setup) may not fill these gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources