BotShelf Vampire BOTSHELF VAMPIRE Register

Library · Team · MCP · monitoring

MCP mcp Ops Untested tool-protocol free

Monitoring Check — MCP

Turn a status paste or log snippet into a short health note: what changed, severity, and a reversible next step. (MCP-oriented tool + prompt pack (read-only first).)

Id: mcp/monitoring · Slug: monitoring · Status: Untested · Untested on this machine — recipe reviewed for safety (no secrets, no destructive commands, no auto-spend). Mark tested after you run it locally.

What is this

MCP for MCP. Turn a status paste or log snippet into a short health note: what changed, severity, and a reversible next step. (MCP-oriented tool + prompt pack (read-only first).)

How this runtime fits

This MCP pack is an MCP integration / tool-enabled agent surface for the parent AI Team. Multi-agent language applies only when a host actually composes multiple agents around these tools.

Parent AI Team: monitoring · What is an AI Team?

What it does

Turn a status paste or log snippet into a short health note: what changed, severity, and a reversible next step. (MCP-oriented tool + prompt pack (read-only first).)

Who for

Builders working on Ops jobs who can run MCP themselves.

Need to run

How to use

  1. Review server_hints.md and implement only allowlisted read-only tools.
  2. Load prompt.md as the client system prompt.
  3. Run one Example in query with tools off; then enable library_search only.
  4. Confirm path allowlist before any file read tool.

Limitations

Test status

Status: Untested · Untested on this machine — recipe reviewed for safety (no secrets, no destructive commands, no auto-spend). Mark tested after you run it locally.

# MCP pack — Monitoring Check

## prompt.md (client)
You are an ops monitoring note-taker. Goal: short health note from a status paste.

RULES:
- Severity: info|warn|critical based only on provided signals.
- Prefer reversible next steps. No destructive commands.
- No auto-remediation that spends money or deletes data.
- If signal is insufficient, say so.

OUTPUT:
1) Status one-liner
2) What changed
3) Severity + evidence
4) Reversible next step
5) Owner / wait condition

## server_hints.md
Expose only read-only tools for stage 1, for example:
- `library_search` — search local catalog snippets the user installed
- `fetch_local_file` — read a path under an allowlisted directory

Tool design rules:
- No tool that sends email, posts to social, or charges payment.
- No tool that reads `~/.ssh`, `.env`, or browser cookie DBs.
- Arguments must be schema-validated; reject path traversal.
- Log tool calls for the human operator.

Example tool schema (illustrative JSON):
```json
{
  "name": "library_search",
  "description": "Search local BotShelf library snippets",
  "inputSchema": {
    "type": "object",
    "properties": {
      "query": {"type": "string", "minLength": 1, "maxLength": 200}
    },
    "required": ["query"]
  }
}
```

Wire this pack into an MCP-aware client with tools disabled until the allowlist is reviewed.
Status paste:
- netlify deploy: ok
- checkout function p95: 1800ms (was 400ms)
- error rate 2.1% (was 0.3%)
Window: last 30m
Status: checkout latency + errors elevated
Changed: p95 400→1800ms; errors 0.3→2.1%
Severity: warn (not confirmed outage)
Next: check last deploy diff; freeze new deploys if rising
Wait: 15m trend

Protocol-level pack. Prefer read-only tools. Never ship credentials inside MCP configs.

Parent: monitoring · implementation_id: mcp/monitoring

teams/monitoring/mcp · commit eb87e8e049fdf9908e438305ff827c7b617505b5 · license: free-use-at-own-risk

Structural check: PASS · env: structural (structural only — does not set Verified)

Soft thematic links only — not identity merges. Marketplace Teams ≠ Library AI Team records.