ooruby: verified AI agents and MCP servers

Hermoso

hermoso · MCP server

Marketing on autopilot, run from your own AI agent. 863 tools. Publishing, scheduling, ad campaign management, comments, DMs and analytics cost no credits on every plan; credits are only for generatin

Not claimed by its maker. Is this yours? Prove it and answer the findings

The registry now serves 0.1.372. Everything measured on this page describes 0.1.305.

Findings, provenance and the install command are records of the scanned version, not the one npm would give you today. Treat them as history until this listing is rescanned. Registry checked 2026-10-03.

Not yet tested

Command execution is bounded: inventory; node child_process (bin/hermoso.mjs:438); An inventory of where the code starts another program, not a verdict on this row: whether each one runs a fixed program or whatever it is handed takes a reading by hand.

Published because it was found. A finding is information about where the limits are, not a verdict that the software is unsafe.

What this does not cover

Everything. Treat it as you would software from anywhere else.

Receipt history: every signed receipt for every version of this listing, and what changed between them.

What it does

Compare with

Compare all 4

How far this has been checked

Static scanned

What it establishes: Its published package, or for a hosted server its source repository at a recorded commit, was read file by file, without running it, by every check in our current scan.
What it does not: How it behaves when it runs, or anything the scan does not read yet: several rubric checks, the repository's history, and compiled code in folders named dist or build. For a hosted server, that the endpoint runs the code that was read. The ooruby Index sets out exactly what was read.
Exactly what was read: Version 0.1.305, the file with digest sha512-TPrYK1KfaULlDthEnl7ennW4A0/1VPTdWHSbDfGQW5k5yS+l1XgELc3IZmwCZSAsLpNH6o1GgEpH03jOAGYMNQ==, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.

How the rungs work

Adding it

Paste this into your client's MCP configuration.

{
  "mcpServers": {
    "hermoso": {
      "command": "npx",
      "args": [
        "-y",
        "hermoso@0.1.305",
        "mcp"
      ]
    }
  }
}

Or run it directly.

npx -y hermoso@0.1.305 mcp

Pinned to 0.1.305, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.

18,826 installs last month · no published advisories · checked 2026-10-03

Where this came from

Registry: npm
Package: hermoso
Version read: 0.1.305
Resolved: 2026-09-25

Open the source

No build provenance published. The repository above is the one the publisher declared, and nothing links it to the package you would install. That is not a mark against this listing, since most packages are published this way, but it is a check nobody can run.

The badge, if this is your listing

It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.

[![ooruby: static scanned](https://ooruby.com/api/badge/hermoso)](https://ooruby.com/market/hermoso)

About this listing

Kind: MCP server
Category: Data & analytics
Pricing: Free
Sandbox: No
Hosted: No
Updated: 2026-09-25

Similar MCP servers

Verification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.