Skip to main content
Glama
etchv-labs

Etchv MCP Server

Official
by etchv-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Etchv MCP Server

No user-submitted related servers found.

    Related Servers

    • Brandize MCP server

      minim-l
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables clients to generate AI logos and full brand kits, create color palettes, SEO meta tags, and JSON-LD schema markup, search design guides, and handle paid logo generation workflows through a hosted streamable-HTTP endpoint.
      MIT

    • SammaPix

      samma1997
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to run real image and PDF processing remotely — compressing, converting, resizing, cropping, watermarking, and chaining multiple operations in a single call — with no local install and zero-retention handling.
      8
      MIT
    • DocImprint Document Intelligence by sawftware-apps

      DocImprint Documentofficial

      sawftware-apps
      A
      license
      A
      quality
      D
      maintenance
      Verifiable document intelligence for AI agents. Extract text, tables, and structured data from PDFs and URLs. Summarize, answer questions, check claims, and translate — all with cited evidence. Store tamper-evident evidence bundles with cryptographic signatures and on-chain attestation via Base L2. Cross-document semantic search and Q&A across named collections. Pay per call with USDC
      22
      2 npm
      1
      MIT
    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

    A3.6/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools target a distinct resource+action pair, and descriptions clarify the job-based flow (watermark/detect → get_job → get_job_result). The only mild overlaps are get_job vs get_job_result and the storage delivery list/get pair, but the descriptions make the boundaries readable.

    Naming Consistency5/5

    Every tool follows a predictable snake_case verb_noun pattern (list_assets, get_asset, download_asset, update_asset, delete_asset, store_asset, redeliver_webhook, etc.). No camelCase or vague verbs break the pattern.

    Tool Count4/5

    18 tools is slightly heavy but justified: four distinct areas (watermarking jobs, assets, storage destinations/deliveries, webhooks) each need CRUD-ish coverage. Nothing feels gratuitous, though a couple of read tools could conceivably be folded together.

    Completeness3/5

    Assets cover read/download/update/delete but there is no create/upload operation, and webhooks expose list/redeliver/deliveries but no create or delete (explicitly deferred to the dashboard). These are deliberate gaps but leave agents unable to complete full lifecycle workflows without leaving the tool surface.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources