outcome_privacy_request — LLPRO Campus MCP Tool
outcome_privacy_request
(outcome privacy request) is one of 61 tools on the
LLPRO Campus
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call outcome_privacy_request from your client
- Claude Code LLPRO Campus outcome_privacy_request run in your project directory
- Claude Desktop LLPRO Campus outcome_privacy_request ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor LLPRO Campus outcome_privacy_request ~/.cursor/mcp.json
- VS Code LLPRO Campus outcome_privacy_request .vscode/mcp.json
- Zed LLPRO Campus outcome_privacy_request ~/.config/zed/settings.json
- Windsurf LLPRO Campus outcome_privacy_request ~/.codeium/windsurf/mcp_config.json
- Cline LLPRO Campus outcome_privacy_request ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI LLPRO Campus outcome_privacy_request ~/.gemini/settings.json
- Grok LLPRO Campus outcome_privacy_request .mcp.json (in your project root)
- ChatGPT LLPRO Campus outcome_privacy_request Settings → Connectors → Advanced → Developer mode
- Claude.ai LLPRO Campus outcome_privacy_request Settings → Connectors → Add custom connector
- LangChain LLPRO Campus outcome_privacy_request pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http campus https://llpro.ai/mcp?via=mcp-registryOther tools on this server
- ground_truth_ask
- ground_truth_sources
- countersign_stamp
- countersign_verify
- countersign_log
- agentrecord_lookup
- agentrecord_search
- agentrecord_submit_receipt
- agentrecord_identity
- agentrecord_census
- agentrecord_nominate
- launchpad_start
- launchpad_progress
- feedback_submit
- page_watch_check
- agent_ready_check
- agent_card_check
- page_to_text
- feed_read
- list_clean
- sitemap_read
- transaction_audit
- spend_limit_check
- witness_record
- handoff_record
- run_record_verify
- underpayment_audit_compare
- hub_route
- hub_directory
- card_skimmer_and_pos_tamper_checks
- outcome_status
- outcome_revocations
- outcome_dispute
- outcome_appeal
- outcome_case
- lpa_and_subscription_agreement
- capital_call_collection_chasing
- agent_identity_check
- domain_health_check
- email_address_check
- website_tech_lookup
- photo_background_remove
- qr_code_make
- page_search_ready
- invoice_make
- pdf_kit
- vat_number_check
- local_business_find
- resume_job_match
- page_snapshot_signed
- certified_lookup
- chemical_trade_credit_payment_days
- card_dispute_outcome_table_win
- dispute_record
- agency_side_certificate_request
- attribution_record
- attribution_statement
- waterfall_and_distribution
- double_brokering_and_identity
- payer_re_credentialing_and_caqh
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.