mirror of
https://github.com/NousResearch/hermes-agent.git
synced 2026-11-06 05:17:15 +00:00
25 lines
2.0 KiB
YAML
25 lines
2.0 KiB
YAML
# Pethost's own package: the hermes/ folder of the repository the other agents install Pethost from.
|
|
name: pethost
|
|
title: Pethost
|
|
repo: https://github.com/pethost-dev/plugin
|
|
sha: 33f6947d88c60b6e84a8d9a646e96d25100f1c26
|
|
subdir: hermes
|
|
version: "1.9.1"
|
|
maintainer: pethost-dev
|
|
tier: community
|
|
category: platform
|
|
docs_url: https://github.com/pethost-dev/plugin/tree/main/hermes#readme
|
|
readme: true
|
|
# The package is a skill and an HTTPS connection; validated with v0.21.6 and v0.22.5 on Linux amd64.
|
|
platforms: []
|
|
description: "Deploy and run Docker Compose projects on Pethost with its skill and Pethost's hosted MCP server: deploys, logs and requests, rollbacks, backups and restores, domains and commands in containers. Disclosure — connects Hermes to Pethost's hosted MCP server (mcp.pethost.dev), signed in by OAuth through `hermes mcp add pethost --url https://mcp.pethost.dev/mcp --auth oauth`, with no key or token in the package; the package marks its server untrusted, but that native entry replaces it and runs at trust: full unless mcp_servers.pethost.trust is set to untrusted, as the README's install does; tools act on the account's machine (deploys, restarts, restores, deletions, commands in containers); to move files the skill has Hermes run tar and curl in commands the skill writes, only to https at the machine's own hostname (*.pethost.network) under /transfer/, never a command the server returns, and says before an upload that the project folder goes as it is, .env included; it also has Hermes generate app secrets with openssl in the user's shell and fetches a deployed site to check it."
|
|
known_issues:
|
|
- "The package's own connection is not signed in and registers no tools: the README's `hermes mcp add` step signs in by OAuth, and the native entry it writes overrides the package connection and trust setting."
|
|
# MCP tools are discovered from the remote server; the package registers no native tools or hooks.
|
|
capabilities:
|
|
provides_tools: []
|
|
provides_hooks: []
|
|
provides_middleware: []
|
|
requires_env: []
|
|
requires_hermes: ">=0.21.6"
|