privi_batch_plan — Privi Agent Survival & Premium MCP Tool
privi_batch_plan
(privi batch plan) is one of 83 tools on the
Privi Agent Survival & Premium
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call privi_batch_plan from your client
- Claude Code Privi Agent Survival & Premium privi_batch_plan run in your project directory
- Claude Desktop Privi Agent Survival & Premium privi_batch_plan ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Privi Agent Survival & Premium privi_batch_plan ~/.cursor/mcp.json
- VS Code Privi Agent Survival & Premium privi_batch_plan .vscode/mcp.json
- Zed Privi Agent Survival & Premium privi_batch_plan ~/.config/zed/settings.json
- Windsurf Privi Agent Survival & Premium privi_batch_plan ~/.codeium/windsurf/mcp_config.json
- Cline Privi Agent Survival & Premium privi_batch_plan ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Privi Agent Survival & Premium privi_batch_plan ~/.gemini/settings.json
- Grok Privi Agent Survival & Premium privi_batch_plan .mcp.json (in your project root)
- ChatGPT Privi Agent Survival & Premium privi_batch_plan Settings → Connectors → Advanced → Developer mode
- Claude.ai Privi Agent Survival & Premium privi_batch_plan Settings → Connectors → Add custom connector
- LangChain Privi Agent Survival & Premium privi_batch_plan pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http privi-agent-survival https://privi-ai-21-gateway.onrender.com/mcpOther tools on this server
- privi_time_now
- privi_nonce_generate
- privi_payload_hash
- privi_receipt_hash
- privi_receipt_verify
- privi_secret_scan
- privi_log_redact
- privi_prompt_risk
- privi_scope_check
- privi_url_safety
- privi_retry_schedule
- privi_backoff_window
- privi_timeout_budget
- privi_circuit_decide
- privi_rate_budget
- privi_uptime_calculate
- privi_slo_budget
- privi_latency_percentiles
- privi_error_classify
- privi_traceparent
- privi_json_canonical
- privi_json_pointer
- privi_json_merge_preview
- privi_csv_profile
- privi_dedupe_records
- privi_token_cost
- privi_quota_remaining
- privi_dependency_order
- privi_tool_schema_check
- privi_idempotency_key
- privi_expiry_window
- privi_pro_manifest_fingerprint
- privi_pro_manifest_diff
- privi_pro_scope_excess
- privi_pro_policy_coverage
- privi_pro_approval_gate
- privi_pro_action_chain_append
- privi_pro_action_chain_verify
- privi_pro_nonce_replay_window
- privi_pro_auth_session_review
- privi_pro_delegation_review
- privi_pro_uptime_slo
- privi_pro_error_budget
- privi_pro_latency_slo
- privi_pro_response_status_mix
- privi_pro_retry_risk
- privi_pro_incident_priority
- privi_pro_deployment_canary
- privi_pro_dependency_availability
- privi_pro_run_health_summary
- privi_pro_circuit_threshold
- privi_pro_dataset_quality
- privi_pro_csv_column_consistency
- privi_pro_json_schema_minimal
- privi_pro_schema_version_diff
- privi_pro_payload_field_audit
- privi_pro_data_freshness
- privi_pro_pii_presence
- privi_pro_retention_schedule
- privi_pro_duplicate_events
- privi_pro_event_order_integrity
- privi_pro_usage_cost_breakdown
- privi_pro_model_cost_estimate
- privi_pro_unit_margin
- privi_pro_pricing_tier_fit
- privi_pro_invoice_reconciliation
- privi_pro_revenue_forecast
- privi_pro_churn_sensitivity
- privi_pro_quota_burn_rate
- privi_pro_stripe_fee_scenario
- privi_pro_usdc_minor_units
- privi_pro_project_priority_matrix
- privi_pro_dependency_dag
- privi_pro_capacity_allocation
- privi_pro_release_readiness
- privi_pro_vendor_risk
- privi_pro_control_evidence_gap
- privi_pro_incident_timeline
- privi_pro_support_sla
- privi_pro_contract_obligations
- privi_pro_buyer_qualification
- privi_pro_procurement_scorecard
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.