Skip to main content
Glama
moxno

ztds-mcp

by moxno
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to ztds-mcp

No user-submitted related servers found.

    Related Servers

    • ztds-mcp

      moxno
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables local, in-memory sanitization of sensitive text before LLM ingestion by replacing PII, PHI, and credentials with deterministic reversible tokens, then restoring the originals in responses. It also audits content for exposed secrets and PII and provides compliance receipts without external network egress or disk writes.
      0
      Apache 2.0

    • SecureMCP

      mj10612
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables local grammar-preserving masking of sensitive content, entities, and code identifiers into synthetic tokens before sending prompts to LLMs, then restores the original text and symbols from responses using session-scoped in-memory mappings.
      1
      Apache 2.0
    • genpark-agentic-zero-knowledge-pii-token-vault-masker-skill by alphaparkinc

      genpark-agentic-zero-knowledgeofficial

      alphaparkinc
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables reversible anonymization of sensitive PII such as SSNs, credit cards, passport numbers, emails, and phone numbers before sending prompts to external LLMs, then restores original values locally using HMAC isolation.
      7
      -
    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

    B3.4/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: specification info, auditing, sanitization, restoration, and session zeroization. Audit vs. sanitize is disambiguated by the attestation receipt focus, and restore vs. reset_session by their opposite data-mapping operations.

    Naming Consistency4/5

    All tools use the ztds_ prefix and snake_case, giving a predictable namespace. Minor inconsistency exists because ztds_info is noun-based while most others are verbs, and ztds_reset_session is the only multiword action name.

    Tool Count5/5

    Five tools is well-scoped for this domain, with each tool earning its place across info, sanitize, audit, restore, and reset operations. There is no obvious redundancy or missing sibling tool at this count.

    Completeness4/5

    The surface covers the core lifecycle: read the standard, sanitize text, audit for compliance, restore mappings, and zeroize session data. Minor gaps remain around explicit session/status inspection or policy configuration, but core agent workflows are supported.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources