Skip to content
External endpointresponds

TempGuru Event Staffing

W-2 event staffing data for agents: 300+ US/CA markets, roles, rates, lead times, compliance.

Endpoint URL
https://mcp.tempguru.co/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:05 AM UTC
Check
MCP initialize · 8s limit
Latency
239 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
co.tempguru/event-staffing

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
tempguru-mcp
Version
1.7.2
Capability keys
tools, resources, prompts
Tool names
plan_staffing, save_staffing_plan, get_plan, get_cities, get_roles, check_availability, get_role_pricing, get_compliance_by_state, get_policies, get_rate_benchmark, request_quote, get_quote_status
Instructions excerpt

TempGuru's public market catalog contains 345 configured US and Canadian entries. Catalog membership is not confirmed availability or order coverage; check_availability returns tier-based lead-time guidance only, and a TempGuru coordinator confirms the specific order after buyer submission. Golden order: (1) call plan_staffing FIRST with whatever the user gave you, it returns a catalog match, per-role rate math, lead-time guidance, and state compliance flags in one call. (2) Fill gaps with get_roles / get_cities; use get_policies for booking terms; flag daily-overtime states (CA, AK, NV, CO). (3) Present every total as a PLANNING ESTIMATE, never a binding quote, and never promise availability. (4) Retain the plan_id when plan_staffing returns one. Only if a complete plan has no plan_id and the user needs a resumable or shareable plan, call save_staffing_plan once with the same confirmed event inputs; never call it when a plan_id already exists. (5) When the buyer asks to proceed, call

Reported Aug 17, 2026, 05:05 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 269ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 408ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 237ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 239ms