porkbun-mcp

Overview Schema Source Related Servers Discussions Admin

ssl_retrieve

Read-only

Retrieve the SSL certificate bundle for any domain using Porkbun nameservers. Get the full certificate chain needed to configure HTTPS.

Instructions

Retrieve the SSL certificate bundle for a domain.

Only available for domains using Porkbun nameservers.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "<domain>"
    },
    "name": "ssl_retrieve"
  }
}

Input Schema

Name	Required	Description	Default
`domain`	Yes	Domain name (e.g., 'example.com')

Output Schema

Name	Required	Description
`public_key`	Yes	Public key (PEM)
`private_key`	Yes	Private key (PEM)
`certificate_chain`	Yes	Certificate chain (PEM)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.2Aug 7, 2026

TDQS

A4.1/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, so the agent knows this is a safe read operation. The description adds the important constraint about Porkbun nameservers, which is a behavioral boundary. It does not describe response format or error behavior, but the read-only nature is covered by annotations and output schema exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences: the first states the purpose, the second states a critical usage constraint. No wasted words; information is front-loaded and directly relevant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With a single parameter, a read-only annotation, and an output schema present, the description covers the essential context. The purpose and unique availability condition are stated. No additional details are needed for a tool of this simplicity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 100% coverage with the description 'Domain name (e.g., 'example.com')' for the 'domain' parameter. The tool description does not add additional parameter semantics beyond this, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Retrieve' and the resource 'SSL certificate bundle for a domain.' This is specific and distinguishes from sibling tools which focus on DNS/domain management, not SSL certificate retrieval.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides an explicit availability constraint: 'Only available for domains using Porkbun nameservers.' This implies when not to use the tool, though it does not mention alternative tools for non-Porkbun nameservers. Still, this is clear context for usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.