Skip to main content
Glama
Sign In
SRC Hunter MCP Server

SRC Hunter MCP Server

by mUggles1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

check-authorization

Verify whether a domain, URL, or IP is within authorized scope before running security tests. Prevent out-of-scope scanning by checking target authorization upfront.

Instructions

检查目标是否在授权测试范围内

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": {
      "target": "<target>"
    },
    "name": "check-authorization"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYes目标（域名/URL/IP）

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

There are no annotations, so the description carries full responsibility for behavioral disclosure. It does not explain what happens when the target is authorized or unauthorized, whether the operation is read-only, or what response the agent should expect.

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 redundant words. It conveys the core purpose immediately.

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?

With no output schema and no behavioral details, an agent cannot know how to interpret the tool's result or how to act on it. For a preflight authorization check, this is 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 target parameter already includes '域名/URL/IP'. The tool description adds no further semantic detail, so the baseline score of 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 '检查目标是否在授权测试范围内' states a specific verb (check) and a specific resource/condition (whether a target is within authorized testing scope). It clearly differentiates this from the sibling scanning, export, and configuration tools.

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 intended use is implied: check a target before engaging in security testing. However, it does not explicitly state when to use this tool versus alternatives, nor does it mention that it should be called before other scanning tools.

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