Live, free, 60 minutes
MCP workshops for teams
Hands-on sessions built on the data behind this registry: what we see when we connect to thousands of MCP servers. Bring your own server list; leave with an approval checklist and a cost estimate.
Vetting MCP servers before you connect them
For: Security and platform teams writing an MCP allowlist
- ›What an MCP server can actually do on a developer's machine, and how to tell from its tool list
- ›Tool poisoning and prompt injection in tool descriptions: real examples from our scans
- ›A practical approval checklist: provenance, install scripts, maintenance, credentials, egress
- ›Running servers in a sandbox and scanning them with open-source tooling (vectra-guard)
Cutting the token cost of agent tool use
For: Teams running Claude Code, Cursor or custom agents at scale
- ›Where the context tax comes from: tool schemas resent on every turn
- ›Measuring your own stack: which servers cost the most per 1,000 turns
- ›Deferred tool loading, trimming tool sets and prompt caching, with before/after numbers
- ›For server authors: rewriting descriptions and schemas to halve their footprint
Private session for your team
We can run either track for your team against the MCP servers you actually use, with a written report afterwards. Email admin@mcpskillhub.com.