Deel

Not to connect, but yes to do anything with your own workforce. We opened an anonymous handshake on 2026-08-17 and the server returned eight tool definitions with no credential. Deel's authorization page confirms that initialize and tools/list are public and that the server challenges only when a client invokes a protected tool. All eight anonymous tools are hiring calculators, not account data.

Because you have not signed in yet. Anthropic's directory snapshot lists 95 tool names, and Deel's own tools reference documents 86 across ten categories, but an unauthenticated client sees only the eight public calculators. The rest sit behind OAuth2 scopes, so they appear after you complete the authorization flow in your MCP client.

Only after you authorize it, and only within the scopes you grant. Nothing in the anonymous surface touches your workforce. Deel's protected resource metadata, which we fetched on 2026-08-17, publishes 81 scopes including payslips:read and people:read, and its authorization page states the server verifies that the access token carries the scope each tool needs.

It can, with write scopes granted. Deel's tools reference documents signContract, createANewContract, amendContract and AddOffCyclePaymentForContract among its 86 tools, and its protected resource metadata publishes 38 write scopes. None of that is reachable anonymously. Grant read scopes only if you want an agent that answers questions rather than one that acts.

Five requests per second, shared across your whole organization. Deel's rate limits page states the ceiling applies per organization rather than per token, uses a rolling one-second window, and returns 429 when exceeded. That page also warns the API returns no rate-limit headers, so a client only discovers the limit by hitting it.

Use a personal access token as a bearer credential. Deel's authorization page directs you to More, then Developer, then Apps in the Deel dashboard, and to select Generate token. You then pass it in an Authorization header in your MCP client configuration. Deel recommends OAuth2 wherever the client supports it, because tokens rotate and scopes stay narrow.

One hour for access tokens and thirty days for refresh tokens. Deel's authorization page states refresh tokens are single-use, so each exchange invalidates the previous one and issues a replacement. Its best practices page adds that failing to store the new refresh token produces invalid_grant errors on the following attempt. Most MCP clients handle this rotation automatically.