Passport

com.scopeblindPublished by scopeblind.comv0.4.3Updated Oct 28, 2026

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

The publisher's own server: Passport.Me

VerifiedSTDIODesktop onlySecurity & MonitoringAI & ML

Overview

AI-generated overview

Local stdio MCP server providing portable cryptographic identity for AI agents, built on Ed25519 keypairs and signed manifests.

What you can do
  • The registry entry gives only a one-line purpose: portable cryptographic identity for AI agents.
  • No tools, instructions or README are published, so the exact operations an assistant can perform are not documented.
  • The stated building blocks are Ed25519 keypairs and signed manifests, suggesting identity creation and signing/verification of agent manifests.
When to use it
Consider it when you want an assistant to work with agent identity material, such as Ed25519 keys or signed manifests, on your own machine. Because no tool list or documentation is available, evaluate it only if you can inspect the package yourself first.
Requirements
Runs as a local process over stdio, installed from the npm package @scopeblind/passport, so a Node.js runtime is needed. Desktop only; no web execution. No authentication, environment variables or headers are declared.
Before you install
It deals with cryptographic keys and signed identity data, so treat any key material it creates or stores as sensitive. No tools, instructions or README are published, so what it writes, stores or sends elsewhere cannot be verified from the listing; review the package before use.

Installation

In SourceWeft

  1. Open 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.3LatestSep 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