Skip to main content
Glama
CloudWaddie

OSINT MCP Server

ssl_certs

Retrieve SSL certificate information for any domain from crt.sh to analyze security configurations and identify associated subdomains.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesDomain name to lookup SSL certificates on crt.sh

Implementation Reference

  • Tool registration and handler for the 'ssl_certs' tool.
    server.tool(
      "ssl_certs",
      { domain: z.string().describe("Domain name to lookup SSL certificates on crt.sh") },
      async ({ domain }) => {
        const result = await sslClient.getCertificates(domain);
        return {
          content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
        };
      }
  • Actual implementation of the SSL certificate lookup logic using crt.sh API.
    async getCertificates(query: string): Promise<SslCertificate[]> {
      try {
        const data = await this.fetch<any[]>("", {
          method: "GET",
        }, {
          q: query,
          output: "json",
        });
    
        if (!Array.isArray(data)) return [];
    
        return z.array(SslCertificateSchema).parse(data);
      } catch (error) {
        if (error instanceof McpError) throw error;
        throw new McpError(
          ErrorCode.InternalError,
          `crt.sh SSL lookup error: ${(error as Error).message}`
        );
      }
    }
  • Zod schema definition for SSL certificate data.
    export const SslCertificateSchema = z.object({
      issuer_ca_id: z.number(),
      issuer_name: z.string(),
      common_name: z.string(),
      name_value: z.string(),
      id: z.number(),
      entry_timestamp: z.string().optional(),
      not_before: z.string().optional(),
      not_after: z.string().optional(),
      serial_number: z.string().optional(),
    });
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/CloudWaddie/osint-mcp'

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