SecureStamp Action Proof — Cross-Cloud Public Beta (Unverified)

online.securestampPublished by securestamp.onlineOfficial publisherv0.3.0-beta.2Updated Oct 27, 2026

UNVERIFIED: cross-cloud beta; sandbox by default; production opt-in via customer Guardian.

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

SecureStamp Action Proof MCP server that lets an assistant call a customer-hosted Guardian service to record and verify action proofs, sandboxed by default.

What you can do
  • No tool list is published, so capabilities are known only from the manifest and description.
  • The server is a bridge to a customer-run Guardian service reached through a local Unix socket.
  • It exposes a small set of beta tools, with an optional profile that unlocks six sandbox tools or an explicit production opt-in.
  • It fails closed when the Guardian socket is unavailable, so calls stop rather than proceed unverified.
When to use it
Consider it when you already run a SecureStamp Guardian and want an assistant to attach verifiable action proofs to its work, starting in the sandbox profile. It is a cross-cloud beta and marked unverified, so treat it as an evaluation rather than a production dependency.
Requirements
A remote endpoint at mcp.securestamp.online or the local npm package run over stdio. OAuth 2.1 bearer token sent in the Authorization header is required. The GUARDIAN_SOCKET_PATH environment variable must point to an absolute path of the customer Guardian Unix socket. SECUESTAMP_RELEASE_PROFILE optionally selects cross-cloud-beta or productive-beta.
Before you install
The registry marks it unverified and in cross-cloud beta. It requires an OAuth bearer token in the Authorization header, so grant only the scopes you intend. Setting the release profile to productive-beta opts into production behavior, which may record or act on real data; keep the default sandbox profile until you have reviewed it. Proof data is exchanged with the customer Guardian service.

Installation

In SourceWeft

  1. Open SecureStamp Action Proof — Cross-Cloud Public Beta (Unverified) 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/online.securestamp%2Faction-proof/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": {
    "securestamp-action-proof-cross-cloud-pub": {
      "type": "http",
      "url": "https://mcp.securestamp.online/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.3.0-beta.2LatestSep 16, 2026

Score

60% 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
  • Documentation15 pts

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

  • License10 pts

    Declare a license in the repository or the registry entry.