xpay tools logo
  • Tools
  • Collections
  • Skills
  • Docs
  • xpay.sh
  1. Home
  2. ›
  3. Mcps
  4. ›
  5. Check Pvs

Mcps
Mcps
Tool

Check Pvs

check_pvs

Check PVS (Potentially Visible Set) visibility between two world positions in a BSP map.

How it works ↓

Pricing

Per call

$0.02

Model

time-based


Pay only for what you use. No subscriptions.
Inputs

z1 *

number

y1 *

number

z2 *

number

x1 *

number

y2 *

number

x2 *

number

map *

string
Try It
API
MCP Config
Input Parameters
z1 *
Z coordinate of the first point
y1 *
Y coordinate of the first point
z2 *
Z coordinate of the second point
x1 *
X coordinate of the first point
y2 *
Y coordinate of the second point
x2 *
X coordinate of the second point
map *
Map name (e.g. 'campgrounds') or path to a .bsp file. A bare name or 'maps/<name>.bsp' is searched inside pk3 archives under WOLFCAMQL_BASEPATH. An absolute path or a path relative to MAP_DIR is read directly.
Cost per run
Execution cost
$0.02
Deducted from your xPay allowance
About Check Pvs

Check PVS (Potentially Visible Set) visibility between two world positions in a BSP map. Returns whether the BSP considers the two points mutually visible — i.e. whether the engine would have sent entity updates between them. Also returns the PVS cluster indices for both points. PVS is a conservative over-approximation: visible=true means updates were sent, not guaranteed line-of-sight. Accepts a bare map name, 'maps/.bsp', or a direct path — see get_bsp_info for lookup rules.

Frequently Asked Questions

Check PVS (Potentially Visible Set) visibility between two world positions in a BSP map. Returns whether the BSP considers the two points mutually visible — i.e. whether the engine would have sent entity updates between them. Also returns the PVS cluster indices for both points. PVS is a conservative over-approximation: visible=true means updates were sent, not guaranteed line-of-sight. Accepts a bare map name, 'maps/<name>.bsp', or a direct path — see get_bsp_info for lookup rules.

Check Pvs costs $0.02 per call on xpay. No subscription, no minimums. Pay only for the calls you make. New accounts get $5 in free credits.

Connect the Mcps MCP endpoint to your client — Claude Code: claude mcp add --transport http quakelive "https://quakelive.mcp.xpay.sh/mcp?key=YOUR_XPAY_KEY"; Cursor/Windsurf/Cline/VS Code: same URL in mcp.json. The agent will see check_pvs as a callable tool with the input schema and run it directly. (Unified across all providers: https://mcp.xpay.sh/mcp?key=YOUR_XPAY_KEY, then xpay_run with toolPath quakelive/check_pvs.)

Yes — that's exactly what xpay is for. You don't need a Mcps account or API key. Sign up at xpay.tools (Google or email), get $5 free credit, and run Check Pvs immediately. Billing flows through your xpay balance.

Check Pvs accepts 7 input parameters: z1, y1, z2, x1, y2, x2…. See the input schema and runnable form on this page for details and to test live.

xpay tools logo

Marketplace for AI Capabilities. Run agents, tools & prompts with pay-per-use micropayments.

or ask your AI app
Popular Tools
FirecrawlTavilyExaHunterPerplexityRecraftIdeogramFlux
Collections
AI Image & MediaContent & ResearchDev ToolsFinanceLead GenWeb ScrapingCompetitive Intel
Developers
DocumentationAPI ReferenceQuickstartSDKsSkillsskill.mdllms.txt
Resources
The Agentic EconomyAgentic CommerceAgent Frameworksx402 ProtocolBlog
Company
About xpayxpay.shGitHubDiscordTwitter / X

© 2026 Agentically Inc. All rights reserved.
Privacy PolicyTerms of Service
✦
xpay Assistant
Check Pvs by Quakelive

Ask me about tools, pricing, or how to connect

How does this tool work?
What parameters does it accept?
Show me a usage example
DocsCollectionsExplore