Travseal

io.github.simohammedbPublished by GitHub account simohammedbv2.0.0Updated Oct 24, 2026

A plug-and-play MCP Server for automated, low-cost C2PA provenance stamping via Base L2.

VerifiedSSEWeb executableSecurity & Monitoring

Overview

AI-generated overview

A remote MCP server that stamps content with C2PA provenance records using the Base L2 blockchain.

What you can do
Travseal is a plug-and-play MCP server for automated C2PA provenance stamping, described as low-cost and settled via Base L2. It is offered as a remote endpoint over SSE, so an assistant connects to it rather than running it locally. No tools are listed in the manifest, so the exact operations it exposes are not documented here.
When to use it
Consider it when you want an assistant to attach C2PA provenance or content-credential records to media as part of a workflow, and you are comfortable with a hosted third-party endpoint. It is less suitable if you need documented tool names, local execution, or offline operation.
Requirements
A client that supports the SSE transport and network access to the remote endpoint. No packages, environment variables, headers, or authentication are declared in the manifest.
Before you install
The endpoint is a third-party remote host, so content submitted for stamping leaves your machine. The manifest declares no authentication, meaning anyone with the address may be able to reach it. Blockchain settlement on Base L2 may involve transaction costs, and the manifest lists no tools, so verify what it actually does before sending sensitive material.

Installation

In SourceWeft

  1. Open Travseal in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.simohammedb%2Ftravseal/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "travseal": {
      "type": "sse",
      "url": "https://exclusive-magical-insights-usr.trycloudflare.com/"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v2.0.0LatestSep 16, 2026

Score

28% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.