Kavra Siegel — Qualified eIDAS Timestamping MCP Server

by mscharfetter Your server? Claim it

not responding

Kavra Siegel — Qualified eIDAS Timestamping is listed as active in the registry but did not answer our last check. It exposes 3 tools.

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

Uptime history 91 days of history · worst day 0%

91 days agonow

0.0%

Uptime 24h

0 of 91 checks

Tools

read from the server

210 ms

Response time

average over 24h

open, no key

Access

streamable-http

Kavra Siegel — Qualified eIDAS Timestamping does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add kavra-siegel --transport http https://siegel.kavra.cloud/mcp

Settings → Connectors → Add custom connector, then paste this address

https://siegel.kavra.cloud/mcp

~/.codex/config.toml

[mcp_servers.kavra-siegel]
url = "https://siegel.kavra.cloud/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "kavra-siegel": {
      "url": "https://siegel.kavra.cloud/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "kavra-siegel": {
      "type": "http",
      "url": "https://siegel.kavra.cloud/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

kavra

kavra_siegel_stamp_content

Erzeugt einen qualifizierten eIDAS-Zeitstempel für base64-encodierten Inhalt (max 1 MB). Hash wird serverseitig berechnet. RFC 3161 via SIGNIUS/IDnow.

kavra_siegel_stamp_hash

Erzeugt einen qualifizierten eIDAS-Zeitstempel für einen SHA-256-Hash. RFC 3161 via SIGNIUS/IDnow Trust Services AB (EU Trusted List).

kavra_siegel_verify_token

Verifiziert einen Stempel-Token anhand seiner UUID.

Endpoints

URL	Transport	State	Latency	Checked
https://siegel.kavra.cloud/mcp	streamable-http	answering	210 ms	7 min ago

Alternatives to Kavra Siegel — Qualified eIDAS Timestamping

same job, measured the same way

aictrl

by aictrl

Project context, backlog tasks, and controlled workflows for coding agents. OAuth sign-in.

answering

Vamoose

by dcadolph

Calendar workflow engine for time off, approvals, and quick actions on any calendar backend.

local only

Vynn MCP

by beee003

Self-improving AI workflows with backtesting, prompt optimization, and scheduling

127 installs/wk local only

Pathista

by pathista

Step-by-step workflows for ChatGPT, Claude and Claude Code: the AI gets one step at a time.

answering

Wavedash

by wvdsh

Wavedash docs and workflow guidance for building and publishing browser games.

4 tools answering

Scribefy

by mkirovbg

Search YouTube, get video metadata, and extract timestamped transcripts for AI workflows.

67 installs/wk local only

Openttt Pot

by helm-protocol

Cryptographic audit trail for Claude Code workflows — tamper-proof timestamps, IETF TTTPS compliant.

114 installs/wk local only

Pagespeed Insights MCP

by ruslanlap

Google PageSpeed Insights and CrUX: six workflow tools for web performance.

615 installs/wk local only

Kavra Siegel — Qualified eIDAS Timestamping — questions

Answers built from our own checks of this server.

What can Kavra Siegel — Qualified eIDAS Timestamping do?

It exposes 3 tools, read directly from the server on our last check. Among them: kavra_siegel_stamp_content, kavra_siegel_stamp_hash, kavra_siegel_verify_token. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Kavra Siegel — Qualified eIDAS Timestamping working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 210 ms. The bar chart above shows every period we have measured.

The registry lists Kavra Siegel — Qualified eIDAS Timestamping as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect Kavra Siegel — Qualified eIDAS Timestamping?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Kavra Siegel — Qualified eIDAS Timestamping need an API key?

No. Kavra Siegel — Qualified eIDAS Timestamping completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.