pet-tools

pet-tools is an MCP server for Claude Code, Codex, Cursor, Gemini CLI, OpenCode from nschneir/PET-Project. Its token cost is not measured, scanned A, original, MIT.

A local MCP server for the pet-tools Python package. MCP lets a coding agent connect to outside tools through a standard interface.

In plain words
What is it for?
Running pet-tools locally as part of an agent setup. The supplied details do not say which pet-related jobs the server supports.
Why use it?
It gives the agent access to whatever pet-tools provides without requiring the package to be built into the agent itself.

MCP server for Claude CodeCodexCursorGemini CLIOpenCode

Written for no agent in particular: it speaks MCP, so any client can run it.

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add mcp/nschneir/pet-project/pet-tools
Clone the repo
git clone --depth 1 https://github.com/nschneir/PET-Project

Made for: Claude Code, Codex, Cursor, Gemini CLI, OpenCode.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for pet-tools

README.md
[![agentmods](https://agentmods.dev/badge/mcp/nschneir/pet-project/pet-tools.svg)](https://agentmods.dev/mcp/nschneir/pet-project/pet-tools)
Your own site
<a href="https://agentmods.dev/mcp/nschneir/pet-project/pet-tools"><img src="https://agentmods.dev/badge/mcp/nschneir/pet-project/pet-tools.svg" alt="Measured on agentmods" height="20"></a>
Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

pet-tools scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

listed in the official MCP registry · 8 lines

What it actually says

{ "pet-tools": { "command": "uvx", "args": [ "pet-tools" ] } }

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 5d ago First seen · 8 lines scan A 7b8cff802de6

Subscribe to this mod's changes

pet-tools is an MCP server published in the GitHub repository nschneir/PET-Project (1 stars, last pushed 13d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.