LPD eIDAS Stamp

digital.lapruebaPublished by laprueba.digitalOfficial publisherv1.0.0Updated Oct 29, 2026

Stamps files/text with eIDAS & Polygon. Requires API Key. Docs: laprueba.digital/mcp/docs

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Remote MCP server that lets an assistant stamp files or text with eIDAS and Polygon timestamps via the laprueba.digital API.

What you can do
  • Stamp files or text with eIDAS-compliant timestamps.
  • Stamp content with Polygon (blockchain) anchoring.
  • No individual tools are listed in the manifest, so exact operations are only described in the provider's documentation.
When to use it
Useful when you need to prove that a file or piece of text existed at a certain time and want the assistant to create eIDAS or Polygon-backed proofs as part of a workflow.
Requirements
A remote MCP endpoint at mcp-api.laprueba.digital over streamable HTTP; OAuth authentication is required, and the provider states an API key is needed. No environment variables or headers are declared.
Before you install
Stamping submits your files or text to a third-party service (laprueba.digital), so check what content may be sent. An API key and OAuth credentials are required; the provider may charge for stamping, so confirm pricing before use.

Installation

In SourceWeft

  1. Open LPD eIDAS Stamp in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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/digital.laprueba%2Fstamp-eidas/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "lpd-eidas-stamp": {
      "type": "http",
      "url": "https://mcp-api.laprueba.digital/mcp"
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestOct 29, 2026

Score

56% 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 listed15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • 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.