MCP Tools DirectoryAbout this integration
Nostr-authenticated MCP server for secure YunoHost administration.
- Transport
- stdio
- Authentication
- unknown
- Initial setup
- user-authorization
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.8.46
- Package
- yunohost-mcp-connect
- Last compatibility test
- Not independently tested
Connect your agent
yunohost-mcp-connectPublisher documentation reviewed only. No key was generated, no YunoHost service was contacted, and no administrative action was attempted. Local stdio server mode is explicitly fully trusted and should remain restricted.
Capabilities: YunoHost administration, incident diagnostics, signed remote MCP bridge, delegated access, owner-approved high-risk operations
Connected profiles
Additional details
io.github.imattau/yunohost-mcp
Source ↗ · Checked 2026-09-170.8.46
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17pypi
Source ↗ · Checked 2026-09-17yunohost-mcp-connect
Source ↗ · Checked 2026-09-190.8.50
Source ↗ · Checked 2026-09-19The reviewed Python artifact provides a local stdio connector that forwards MCP requests to a remote HTTP server and signs them with a per-client Nostr key; the same package also exposes server and approval commands.
Source ↗ · Checked 2026-09-19Authentication is NIP-98 rather than a native taxonomy option: each client uses a distinct local private-key file, the corresponding npub receives a server role, optional delegations are signed bearer credentials, and listed high-risk operations require owner co-signature.
Source ↗ · Checked 2026-09-19Run yunohost-mcp-connect with a remote HTTPS MCP URL and a mode-0600 key file, then point the MCP client at the local stdio connector.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19