Skip to main content
Glama
Tokenectomy-Labs

Tokenectomy-Razor

by Tokenectomy-Labs
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Rust
Local

Related Servers

Alternatives to Tokenectomy-Razor

Related Servers

  • AIS Revizor

    bswvladimir-beep
    F
    license
    Not graded
    quality
    C
    maintenance
    A local-first MCP server that gives AI coding agents runtime visibility and AI-managed debug logging. It replaces blind print() debugging by turning runtime execution into causal chains, allowing agents to instantly locate bugs by finding missing .success events in Python and TypeScript code. Single binary with MCP, CLI, and HTTP interfaces.
    -

  • CodeCortX-MCP

    kensave
    F
    license
    Not graded
    quality
    D
    maintenance
    A lightning-fast, language-agnostic code analysis MCP (Model Context Protocol) server built in Rust
    9
    -

  • uacos

    caotiensinh
    A
    license
    Not graded
    quality
    C
    maintenance
    Local-first code intelligence and safety layer for AI coding agents. MCP server exposes dependency graph, impact analysis, and AST-compressed repo context, backed by typed local memory, patch-scope safety gates, and git-independent transaction rollback.
    1
    MIT

  • SuperBased Observer

    superbasedapp
    F
    license
    Not graded
    quality
    A
    maintenance
    Local MCP server that lets your AI coding agent query its own cross-tool project history - file/command freshness, past test failures, cost & token spend, cache status, and session handoff - over stdio, 100% local, no telemetry.
    48
    -
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.4/5.0

Scored across 5 tools

Disambiguation2/5

get_error_context and audit_context_health overlap heavily: both consume raw error logs, strip framework noise, and detect credentials, differing mainly in output metrics vs. source extraction. The other tools are distinct, but these two create real ambiguity about which to call for a given error log.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern: get_error_context, search_stack_overflow, apply_code_patch, analyze_code, audit_context_health. The verbs clearly describe the action and the nouns identify the target.

Tool Count5/5

Five tools is well-scoped for an error-diagnosis-and-patching workflow. Each tool serves a distinct stage (extract context, search external knowledge, analyze statically, apply patch, audit token health) without redundant or excessive surface area.

Completeness3/5

The core flow from error context to search to analysis to patching is present, but there is no tool to verify behavior after a patch or revert a syntactically valid but logically incorrect change. Additionally, audit_context_health reports token savings but does not return a cleaned/trimmed payload, leaving a notable gap for a context-optimization-focused server.

Maintenance

ActivityMaintained
ResponsivenessResponsive

Resources