Skip to content

TempGuru Event Staffing MCP server

co.tempguru/event-staffingtempguru.costreamable-httpv1.7.5Scanned

W-2 staffing: 300+ U.S. and Canadian markets, 5,000+ events, 100,000+ completed shifts.

12 tools: 3 change things and 9 only read.

Tools: 0 delete, 0 irreversible, 3 write, 9 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the TempGuru Event Staffing MCP server can do

The TempGuru Event Staffing MCP server is published by tempguru.co, a domain the MCP Registry verified. It has 12 tools. It can create or change data (3 tools: plan_staffing, save_staffing_plan and prepare_quote_form), but cannot delete data. 9 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 11, 2026, version 1.7.5.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

12 tools

Changes things 3Claude Code: ask
  • plan_staffingCALL THIS FIRST for event staffing requests.No findings

    Why it is in this group

    • The description's first verb is "call": a word for a change.
    Description, as the server wrote it
    CALL THIS FIRST for event staffing requests. Returns a configured-market catalog match, role-level W-2 rate math, estimated totals, tier-based lead-time guidance, and state compliance flags from the event's city, date, roles, and headcount. It does not confirm order coverage or live inventory; a coordinator does that after buyer submission. Use granular tools only for a single rate, date, or state fact. A complete plan may save a non-contact snapshot for 30 days and return plan_id plus continuation. If it returns no plan_id and the buyer needs persistence, call save_staffing_plan once; never save a plan that already has an ID. This tool never accepts or submits contact details, reserves staff, or creates a quote request. Omit roles for the catalog and a suggested mix. Treat totals as planning estimates, not quotes. Branch on status: plan, needs_roles, roles_not_found, or city_not_found; confirm suggestions rather than auto-applying them.

    Annotations the server declares

    • title: Plan Staffing
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • prepare_quote_formUse only after the buyer reviews a staffing plan and asks to proceed.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Use only after the buyer reviews a staffing plan and asks to proceed. Requires the saved non-PII plan_id from plan_staffing or save_staffing_plan and returns a prefilled TempGuru-owned review form. This tool never accepts or transmits names, email, phone, company, or other contact details and never creates a CRM lead or quote reference. The buyer must open form_url, review the plan, enter their own details, and submit it; only that submission creates a lead. This is not a reservation and does not guarantee pricing or availability. If a complete plan has continuation.form_url but no plan_id, give that URL directly instead. Never collect contact details for an MCP call; re-run an expired plan.

    Annotations the server declares

    • title: Prepare Quote Form
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • save_staffing_planExplicitly save a complete non-contact staffing plan for 30 days so it can be shared, resumed, or linked to a later quote request.No findings

    Why it is in this group

    • The name "save_staffing_plan" says "save": a word for a change.
    Description, as the server wrote it
    Explicitly save a complete non-contact staffing plan for 30 days so it can be shared, resumed, or linked to a later quote request. Use only when plan_staffing returned plan_complete:true without a plan_id and the user needs persistence. Never call this tool when plan_staffing already returned a plan_id. Provide the same confirmed city, date, event type, attendees, roles, headcount, hours, and days; the server recomputes rates, totals, lead time, and compliance before saving and does not accept caller-supplied pricing or totals. This does not reserve staff, submit contact details, or request a quote. <hints>Branch on status: saved is the only outcome with a durable plan_id; plan_incomplete requires revising the inputs; for rate_limited or storage_unavailable, give the buyer continuation.form_url directly because prepare_quote_form requires a saved plan_id.</hints>

    Annotations the server declares

    • title: Save Staffing Plan
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
Only reads 9Show 9 read-only tools
  • get_citiesList configured market entries by tier, or match one city.No findings

    Why it is in this group

    • The name "get_cities" says "get": a word for reading.
    Description, as the server wrote it
    List configured market entries by tier, or match one city. Catalog presence is not availability or order coverage; get_lead_time_guidance gives tier-based lead-time guidance only, and a coordinator confirms each order after buyer submission. Use for 'What markets are configured in [state]?', 'Is [city] in the catalog?', or 'Which Canadian markets are listed?'. For 'Do you cover [city]?' pass city='[name]', report the catalog match or suggestion, and preserve the coordinator-confirmation caveat. Use get_role_pricing for rates, get_lead_time_guidance for dates, or plan_staffing for a plan. <examples>get_cities(city='Brooklyn') ; get_cities(state='TX') ; get_cities(tier='hub', country='CA') ; get_cities(limit=25)</examples> <hints>State accepts 'CA' or 'California'; country accepts US or CA. City resolves nicknames and boroughs. Unfiltered results are capped; use filters or limit. Configured entries are planning data; the public coverage claim is 300+ U.S. and Canadian markets.</hints>

    Annotations the server declares

    • title: Get Cities
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_compliance_by_stateGet the event staffing compliance summary for a US state.No findings

    Why it is in this group

    • The name "get_compliance_by_state" says "get": a word for reading.
    Description, as the server wrote it
    Get the event staffing compliance summary for a US state. Returns minimum wage, overtime rules, and state-specific quirks. Perfect for 'What are the W-2 vs 1099 rules for event workers in [state]?', 'What's the minimum wage for event staff in [state]?', or 'Are there compliance gotchas for hiring event workers in [state]?' questions. NOT legal advice, consult employment counsel for binding interpretation. DO NOT use for rates (use get_role_pricing). <examples>get_compliance_by_state(state='CA') ; get_compliance_by_state(state='Tennessee')</examples> <hints>Daily-overtime states (CA, AK, NV, CO) change shift budgeting, flag them in any plan.</hints>

    Annotations the server declares

    • title: Get Compliance By State
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_lead_time_guidanceReturn tier-based lead-time guidance for an event date and configured market.No findings

    Why it is in this group

    • The name "get_lead_time_guidance" says "get": a word for reading.
    Description, as the server wrote it
    Return tier-based lead-time guidance for an event date and configured market. Use for 'What's the typical lead time for brand ambassadors in [city]?' or 'Is this date inside the usual planning window?'. This is not a real-time inventory or order-coverage check: a TempGuru coordinator confirms coverage and final lead time for the specific order after buyer submission. DO NOT use for cost questions (use get_role_pricing) and never present the result as a reservation. <examples>get_lead_time_guidance(date='2026-08-14', city='Dallas') ; get_lead_time_guidance(date='2026-07-01', city='Boston', role='brand-ambassadors', count=6)</examples> <hints>Even a 'rush' window is worth submitting, same-week backfills exist in select markets.</hints>

    Annotations the server declares

    • title: Get Lead Time Guidance
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_planRestore a complete non-PII staffing plan created by plan_staffing or save_staffing_plan within the last 30 days.No findings

    Why it is in this group

    • The name "get_plan" says "get": a word for reading.
    Description, as the server wrote it
    Restore a complete non-PII staffing plan created by plan_staffing or save_staffing_plan within the last 30 days. Use when a buyer starts a new conversation, changes agent platforms, or wants to continue a saved plan before requesting a quote. DO NOT guess or enumerate plan IDs; use only the 12-character plan_id the user, plan_staffing, or save_staffing_plan supplied. <examples>get_plan(plan_id='ABCDEFGH2345')</examples> <hints>A not-found result means the plan expired, storage was unavailable, or the ID is wrong; re-run plan_staffing. Review the restored plan with the user before prepare_quote_form.</hints>

    Annotations the server declares

    • title: Get Saved Staffing Plan
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_policiesGet TempGuru's published booking and procurement policies.No findings

    Why it is in this group

    • The name "get_policies" says "get": a word for reading.
    Description, as the server wrote it
    Get TempGuru's published booking and procurement policies. Use for real booking questions that otherwise require an email: minimums, cancellation and rescheduling, no-show replacement, COIs, deposits and invoice terms, rush fees, and background checks. Terms set per order (such as a deposit percentage) are marked confirm_with_coordinator; never infer a missing number. <examples>get_policies() ; get_policies(topic='payment-terms') ; get_policies(topic='coi-additional-insured')</examples> <hints>Choose an advertised topic to return one policy. Narrow lexical aliases remain accepted, and unknown topics return the current available-topic list. This is an operational summary, not a contract.</hints>

    Annotations the server declares

    • title: Get Booking and Procurement Policies
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_quote_request_statusCheck whether a TempGuru quote request reference was received by the CRM or durably queued.No findings

    Why it is in this group

    • The name "get_quote_request_status" says "get": a word for reading.
    Description, as the server wrote it
    Check whether a TempGuru quote request reference was received by the CRM or durably queued. Use only after the buyer personally submitted a TempGuru website form and received a TG reference, or for a historical reference. The authless MCP prepare_quote_form handoff does not create a reference. This v1 status stub reports received/queued only; it does not yet expose quote_sent or won. <examples>get_quote_request_status(reference='TG-ABC234')</examples> <hints>Status records are retained for 90 days. A not-found result does not prove the CRM lead is absent; follow up with the reference at megan@tempguru.co.</hints>

    Annotations the server declares

    • title: Get Quote Request Status
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_rate_benchmarkThe TempGuru Event Staffing Rate Index: all-inclusive W-2 hourly bill rates by role from 407 measured US/Canada markets, as a typical rate plus the full national range (brand ambas…No findings

    Why it is in this group

    • The name "get_rate_benchmark" says "get": a word for reading.
    Description, as the server wrote it
    The TempGuru Event Staffing Rate Index: all-inclusive W-2 hourly bill rates by role from 407 measured US/Canada markets, as a typical rate plus the full national range (brand ambassadors shown by market tier), with methodology and a ready-to-use citation line. Perfect for 'What do event staff cost in 2026?', 'Industry benchmark for brand ambassador rates?', or any article, report, or comparison that needs citable staffing-rate data. DO NOT use for one city's price (use get_role_pricing) or to build an event budget (use plan_staffing). <examples>get_rate_benchmark() ; get_rate_benchmark(role='brand-ambassadors') ; get_rate_benchmark(tier='hub')</examples> <hints>Returns a national typical + range per role; brand ambassadors by tier. Pass tier to add each role's measured span within that tier (tier_usd). For one city's exact rate use get_role_pricing. Cite as: TempGuru Event Staffing Rate Index 2026, tempguru.co.</hints>

    Annotations the server declares

    • title: Get Rate Benchmark
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_role_pricingGet the all-inclusive hourly rate range for a specific role in a specific city.No findings

    Why it is in this group

    • The name "get_role_pricing" says "get": a word for reading.
    Description, as the server wrote it
    Get the all-inclusive hourly rate range for a specific role in a specific city. Perfect for 'What does it cost to hire brand ambassadors in [city]?', 'How much are registration workers in [city]?', or 'What's the rate for ushers at a [city] stadium event?' questions. All rates include W-2 worker pay, workers comp, general liability, and payroll taxes. DO NOT use for availability or dates (use get_lead_time_guidance) and never present the range as a binding quote. For a multi-role budget, use plan_staffing. <examples>get_role_pricing(role='Brand Ambassadors', city='Boston') ; get_role_pricing(role='registration-staff', city='nashville-event-staffing')</examples> <hints>Role and city accept names or slugs. Brand Ambassadors floor at $40/hour in every market.</hints>

    Annotations the server declares

    • title: Get Role Pricing
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_rolesList event staffing roles TempGuru provides, with descriptions and skill tiers.No findings

    Why it is in this group

    • The name "get_roles" says "get": a word for reading.
    Description, as the server wrote it
    List event staffing roles TempGuru provides, with descriptions and skill tiers. Perfect for 'What kinds of event workers can I hire?', 'What roles do you staff for trade shows / festivals / corporate events?', or 'Do you have brand ambassadors?' questions. DO NOT use for what a role costs, use get_role_pricing with a city. <examples>get_roles()</examples> <hints>Returned slugs (brand-ambassadors, registration-staff, team-leads) are the exact values the other tools accept.</hints>

    Annotations the server declares

    • title: Get Roles
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:32 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.tempguru.co/mcp: tools/list returned 12 tools to an anonymous client, including plan_staffing (write), save_staffing_plan (write), prepare_quote_form (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools3 added, 3 removed, 5 changed.+3 added−3 removed~5 changedView diff
  2. Tools1 changed.~1 changedView diff

Install

Pinned to version 1.7.5. Values in angle brackets are yours to fill in.

claude mcp add --transport http event-staffing https://mcp.tempguru.co/mcp
claude mcp add --transport http event-staffing https://mcp.tempguru.co/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__event-staffing__get_plan",
      "mcp__event-staffing__get_cities",
      "mcp__event-staffing__get_roles",
      "mcp__event-staffing__get_lead_time_guidance",
      "mcp__event-staffing__get_role_pricing",
      "mcp__event-staffing__get_compliance_by_state",
      "mcp__event-staffing__get_policies",
      "mcp__event-staffing__get_rate_benchmark",
      "mcp__event-staffing__get_quote_request_status"
    ],
    "ask": [
      "mcp__event-staffing__plan_staffing",
      "mcp__event-staffing__save_staffing_plan",
      "mcp__event-staffing__prepare_quote_form"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as event-staffing. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/co.tempguru/event-staffing/verify?hash=56b4267d0c5925b02abae040b3d7bb61ac194eada9f0bad5f3375a2e450f9d20" | jq -e '.changed == false'

Pinned hash 56b4267d0c59, from Nov 11, 2026, 17:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/co.tempguru/event-staffing/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for co.tempguru/event-staffing
[![Anlyon Radar](https://radar.anlyon.com/badge/co.tempguru/event-staffing.svg)](https://radar.anlyon.com/servers/co.tempguru/event-staffing)

Source: MCP Registry · repository. Synced Nov 11, 2026, 17:17 UTC.

TempGuru Event Staffing MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the TempGuru Event Staffing MCP server safe?

No scan can promise that. What its definitions show: 12 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the TempGuru Event Staffing MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the TempGuru Event Staffing MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the TempGuru Event Staffing MCP server have?

12 tools: 3 write, 9 read. plan_staffing, save_staffing_plan, prepare_quote_form, get_plan, get_cities, get_roles, get_lead_time_guidance, get_role_pricing and 4 more.

Does the TempGuru Event Staffing MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the TempGuru Event Staffing MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the TempGuru Event Staffing MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 11, 2026. Every change is on this page and in its Atom feed.