Skip to main content
Glama
Sign In
Ajinkya710

markproof-mcp

by Ajinkya710
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to markproof-mcp

No user-submitted related servers found.

    Related Servers

    • MCP Content Credentials Server

      noga7
      A
      license
      A
      quality
      D
      maintenance
      Enables reading and verifying C2PA Content Credentials from images and videos through both embedded manifests and invisible watermarks. Supports direct filesystem access, URL checking, and provides structured provenance data including creator identity, AI generation info, and content authenticity.
      2
      MIT

    • chronoverify-mcp

      beeswaxpat
      A
      license
      A
      quality
      D
      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
      51 npm
      2
      MIT

    • Check AI Free MCP Server

      hyai-dev
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to analyze images from a URL, local path, or Base64 string and determine whether they are AI-generated, including detection of signatures from Flux, Midjourney, DALL·E, and Stable Diffusion. Also inspects cryptographic C2PA provenance manifests, signing certificate authorities, and camera EXIF metadata without requiring API keys or accounts.
      2
      71 npm
      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.3/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a distinct action on a distinct input: mark_file writes a watermark to a file, verify_file inspects an arbitrary file for marks, and get_asset retrieves a stored record by asset_id. The descriptions make the file-path vs asset_id boundary explicit, so misselection is unlikely despite the shared 'record lookup' element in verify_file.

    Naming Consistency5/5

    All three tools follow a clean verb_noun pattern (mark_file, verify_file, get_asset) with consistent snake_case. The conventions are predictable enough that a caller can guess naming for any future tool.

    Tool Count5/5

    Three tools map exactly onto the narrow workflow of write-mark, check-mark, and fetch-record; nothing feels redundant or padded. This sits at the low end of the ideal 3-15 range but is well-matched to a single-purpose watermarking service.

    Completeness4/5

    The core lifecycle (mark, verify, retrieve by id) is fully covered with no dead ends for the primary use case. The main gap is the absence of a list/enumerate operation for assets marked by the account, so an agent must persist asset_ids itself; revocation or quota-checking is also absent but less critical.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources