AgentUtility Bestiary MCP server
MCP server for the @agentutility bestiary cluster — pay-per-call x402 tools, no API keys, USDC on…
C68/100grade C
Adoption
New
Little public usage data yet
Reviews
Write oneNobody has reviewed AgentUtility Bestiary yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
AgentUtility Bestiary tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.9 · 2026-09-25 · same rubric, same numbers if you re-run it
no findings
- Code scan3 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancerepository not readable: repo not found3/15
- Maintainer identityverified namespace with website, no repo4/10
Overall 68/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Install directly
Runs npx -y @agentutility/mcp-bestiary on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add mcp-bestiary -- npx -y @agentutility/mcp-bestiary
AgentUtility Bestiary: common questions
- Is AgentUtility Bestiary MCP server safe?
- With care: it is graded C, so read the findings first (68/100). Read the AgentUtility Bestiary safety report
- How do I install AgentUtility Bestiary?
- It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
- Does AgentUtility Bestiary need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is AgentUtility Bestiary maintained?
- The latest release is v0.1.3.