Skip to main content
Glama
VisualSentinel

Visual Sentinel MCP Server

Official
by VisualSentinel
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

vs_ssl_check

Check the TLS/SSL certificate details of any hostname, including issuer, validity, SAN list, and certificate chain. Ideal for verifying certificate configuration.

Instructions

Inspect a TLS/SSL certificate for a hostname: issuer, subject, validity dates, SAN list, key algorithm, and certificate chain. No authentication required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostYesHostname to inspect, e.g. example.com (without protocol).
portNoTCP port. Default 443.

Implementation Reference

  • src/tools.ts:106-111 (handler)
    The handler function for vs_ssl_check. It calls the Visual Sentinel API endpoint /api/tools/ssl-check with the 'host' (required) and 'port' (optional) query parameters. No authentication is required.
      handler: async (args, client) =>
    client.request('GET', '/api/tools/ssl-check', {
      auth: false,
      query: { host: requireString(args, 'host'), port: pickNumber(args, 'port') },
    }),
},

Tool Definition Quality

A4.1/5.0
Behavior4/5

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

With no annotations provided, the description carries the burden. It discloses that no authentication is required, indicating a public read operation. However, it does not mention rate limits, data caching, or any potential side effects, which could strengthen transparency.

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 sentence that efficiently conveys the tool's purpose and key details (list of inspected attributes and auth requirement). No redundant information.

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?

Since there is no output schema, the description compensates by listing the exact attributes inspected (issuer, subject, validity dates, SAN list, key algorithm, certificate chain). This sufficiently informs the agent about the output structure and scope.

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?

Input schema coverage is 100% with clear descriptions for 'host' and 'port'. The description does not add new semantic details beyond the schema; it merely repeats the concept of hostname inspection. Baseline 3 applies.

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 'Inspect a TLS/SSL certificate for a hostname' and enumerates specific items (issuer, subject, validity dates, SAN list, key algorithm, certificate chain). It is specific and distinct from sibling tools which cover alerts, DNS, health, incidents, monitors, etc.

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

Usage Guidelines3/5

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

The description mentions 'No authentication required,' implying it can be used without credentials, but does not provide explicit guidance on when to use versus alternatives or any when-not-to conditions. Since it is the only SSL-related tool, context is clear but exclusionary advice is absent.

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/VisualSentinel/mcp-server'

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