Skip to main content
Glama
SpaceTimee

Console CensorChecker

by SpaceTimee
OverviewSchemaRelated ServersScoreDiscussions
Local

自我介绍

Console CensorChecker: 一只基于 Pwsh(.Net 8) 的 Tcping 批量拨测与审查检测脚本

  • 适用平台: Any

Related MCP server: Keel

注意事项

本项目仅供测试 Tcping 延迟与监控服务可用性，无意绕过任何审查设备的审查

下载地址

  1. Github Release: https://github.com/SpaceTimee/Console-CensorChecker/releases

  2. PowerShell Gallery: https://www.powershellgallery.com/packages/Console-CensorChecker

  3. Github Marketplace: https://github.com/marketplace/actions/console-censorchecker

安装方式

PowerShell Module: Install-Module Console-CensorChecker

食用方式

  1. PowerShell Script: 在 pwsh 7.x 环境中运行 Console-CensorChecker.ps1 脚本 → 按照提示操作即可

  2. PowerShell Module: 在 pwsh 7.x 环境中执行 Invoke-Check 命令即可

Invoke-Check -targets example.com

  1. MCP Server: 在 pwsh 7.x 环境中执行 Invoke-Check -mcp 命令即可

Invoke-Check -mcp

  1. MCP Client: 在 Agent 客户端中添加 MCP 配置即可

{
    "mcpServers": {
        "console-censorchecker": {
            "command": "pwsh",
            "args": ["-Command", "Invoke-Check -mcp"]
        }
    }
}

  1. Github Actions: 在工作流中调用 SpaceTimee/Console-CensorChecker 即可

- uses: SpaceTimee/Console-CensorChecker@v1.1.4.55
  with:
      TARGETS: example.com

MCP 托管

  1. Smithery (首选): https://smithery.ai/servers/spacetime/console-censorchecker

  2. Glama: https://glama.ai/mcp/servers/SpaceTimee/Console-CensorChecker

开发者

Space Time

联系方式

  1. QQ 群 (主群): 964102080，1034315671，716266896，338919498

  2. TG 群 (分群): PixCealerChat

  3. 邮箱: Zeus6_6@163.com

•ᴗ•

Available Tools

1 tool
Invoke-CheckB

Synopsis: Check host targets for tcping latency and censorship. Returns a JSON result with Target and Latency (timeout: 2147483647) Component: Network Role: Probe Functionality: Batch tcping probe & Censor checker

ParametersJSON Schema
NameRequiredDescriptionDefault
portNoDefault port for targets
browserNoChromium browser path
targetsNoHost targets or a target file path to check

TDQS

B3.3/5.0
Behavior2/5

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

No annotations provided, so description must carry full burden. It mentions return format (JSON with Target and Latency) and timeout value, but does not disclose whether the tool has destructive side effects, requires permissions, or has rate limits.

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

Conciseness3/5

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

The description includes structured fields (Synopsis, Component, etc.) but contains redundancy (e.g., 'Component: Network' is implicit). Could be more concise.

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?

No output schema, so description must explain return values. It does mention JSON result with Target and Latency, but lacks details on censorship check interpretation or error handling. Adequate but not fully comprehensive.

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 coverage is 100% with descriptions. The description adds context (tcping latency) but does not significantly improve understanding beyond what the schema already provides.

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 the tool checks host targets for tcping latency and censorship, with specific verb and resource. It distinguishes itself from no siblings, so clarity is high.

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?

No explicit guidance on when to use or not use this tool, but with no siblings, the context implies usage for network probing. Lacks 'when-not-to-use' criteria.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool update
    • First observedInvoke-Check
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.4/5.0
Disambiguation5/5

Only one tool exists, so there is no possibility of ambiguity.

Naming Consistency5/5

The single tool follows a consistent PowerShell verb-noun convention (Invoke-Check).

Tool Count3/5

With only one tool, the server feels underdeveloped; a network checker typically requires multiple tools for different operations.

Completeness2/5

The server only provides a single tool for tcping and censorship checking, missing other essential network diagnostics like traceroute or DNS checks.

Maintenance

ActivitySlowing
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • Keel

    seayniclabs
    A
    license
    A
    quality
    C
    maintenance
    Network diagnostics — ping, traceroute, DNS lookup, port scanning, and connectivity testing via MCP.
    14
    MIT

  • SurveyHub-MCP

    helGayhub233
    A
    license
    B
    quality
    B
    maintenance
    Aggregates multiple cyberspace search engines (FOFA, Quake, Hunter, ZoomEye) into a unified MCP server, enabling asset search, pagination, statistics, and account info retrieval.
    26
    MIT

  • xray-mcp-monitor

    i-zrhe2016
    F
    license
    B
    quality
    C
    maintenance
    MCP server for checking reachability of nodes inside an Xray subscription by fetching subscription URLs, parsing nodes, running TCP probes, and exposing tools for scheduled monitoring.
    7
    -

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/SpaceTimee/Console-CensorChecker'

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