Skip to main content
Glama
noga7

MCP Content Credentials Server

by noga7
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to MCP Content Credentials Server

No user-submitted related servers found.

    Related Servers

    • c2pa-mcp

      harelrech
      A
      license
      A
      quality
      A
      maintenance
      Verifies C2PA Content Credentials for local files or URLs and returns an LLM-ready verdict on trust, AI generation, and provenance.
      4
      282 npm
      1
      Apache 2.0

    • chronoverify-mcp

      beeswaxpat
      A
      license
      A
      quality
      B
      maintenance
      Provides MCP-compatible AI agents with a verify_image tool to check a photo's capture time and provenance using C2PA, EXIF, XMP metadata, and pixel forensics, returning a verdict and confidence score.
      1
      32 npm
      2
      MIT

    • is-it-ai-mcp

      JohannsenLum
      A
      license
      A
      quality
      B
      maintenance
      An MCP server that reads a file's embedded C2PA Content Credential to report whether it declares AI generation or a real-world capture, and checks whether that declaration's signature still verifies against the file's current bytes.
      2
      23 PyPI
      MIT

    • mtl-c2pa-mcp

      musictechlab
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for reading C2PA content provenance manifests from media files, enabling natural language queries about AI-generated content, signatures, and provenance.
      3
      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

    A4.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes based on input source: read_credentials_file handles local files while read_credentials_url handles URLs. Their descriptions explicitly specify when to use each tool, eliminating any potential confusion about which to select for a given scenario.

    Naming Consistency5/5

    Both tools follow an identical verb_noun pattern (read_credentials_file and read_credentials_url) with perfect consistency. The naming clearly indicates the action (read) and distinguishes the input type (file vs URL) in a predictable manner.

    Tool Count3/5

    With only 2 tools, the server feels somewhat thin for a Content Credentials domain that could benefit from additional operations like validation, manifest listing, or credential creation. While the two tools cover the core reading functionality from different sources, the scope seems limited compared to what a comprehensive C2PA/credentials server might offer.

    Completeness2/5

    The server only provides read operations from two input sources, missing essential capabilities for a Content Credentials domain. There are no tools for creating, updating, validating, or managing credentials, nor tools to list available manifests or check credential status. This creates significant gaps that would limit agent workflows beyond basic information retrieval.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources