Scopeblind Passport

io.github.tomjwxfPublished by GitHub account tomjwxfv0.4.2Updated Oct 24, 2026

Portable cryptographic identity for AI agents. Ed25519 keypairs and signed manifests.

The publisher's own server: Passport.Me

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

Gives an assistant a portable cryptographic identity: Ed25519 keypairs and signed manifests, run locally over stdio.

What you can do
Scopeblind Passport provides portable cryptographic identity for AI agents. According to its registry description, it works with Ed25519 keypairs and signed manifests, so an assistant can hold a keypair and produce or verify signed manifest data. No tool list is published, so the exact operations exposed are not documented here.
When to use it
Consider it when an assistant needs a stable cryptographic identity or signed manifests, for example to sign or verify agent-related artifacts. It is a narrow, identity-focused server rather than a general-purpose toolset.
Requirements
Runs as a local process on the user's machine over stdio, installed from the npm package @scopeblind/passport, so a Node.js runtime is needed. The manifest declares no authentication, environment variables, or headers. Desktop only; no web executable.
Before you install
It handles cryptographic key material, so private keys generated or stored by the server are sensitive and should be protected. The manifest declares no credentials, but the README is unavailable, so review what the server does with keys and where it writes them before installing.

Installation

In SourceWeft

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

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.4.2LatestSep 16, 2026

Score

25% 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 days25 pts

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

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

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Passport integrations