Relevant when…
You need to scope the trust boundary around an MCP deployment before commissioning a broader penetration test.
This is editorial fit guidance based on public positioning. We have not independently tested this provider or confirmed availability.
What the provider documents
- Assessment scope
- MCP assessment · Tool misuse
- Engagement model
- Assessment service
- Deliverables
- Prioritized recommendations, a technical and executive summary, and a handover session.
- Deployment
- One MCP deployment is the published starting scope; hosting support needs confirmation.
- Pricing
- Not published
- Retesting
- Confirm with provider
Source for documented facts: the provider’s official offering ↗. “Not published” means not recorded in the reviewed source, not that an option is unavailable.
Before you request a proposal
- Which live attack tests, if any, are included?
- Does your scope exceed five tool operations or one authentication flow?
- What production testing must be separately agreed?
Ask the provider to put authorized systems, exclusions, evidence handling, timing and acceptance criteria in the written scope. Do not send credentials or vulnerability evidence through an initial inquiry.
Sources & verification
- Bastet Security — official service information ↗
Supports the summary, service model, scope and recorded engagement facts above. Evidence status: provider-stated.