Skip to main content
Glama
mako10k

Web Proxy MCP Server

by mako10k

ssl_get_ca_certificate

Retrieve and install the CA certificate to enable HTTPS traffic inspection through the Web Proxy MCP Server for monitoring and analysis.

Instructions

Get CA certificate and installation instructions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler implementation: reads the CA certificate file from disk, retrieves its content, and generates platform-specific installation instructions using _getInstallationInstructions helper.
    async getCACertificate() {
      const caCertPath = path.join(this.caDir, 'ca.crt');
      try {
        const certContent = await fs.readFile(caCertPath, 'utf-8');
        return {
          certPath: caCertPath,
          certContent,
          installationInstructions: this._getInstallationInstructions(caCertPath)
        };
      } catch (error) {
        throw new Error(`CA certificate not found: ${error.message}`);
      }
    }
  • MCP tool dispatch handler: invokes sslManager.getCACertificate() and formats the result as MCP content response with certificate path and instructions.
    case 'ssl_get_ca_certificate':
      const caCert = await this.sslManager.getCACertificate();
      return {
        content: [{
          type: "text",
          text: `šŸ“œ CA Certificate\n\nšŸ“ Certificate Path: ${caCert.certPath}\n\n${caCert.installationInstructions}`
        }]
      };
  • Tool schema definition: specifies the tool name, description, and empty input schema (no parameters required).
    ssl_get_ca_certificate: {
      name: "ssl_get_ca_certificate",
      description: "Get CA certificate and installation instructions",
      inputSchema: {
        type: "object",
        properties: {}
      }
    },
  • Helper method that generates detailed, platform-specific (Linux/macOS/Windows) installation instructions for trusting the CA certificate in browsers and system stores.
    _getInstallationInstructions(caCertPath) {
      const platform = os.platform();
      const caName = this.currentCA;
    
      const instructions = {
        linux: [
          `🐧 Linux Installation:`,
          ``,
          `1. Copy CA certificate to system store:`,
          `   sudo cp "${caCertPath}" /usr/local/share/ca-certificates/${caName}.crt`,
          `   sudo update-ca-certificates`,
          ``,
          `2. For browsers (Chrome/Chromium):`,
          `   chrome://settings/certificates → Authorities → Import`,
          `   Select: ${caCertPath}`,
          ``,
          `3. For Firefox:`,
          `   about:preferences#privacy → Certificates → View Certificates`,
          `   → Authorities → Import → Select: ${caCertPath}`,
          ``,
          `4. Verify installation:`,
          `   openssl verify -CAfile "${caCertPath}" <any_generated_cert>`
        ],
        darwin: [
          `šŸŽ macOS Installation:`,
          ``,
          `1. Add to system keychain:`,
          `   sudo security add-trusted-cert -d -r trustRoot -k /System/Library/Keychains/SystemRootCertificates.keychain "${caCertPath}"`,
          ``,
          `2. Alternative (user keychain):`,
          `   security add-trusted-cert -d -r trustRoot -k ~/Library/Keychains/login.keychain "${caCertPath}"`,
          ``,
          `3. For browsers:`,
          `   - Chrome: Uses system keychain automatically`,
          `   - Firefox: Manual import required (same as Linux)`,
          ``,
          `4. Verify in Keychain Access app`
        ],
        win32: [
          `🪟 Windows Installation:`,
          ``,
          `1. Import via Certificate Manager:`,
          `   certmgr.msc → Trusted Root Certification Authorities`,
          `   → Certificates → Import → Select: ${caCertPath}`,
          ``,
          `2. Command line (as Administrator):`,
          `   certutil -addstore -f "ROOT" "${caCertPath}"`,
          ``,
          `3. PowerShell (as Administrator):`,
          `   Import-Certificate -FilePath "${caCertPath}" -CertStoreLocation Cert:\\LocalMachine\\Root`,
          ``,
          `4. Verify installation:`,
          `   certutil -store root | findstr "${caName}"`
        ]
      };
    
      const platformInstructions = instructions[platform] || instructions.linux;
      
      return [
        `šŸ”’ SSL Certificate Installation Instructions`,
        ``,
        `CA Name: ${caName}`,
        `CA Certificate: ${caCertPath}`,
        `Platform: ${platform}`,
        ``,
        ...platformInstructions,
        ``,
        `āš ļø  Important Security Notes:`,
        `- This CA can decrypt ALL HTTPS traffic routed through the proxy`,
        `- Only install on development/testing systems`,
        `- Remove CA when proxy testing is complete`,
        `- Keep CA private key secure and never share it`,
        ``,
        `šŸ”„ To remove CA later:`,
        `- Linux: sudo update-ca-certificates --fresh`,
        `- macOS: security delete-certificate -c "${caName}" (in Keychain Access)`,
        `- Windows: certmgr.msc → Remove from Trusted Root CAs`
      ].join('\n');
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions retrieving a CA certificate and instructions but doesn't specify if this is a read-only operation, requires authentication, involves rate limits, or what the output format might be. This leaves critical behavioral traits unclear for a tool that likely handles sensitive SSL data.

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?

The description is a single, efficient sentence that directly states the tool's purpose without any wasted words. It is appropriately sized and front-loaded, making it easy to parse quickly.

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

Completeness2/5

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

Given the complexity of SSL/CA operations and the lack of annotations and output schema, the description is incomplete. It doesn't explain what kind of CA certificate is retrieved (e.g., active, specific), the format of installation instructions, or any prerequisites, leaving gaps for effective tool use in a security context.

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

Parameters4/5

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

The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description adds no parameter information, which is acceptable here as there are no parameters to explain. A baseline of 4 is appropriate since no compensation is needed for missing parameter details.

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

Purpose4/5

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

The description clearly states the action ('Get') and the resource ('CA certificate and installation instructions'), making the purpose understandable. However, it doesn't differentiate this tool from sibling SSL tools like 'ssl_ca_status' or 'ssl_list_cas', which might provide overlapping or related CA information.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. With siblings like 'ssl_ca_status' and 'ssl_list_cas', the description lacks context on whether this retrieves a specific CA certificate, all CAs, or installation details only, leaving usage ambiguous.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mako10k/mcp-web-proxy'

If you have feedback or need assistance with the MCP directory API, please join our Discord server