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.
git clone --depth 1 https://github.com/Tempguru-co/tempguru-mcpWrote 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.
[](https://agentmods.dev/mcp/tempguru-co/tempguru-mcp/event-staffing)<a href="https://agentmods.dev/mcp/tempguru-co/tempguru-mcp/event-staffing"><img src="https://agentmods.dev/badge/mcp/tempguru-co/tempguru-mcp/event-staffing/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/tempguru-co/tempguru-mcp/event-staffing"><img src="https://agentmods.dev/badge/mcp/tempguru-co/tempguru-mcp/event-staffing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
event-staffing 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 9d 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.
Copies of this mod
3 near-identical copies found in the catalogue:
- bringfour — 86% identical, 9 lines differ
- loa-mcp-server — 81% identical, 9 lines differ
- markfetch — 81% identical, 9 lines differ
What it actually says
{
"event-staffing": {
"command": "npx",
"args": [
"-y",
"tempguru-mcp"
],
"env": {}
}
}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.
- 9d ago First seen · 10 lines scan A d85b04cf720f
event-staffing is an MCP server published in the GitHub repository Tempguru-co/tempguru-mcp (2 stars, last pushed 2d 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.
Other mcp servers, from other repositories
connectwise-manage-mcp
MCP server "connectwise-manage-mcp" as configured in WYRE-AI/connectwise-manage-mcp. Runs in Docker (ghcr.io/wyre-ai/connectwise-manage-mcp:v1.8.8). Needs 8 environment variables to run.
syncro-mcp
MCP server "syncro-mcp" as configured in WYRE-AI/syncro-mcp. Runs in Docker (ghcr.io/wyre-ai/syncro-mcp:v1.4.9). Needs 5 environment variables to run.
halopsa-mcp
MCP server "halopsa-mcp" as configured in WYRE-AI/halopsa-mcp. Runs in Docker (ghcr.io/wyre-ai/halopsa-mcp:v1.7.13). Needs 7 environment variables to run.
mcp-server
Project portfolio management for PMOs. Alternative to Microsoft Project Online. OAuth + PAT. Remote server at mcp.onplana.com.
openproject-mcp-server
MCP server for OpenProject: 87 tools for work packages, attachments, git activity, time tracking, meetings and reporting over the API v3. Runs locally from the openproject-mcp-server Python package. Needs 5 environment variables to run.
delega
Task management API for AI agents. Create, delegate, and track tasks via MCP. Runs locally from the @delega-dev/mcp npm package. Needs 2 environment variables to run.