---
title: "MCP Trust Boundary Suite"
canonical: https://trickest.com/library/mcp-trust-boundary-suite
description: "Inventory HoneyMCP ghost tools and MCParasite channels, then correlate MCP trust-boundary findings you can retest."
---

# MCP Trust Boundary Suite

## Overview

MCP servers widen what an agent can touch. Ghost tools, miswired channels, and scenario inventories need a smoke path that does not require SaaS tokens, plus a place to drop your own HoneyMCP config when you harden a real stack.

This is a standing check for [continuous security testing](/use-cases/continuous-security-testing). You seed a demo HoneyMCP config, run HoneyMCP for a ghost-tool catalog and MCParasite for channel or scenario inventory, then correlate findings with a retest delta when MCP configs change.

It sits next to [Web AI Agent Audit](/library/web-ai-agent-audit) (embedded web agents). This Collection unit is the MCP trust-boundary path: config and channel inventory first. Set MCParasite `mode=run` and LLM keys when you want a live kill-chain.

## Pipeline

1. Seed · Demo HoneyMCP config emits a fixture `honeymcp.yaml` for the smoke path.
2. Scan · HoneyMCP ghost catalog reads that config and lists ghost or unexpected tools.
3. Scan · MCParasite channels inventories channels or scenarios (list mode by default).
4. Results · Correlate merges both folders into findings, inventory, remediation, and retest_delta outputs.

## Inputs

- **Seed HoneyMCP config.** Default demo YAML. Replace with your `honeymcp.yaml`.
- **MCParasite mode.** Default list/inventory. `run` needs LLM keys in vault (chips already wired) and executes a live kill-chain.

## Outputs

- **findings.jsonl.** MCP trust-boundary hits with remediation hints.
- **inventory.jsonl.** Tools and channels observed.
- **retest_delta.jsonl.** Schedule-as-diff scaffold when MCP configs change.

## Integrations

- [HoneyMCP](/tools/honeymcp) (BHUSA 2026 Arsenal)
- [MCParasite](/tools/mcparasite) (BHUSA 2026 Arsenal)

## Sample output

Sample shape from the correlate pack on the demo config (illustrative, not a live KPI).

```jsonl
{"kind":"finding","title":"Ghost or unexpected MCP tool exposure","severity":"high"}
{"kind":"inventory","note":"MCP channel or scenario row from the list pass"}
{"kind":"retest_delta","note":"Schedule re-runs when honeymcp.yaml or channel wiring changes"}
```

## FAQ

### Do I need SaaS tokens for the smoke?

No. The default seed and list modes run without SaaS credentials.

### When do I enable MCParasite run mode?

Set `mode=run` on MCParasite and add OpenAI or Anthropic keys in vault (already wired on the node). Default `list` stays on inventory.

### Why schedule this?

Correlate emits `retest_delta.jsonl` so scheduled re-runs can surface MCP config drift after agent and server changes.

## Related workflows

- [Web AI Agent Audit](/library/web-ai-agent-audit). Reach for this instead when the surface is an embedded web chat agent, not MCP server config.
- [Coding Agent Policy Gate](/library/coding-agent-policy-gate). Reach for this instead when the job is coding-agent action policy, not MCP server config.
- [CICD Attack Surface Scanner](/library/cicd-attack-surface-scanner). Reach for this instead when the trust boundary is CI YAML, not MCP.

---
_Markdown source of https://trickest.com/library/mcp-trust-boundary-suite._