Bring Dialer
to Pydantic AI
Learn how to connect Adversus to Pydantic AI and start using 7 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Adversus MCP Server?
Connect your Adversus account to any AI agent and take full control of your outbound sales operations, telemarketing, and CRM orchestration through natural conversation.
What you can do
- Campaign Orchestration — List all telemarketing and outreach campaigns programmatically, retrieving detailed status, high-fidelity metadata, and performance metrics in real-time
- Lead Execution Intelligence — Programmatically add new contacts and leads to specific campaigns to coordinate your automated dialer and outreach strategy
- Contact Database Management — Access complete directories of leads and contacts assigned to campaigns, retrieving high-fidelity profile metadata and relationship history
- Project & Team Visibility — Access configured CRM projects and associated campaigns to maintain a perfectly coordinated sales pipeline
- Operational Monitoring — Access high-fidelity metadata for account agents and verify API connectivity directly through your agent for instant operational reporting
How it works
1. Subscribe to this server
2. Retrieve your API Key from your Adversus dashboard (Account Settings > API)
3. Start orchestrating your outbound sales pipeline from Claude, Cursor, or any MCP client
No more manual toggling between dialer tabs or digging through complex lead tables. Your AI acts as your dedicated sales operations coordinator and lead architect.
Who is this for?
- Sales Operations Leads — instantly retrieve campaign performance recaps and manage lead distribution using natural language commands
- Telemarketing Managers — coordinate agent assignments and monitor campaign health without leaving your workspace
- Business Developers — automate the ingestion of new leads into specialized outreach campaigns through simple AI queries
Built-in capabilities (7)
Add a new contact to a campaign
Get details for a specific campaign
List team users
List global leads
List contacts in a campaign
List Adversus campaigns
List projects
Why Pydantic AI?
Pydantic AI validates every Adversus tool response against typed schemas, catching data inconsistencies at build time. Connect 7 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 Adversus integration code
- —
Structured output guarantee: Pydantic AI ensures tool results conform to defined schemas, eliminating runtime type errors
- —
Dependency injection system cleanly separates your Adversus connection logic from agent behavior for testable, maintainable code
Adversus in Pydantic AI
Adversus and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Adversus 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 Adversus in Pydantic AI
The Adversus 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 7 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
Adversus for Pydantic AI
Every tool call from Pydantic AI to the Adversus MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my Adversus API Key?
Log in to your account, navigate to Account Settings > API, and generate or copy your unique API Key.
Can I add a contact to a specific campaign via AI?
Yes! The add_contact_to_campaign tool allows your agent to register new leads programmatically by providing the campaign ID and phone number.
How do I check my global leads?
Use the list_active_leads tool to retrieve a comprehensive directory of all contacts across your entire Adversus account.
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 Adversus MCP integration works identically with OpenAI, Anthropic, Google, or any supported provider.
MCPServerHTTP not found
Update: pip install --upgrade pydantic-ai