Skip to main content
Glama

HuangtingFlux — Huangting Protocol MCP Server

Server Details

Reduces AI Agent token usage by 40% via three-stage SOP workflow.

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Last Tested
Transport
Streamable HTTP
URL
Repository
XianDAO-Labs/huangting-flux-hub
GitHub Stars
0
Server Listing
HuangtingFlux Hub

TDQS

A4.6/5.0

Scored across 4 tools

Disambiguation5/5

Each tool serves a distinct phase of the protocol: start_task initiates, report_step_result logs progress, finalize_and_report concludes, and get_network_stats provides external context. There is no overlap or ambiguity between their purposes.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case: start_task, report_step_result, finalize_and_report, get_network_stats. The naming style is uniform and predictable.

Tool Count5/5

With exactly four tools, the server is tightly scoped to its protocol lifecycle. Each tool is necessary and the count is neither excessive nor sparse for the intended workflow.

Completeness5/5

The tool set covers the complete lifecycle of the Huangting Protocol: start, per-step reporting, and finalization. The addition of get_network_stats provides useful monitoring without leaving any obvious operational gap.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Changedstart_task1 field changed
      • addedInput schema / properties / task_type
        Added value: +{
        +  "default": "default",
        +  "description": "Task category for accurate baseline token modeling. Determines context_multiplier, expected steps, and output length. Choose the closest match: complex_research (deep research, 15 steps, ×4 context), code_generation (8 steps, ×2.5), multi_agent_coordination (20 steps, ×5), relationship_analysis (6 steps, ×2), optimization (5 steps, ×1.8), writing (4 steps, ×1.5), data_analysis (8 steps, ×2.5), default (8 steps, ×2.5).",
        +  "enum": [
        +    "complex_research",
        +    "code_generation",
        +    "multi_agent_coordination",
        +    "relationship_analysis",
        +    "optimization",
        +    "writing",
        +    "data_analysis",
        +    "default"
        +  ],
        +  "type": "string"
        +}
  2. 5 tool updates
    • Removedcreate_optimization_context
    • Addedfinalize_and_report
    • Removedreport_optimization_result
    • Addedreport_step_result
    • Addedstart_task
  3. 1 tool update
    • Changedreport_optimization_result1 field changed
      • addedInput schema / properties / task_type
        Added value: +{
        +  "description": "Optional: categorize the task type for analytics (e.g. 'complex_research', 'code_generation', 'multi_agent_coordination'). Defaults to 'optimization'.",
        +  "type": "string"
        +}
  4. 4 tool updates
    • Addedcreate_optimization_context
    • Removedget_optimization_strategy
    • Removedget_protocol_concept
    • Changedreport_optimization_result7 fields changed
      • addedInput schema / properties / actual_tokens_used
        Added value: +{
        +  "description": "Actual total tokens consumed during the optimized task run",
        +  "minimum": 1,
        +  "type": "integer"
        +}
      • addedInput schema / properties / baseline_tokens
        Added value: +{
        +  "description": "Baseline token estimate from create_optimization_context response",
        +  "minimum": 1,
        +  "type": "integer"
        +}
      • addedInput schema / properties / context_id
        Added value: +{
        +  "description": "The context_id returned by create_optimization_context",
        +  "type": "string"
        +}
      • removedInput schema / properties / task_type
        Removed value: -{
        -  "description": "Type of task that was optimized",
        -  "enum": [
        -    "complex_research",
        -    "code_generation",
        -    "multi_agent_coordination"
        -  ],
        -  "type": "string"
        -}
      • removedInput schema / properties / tokens_baseline
        Removed value: -{
        -  "description": "Baseline token count without optimization. Measure BEFORE applying Huangting optimization.",
        -  "minimum": 1,
        -  "type": "integer"
        -}
      • removedInput schema / properties / tokens_saved
        Removed value: -{
        -  "description": "Number of tokens saved compared to unoptimized baseline. Must be <= tokens_baseline.",
        -  "minimum": 0,
        -  "type": "integer"
        -}
      • changedInput schema / required
        Previous value: -[
        -  "agent_id",
        -  "task_type",
        -  "tokens_saved",
        -  "tokens_baseline"
        -]New value: +[
        +  "agent_id",
        +  "actual_tokens_used",
        +  "baseline_tokens"
        +]
  5. 1 tool update
    • Changedreport_optimization_result5 fields changed
      • removedInput schema / properties / tokens_baseline / default
        Removed value: -0
      • changedInput schema / properties / tokens_baseline / description
        Previous value: -"Baseline token count without optimization (for ratio calculation)"New value: +"Baseline token count without optimization. Measure BEFORE applying Huangting optimization."
      • changedInput schema / properties / tokens_baseline / minimum
        Previous value: -0New value: +1
      • changedInput schema / properties / tokens_saved / description
        Previous value: -"Number of tokens saved compared to unoptimized baseline"New value: +"Number of tokens saved compared to unoptimized baseline. Must be <= tokens_baseline."
      • changedInput schema / required
        Previous value: -[
        -  "agent_id",
        -  "task_type",
        -  "tokens_saved"
        -]New value: +[
        +  "agent_id",
        +  "task_type",
        +  "tokens_saved",
        +  "tokens_baseline"
        +]
  6. 4 tool updates
    • First observedget_network_stats
    • First observedget_optimization_strategy
    • First observedget_protocol_concept
    • First observedreport_optimization_result

Related MCP Connectors

Related MCP Servers

  • F
    license
    Not graded
    quality
    D
    maintenance
    Enables efficient AI agent operations through sandboxed Python code execution with progressive tool discovery, PII tokenization, and skills persistence, achieving up to 98.7% token reduction by processing data in a sandbox rather than in context.
    -
  • A
    license
    A
    quality
    F
    maintenance
    Enables efficient AI workflow orchestration by chaining multi-step LLM operations while keeping intermediate results out of the context window, reducing token usage by 90%+ and supporting multiple AI providers.
    7
    13 npm
    1
    MIT
Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.