MCP.Market

WORKFORCE Dental Staffing MCP server

online · 100% uptime
by workforcedentalstaffing.com·com.workforcedentalstaffing/workforce·v1.0.0

WORKFORCE: dental candidates broadcast availability and commute distance; offices book around it.

A97/100grade A
What users say
No reviews yet
Be the first
Safety scan
A97/100

full report

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed WORKFORCE Dental Staffing yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

WORKFORCE Dental Staffing tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.10 · 2026-10-16 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 331ms (auth required)20/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityOAuth resource metadata advertised on 40115/15
  • Maintenancelast push 9 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; website matches verified namespace8/10
Overall 97/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How WORKFORCE Dental Staffing compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
97/100
higher than 98% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
549 ms
faster than 26% of 30,031 servers

Install WORKFORCE Dental Staffing in Claude Code, Cursor or VS Code

claude mcp add --transport http workforce https://app.workforcedentalstaffing.com/api/agent/mcp
Add to Cursor

What the publisher says

From the WORKFORCE Dental Staffing repository's README, as published. We do not edit it. Read it on GitHub

WORKFORCE Dental Staffing plugin

Dental temp staffing for the US and Canada, inside your AI agent.

Candidates (Registered Hygienists, Dental Assistants, Front Office Staff / Reception, Associate Dentists, and EFDAs) broadcast the days they're available and their commute radius (kilometres in Canada, miles in the US). Dental offices see them on the availability map and book shifts around that availability. Both sides can also sign up, manage their profiles, and handle shifts, applications, and timesheets in chat.

This plugin bundles:

  • the WORKFORCE Dental Staffing MCP server (remote, OAuth sign-in), and
  • sign-up skills that guide an agent through candidate and office onboarding.

Install

  1. Install WORKFORCE Dental Staffing from the Cursor Marketplace (Customize → Plugins), or copy this repository into ~/.cursor/plugins/local/workforce-dental-staffing and reload the window.
  2. Open Customize and check that the workforce-dental-staffing MCP server and the three skills appear.

Connect (OAuth sign-in)

The MCP server is https://app.workforcedentalstaffing.com/api/agent/mcp. No API keys or variables are needed.

  1. Enable the workforce-dental-staffing MCP server. Your client opens the WORKFORCE sign-in page.
  2. Sign in with your WORKFORCE candidate or office account (Google, Apple, or a 6-digit email code) and approve access. If you don't have an account yet, you can create one there.
  3. Ask your agent to "sign me up for WORKFORCE", or start with a task such as "broadcast that I'm free next Tuesday and Thursday within 25 km".

Each sign-in is for one account. A candidate account gets candidate tools and an office account gets office tools. The agent can only see and change the signed-in account's own data. To switch accounts, disconnect and sign in again.

Skills

Tools at a glance

Candidates

  • Setup and profile: setup checklist, profile schema, create or update the profile, profile status, document uploads (photo, resume, licence, certificates), and a bio drafted from the resume.
  • Availability: commute radius, weekly availability, specific dates, open or unavailable status, and broadcast availability to offices (preview, confirm, status, stop).
  • Shifts: search open shifts, job details, apply, track or withdraw applications, booked shifts, confirm a shift, a link to cancel a booked shift in the app, and timesheets.

Offices

  • Setup: office profile schema and readiness, create or update the office, website prefill, phone verification, plans, and the rate agreement.
  • Booking: search the availability map, post, copy, update, and cancel temp shifts, held pay rates, review and accept or decline applicants, and permanent job requests.
  • Operations: timesheets (approve or dispute), the office dashboard, and multiple locations.

Actions that change something use a preview first (confirm: false), and the agent should ask before committing. Full tool documentation:

What stays in the WORKFORCE app

ID verification, payment and banking details, and account deletion are finished in the WORKFORCE app at , never in chat. Offices never see candidates' payment details.

Privacy, terms, and support

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

WORKFORCE Dental Staffing: common questions

Is WORKFORCE Dental Staffing MCP server safe?
Yes, by our scan: it is graded A (97/100). Read the WORKFORCE Dental Staffing safety report
How do I install WORKFORCE Dental Staffing?
It runs remotely at app.workforcedentalstaffing.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does WORKFORCE Dental Staffing need an API key?
No key to paste: it signs you in with OAuth when your client connects.
Is WORKFORCE Dental Staffing maintained?
The last commit was 28 days ago (2026-10-07). The latest release is v1.0.0.
Is WORKFORCE Dental Staffing up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does WORKFORCE Dental Staffing compare with other MCP servers?
safety score 97/100 (higher than 98% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 549 ms (faster than 26% of 30,031 servers). Full comparison.