Workday
NPM · @MINDSTONE/MCP-SERVER-WORKDAY · SCANNED AUG 7
Workday HCM MCP server for Model Context Protocol hosts — workers, profiles, organizations
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Known CVEs were checked across the 95 of 99 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Dependency health was assessed across the 95 of 99 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (FSL-1.1-MIT) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 80 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 866 tokens (~216/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @mindstone/mcp-server-workday
claude mcp add mindstone-mcp-server-workday -- npx -y @mindstone/mcp-server-workday
codex mcp add mindstone-mcp-server-workday -- npx -y @mindstone/mcp-server-workday
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mindstone-mcp-server-workday": {
"type": "local",
"command": [
"npx",
"-y",
"@mindstone/mcp-server-workday"
],
"enabled": true
}
}
} openclaw mcp add mindstone-mcp-server-workday --command npx --arg -y --arg @mindstone/mcp-server-workday
mcp_servers:
mindstone-mcp-server-workday:
command: "npx"
args: ["-y", "@mindstone/mcp-server-workday"] {
"mcpServers": {
"mindstone-mcp-server-workday": {
"command": "npx",
"args": [
"-y",
"@mindstone/mcp-server-workday"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 7 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Aug 26 +3
- Stability: unverified → 0.23 ▲ functional
- 2 Aug 26 +56
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- License: unverified → fail ▼ functional
- Schema quality: unverified → excellent ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Licence: FSL-1.1-MIT functional
- 1 Aug 26 −13
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 31 Jul 26 −7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 27 Jul 26 43
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 7 Aug 2026 · Analysed npm/@mindstone/[email protected]
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Deprecated | 95 |
| Stale | 29 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
configure_workday_credentials ~333
Configure Workday API credentials. Call this when the user provides their Workday OAuth credentials. SETUP PREREQUISITES: 1. A Workday Integration System User (ISU) with appropriate security group access 2. An API Client registered in Workday (Tenant Setup > API Clients) 3. The Client ID and Client Secret from the API Client registration 4. Optionally, a pre-generated Refresh Token (from OAuth token exchange) PARAMETERS: - host: Workday API domain (e.g., "wd5-impl-services1.workday.com") - tenant: Your Workday tenant name (e.g., "acme_corp") - client_id: OAuth Client ID from API Client registration - client_secret: OAuth Client Secret - refresh_token: (Optional) Pre-generated refresh token. If omitted, uses client_credentials grant. COMMON MISTAKES: - Host should be just the domain (e.g., "wd5-impl-services1.workday.com"), not a full URL - Tenant name is case-sensitive - The ISU must have permissions for the REST API resources you want to access
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | string | yes | OAuth Client ID from Workday API Client registration |
| client_secret | string | yes | OAuth Client Secret |
| host | string | yes | Workday API domain (e.g., "wd5-impl-services1.workday.com") |
| refresh_token | string | – | Optional refresh token. If omitted, client_credentials grant is used. |
| tenant | string | yes | Workday tenant name (e.g., "acme_corp") |
No output schema declared.
No examples provided.
get_workday_worker ~154
Get a worker's full profile by ID from Workday. Returns detailed profile: name, email, title, manager status, location, supervisory organization, years of service. Example: { "worker_id": "3aa5550b7fe348b98d7b5741afc65534" } WORKFLOW - To find a worker: 1. Call list_workday_workers to search by name or email 2. Use the worker's id from the results here RELATED TOOLS: - list_workday_workers: Search/browse workers to find IDs - list_workday_organizations: See org structure
| Name | Type | Req | Description |
|---|---|---|---|
| worker_id | string | yes | Worker ID (from list_workday_workers) |
No output schema declared.
No examples provided.
list_workday_organizations ~155
List organizations (departments, supervisory orgs, cost centers, etc.) in Workday. Returns: ID, name/descriptor, type, active status. Example: {} Example: { "limit": 25, "offset": 50 } Pagination: Returns up to 'limit' results (default 50, max 100). Use 'offset' for next page. RELATED TOOLS: - list_workday_workers: Browse workers in the organization - get_workday_worker: See which organization a worker belongs to
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results per page (default 50, max 100) |
| offset | number | – | Number of results to skip (for pagination, default 0) |
No output schema declared.
No examples provided.
list_workday_workers ~224
List or search workers (employees and contingent workers) in Workday. Returns compact worker summaries: ID, name, email, title, manager status. Example: {} Example: { "search": "Jane Smith" } Example: { "limit": 20, "offset": 100 } Pagination: Returns up to 'limit' results (default 50, max 100). Use 'offset' for next page. RELATED TOOLS: - get_workday_worker: Pass a worker's id to get their full profile - list_workday_organizations: Browse organizational structure COMMON MISTAKES: - search is a free-text filter (name, email, etc.) — not a Workday query language - Maximum limit is 100 per request; use offset for pagination
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results per page (default 50, max 100) |
| offset | number | – | Number of results to skip (for pagination, default 0) |
| search | string | – | Free-text search filter (name, email, etc.) |
No output schema declared.
No examples provided.