Skip to main content
Glama
Sign In
SRC Hunter MCP Server

SRC Hunter MCP Server

by mUggles1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

enumerate-subdomains-lite

Enumerate subdomains for a given domain using the crt.sh API. Discover associated subdomains without needing external tools.

Instructions

子域名枚举（使用 crt.sh API，无需外部工具）

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": "enumerate-subdomains-lite"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes主域名（如 example.com）

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral disclosure burden. It does reveal that the tool relies on the crt.sh API and needs no external tools, which implies a passive, network-dependent operation. However, it does not mention output format, rate limits, or failure modes, leaving important behavior undisclosed.

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 compact sentence with no filler. The core action is front-loaded, and the parenthetical adds genuinely new information about the method and external dependency.

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

Completeness3/5

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

For a one-parameter, read-only enumeration tool, the description is minimally viable: an agent knows what to call and with what input. But with no output schema and no stated return format, an agent cannot know what the tool will hand back, leaving a meaningful gap.

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?

Schema description coverage is 100% and the 'domain' parameter is already explained with an example. The tool description adds no additional parameter semantics, so it sits at the baseline.

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 states a specific action and resource: '子域名枚举' (subdomain enumeration), and adds the concrete method '使用 crt.sh API' (uses crt.sh API). It stops short of distinguishing itself from the sibling tool 'enumerate-subdomains', so it loses the fifth point.

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?

There is no guidance on when to prefer this lite tool over 'enumerate-subdomains' or when to choose it instead of other enumeration/scan siblings. The parenthetical '无需外部工具' hints at one use case (no external tool installation) but never states it as a selection condition.

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

Deploy Server

Other Tools