Skip to main content
Glama
SemanticDataCharter

sdc-mapper-mcp

Official
by SemanticDataCharter
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to sdc-mapper-mcp

No user-submitted related servers found.

    Related Servers

    • VeriLock MCP

      clevertech-os
      A
      license
      A
      quality
      C
      maintenance
      Provides read-only access to VeriLock document metadata and cryptographic evidence, enabling clients to list, retrieve, verify, and audit documents through the Model Context Protocol.
      8
      MIT

    • MAPI

      cabo0m
      A
      license
      Not graded
      quality
      D
      maintenance
      An auditable memory, lifecycle, and governance server for AI agents, providing durable memories with provenance, lifecycle management, and guarded workflows through the Model Context Protocol.
      Apache 2.0

    • Klarova

      samson-ailabs
      A
      license
      Not graded
      quality
      D
      maintenance
      A governed context layer for internal data exposed over MCP, enabling agents to query governed definitions, retrieve grounded data, and execute scoped actions with citations and auditing.
      Apache 2.0

    • harvey-design-system-mcp

      thenpceo
      A
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol server that exposes a versioned brand package (tokens, rules, recipes, media rights, and audit gates) as resources, tools, and prompts for AI agents. It enables agents to plan and audit on-brand UI, image, motion, and video outputs while remaining read-only and credential-free.
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.7/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: listing targets, mapping a record, validating a mapping file, comparing fidelity across mappers, summarizing the log, and verifying log integrity. Although map_record and fidelity both involve mapping a record, their scopes are clearly separated (single target vs. cross-target comparison) and descriptions make the boundary explicit.

    Naming Consistency4/5

    Most tools follow a clear verb_noun pattern (list_targets, map_record, check_mapping, log_summary, verify_log), with 'fidelity' being the lone noun-only exception. The set remains readable and predictable overall, but the deviation prevents a perfect score.

    Tool Count5/5

    Six tools is well-scoped for a mapping and logging server, and each tool appears to earn its place. There is no apparent bloat or missing essential operation at the count level.

    Completeness4/5

    The surface covers target listing, mapping, mapping validation, cross-target fidelity comparison, log summarization, and log integrity verification. Minor gaps exist around discovering available models or mapping files, but core workflows are covered and agents can work around these omissions.

    Resources