meok-compliance-passport-mcp

io.github.CSOAI-ORGPublished by GitHub account CSOAI-ORGv1.0.2Updated Oct 24, 2026

Agent Compliance Passport MCP server - portable, signed credentials AI agents carry to prove complia

The publisher's own server: Passport.Me

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

A local MCP server that issues portable, signed compliance credentials, called passports, for AI agents to carry as proof of compliance.

What you can do
Issues signed compliance passports for AI agents, according to the registry description, so an agent can present portable proof of compliance. The manifest lists no tools, so the exact operations an assistant can call are not documented here. It runs as a local process on the user's machine and is intended for desktop use only.
When to use it
Consider it when you need an AI agent to carry verifiable, signed evidence of compliance that can be presented to others. It is not a fit if you need documented tools or a web-hosted endpoint, since neither is described.
Requirements
Runs locally over stdio as a Python package, launched with uvx, so a Python environment with uvx available is needed. It is desktop only and not web executable. No authentication, environment variables or headers are declared.
Before you install
The description is very short and no tools, README or instructions are provided, so what the server actually does and what data it handles cannot be verified before installing. Treat the signed credentials it produces as sensitive and review the package before running it locally.

Installation

In SourceWeft

  1. Open meok-compliance-passport-mcp 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. v1.0.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