Bring Ai Recruiting
to Pydantic AI
Learn how to connect Mav to Pydantic AI and start using 9 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Mav MCP Server?
Connect your Mav AI recruiting account to any AI agent and manage candidate screening through natural conversation.
What you can do
- Candidate Screening — Trigger automated AI screening conversations
- SMS Campaigns — Launch and manage outbound SMS recruiting campaigns
- Lead Management — Browse candidates and their qualification status
- Engagement Tracking — Monitor open rates, reply rates, and drop-offs
- Interview Data — Access responses and screening transcripts
How it works
1. Subscribe to this server
2. Enter your Mav API Key
3. Start managing recruiting campaigns from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Recruiters — automate initial candidate screening at scale
- Talent Acquisition — run high-volume SMS outreach campaigns
- HR Ops — monitor hiring funnel metrics and candidate engagement
Built-in capabilities (9)
Create a lead and trigger a playbook
Get details for a specific lead
Get details for a specific playbook
List recent activities/events
List all leads
List all available Mav playbooks
Manually opt-out a lead
Stop a running playbook for a lead
Update an existing lead
Why Pydantic AI?
Pydantic AI validates every Mav tool response against typed schemas, catching data inconsistencies at build time. Connect 9 tools through Vinkius and switch between OpenAI, Anthropic, or Gemini without changing your integration code. full type safety, structured output guarantees, and dependency injection for testable agents.
- —
Full type safety: every MCP tool response is validated against Pydantic models, catching data inconsistencies before they reach your application
- —
Model-agnostic architecture. switch between OpenAI, Anthropic, or Gemini without changing your Mav integration code
- —
Structured output guarantee: Pydantic AI ensures tool results conform to defined schemas, eliminating runtime type errors
- —
Dependency injection system cleanly separates your Mav connection logic from agent behavior for testable, maintainable code
Mav in Pydantic AI
Mav and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Mav to Pydantic AI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Mav in Pydantic AI
The Mav MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 9 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Pydantic AI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Mav for Pydantic AI
Every tool call from Pydantic AI to the Mav MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I trigger AI screening conversations?
Yes. Launch SMS or web-based screening flows and track candidate responses automatically.
How does Mav authentication work?
Mav uses a custom API Key header against hiremav.com/api/v2.
Can I track campaign engagement metrics?
Yes. Monitor open rates, reply rates, completion rates, and candidate drop-off points.
How does Pydantic AI discover MCP tools?
Create an MCPServerHTTP instance with the server URL. Pydantic AI connects, discovers all tools, and generates typed Python interfaces automatically.
Does Pydantic AI validate MCP tool responses?
Yes. When you define result types as Pydantic models, every tool response is validated against the schema. Invalid data raises a clear error instead of silently corrupting your pipeline.
Can I switch LLM providers without changing MCP code?
Absolutely. Pydantic AI abstracts the model layer. your Mav MCP integration works identically with OpenAI, Anthropic, Google, or any supported provider.
MCPServerHTTP not found
Update: pip install --upgrade pydantic-ai