Kavra Siegel — Qualified eIDAS Timestamping

io.github.mscharfetterPublished by GitHub account mscharfetterv0.2.0Updated Oct 24, 2026

Qualified eIDAS RFC 3161 timestamping for AI workflow provenance. SIGNIUS/IDnow backbone.

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Lets an assistant obtain qualified eIDAS RFC 3161 timestamps to prove when a document or workflow output existed.

What you can do
This remote MCP server provides qualified eIDAS RFC 3161 timestamping, described as being for AI workflow provenance. It is backed by a SIGNIUS/IDnow infrastructure. The manifest lists no tools, so the exact operations are not documented here.
When to use it
Consider it when an assistant needs verifiable proof of existence or creation time for documents, outputs, or workflow steps under a qualified European timestamping scheme. It is not useful if you only need ordinary local timestamps.
Requirements
A remote MCP endpoint at siegel.kavra.cloud over streamable HTTP. The manifest declares no authentication, environment variables, or headers, and no packages.
Before you install
The manifest declares no authentication, so confirm how access is controlled before sending sensitive material. Timestamping typically submits a hash or document to an external qualified trust service, meaning data leaves your environment; check what is transmitted and any cost or account terms.

Installation

In SourceWeft

  1. Open Kavra Siegel — Qualified eIDAS Timestamping in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. 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.mscharfetter%2Fkavra-siegel/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": {
    "kavra-siegel-qualified-eidas-timestampin": {
      "type": "http",
      "url": "https://siegel.kavra.cloud/mcp"
    }
  }
}

Tools

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

Version history

1
  1. v0.2.0LatestSep 16, 2026

Score

67% 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
  • Auth declaredRequired10 pts
  • Tools listedRequired15 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.