Home / MCP registry index / io.usefulapi/papershift

Papershift MCP by usefulapi

io.usefulapi/papershift in the official MCP registry. Endpoint https://papershift.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.

The registry describes it as: Read Papershift absences, vacation, time tracking and shifts; request and review absences.

We read its 26 tools on 2026-10-31. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http papershift https://papershift.usefulapi.io/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "papershift": {
      "url": "https://papershift.usefulapi.io/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"papershift","type":"http","url":"https://papershift.usefulapi.io/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

papershift_get_account papershift_list_locations papershift_get_location papershift_list_working_areas papershift_list_users papershift_get_user papershift_list_tags papershift_list_absence_types papershift_list_absences papershift_get_absence papershift_list_vacation_entitlements papershift_list_time_trackings papershift_get_time_tracking papershift_list_evaluations papershift_list_target_hours papershift_list_payrolls papershift_list_shifts papershift_get_shift papershift_list_shift_assignments papershift_list_availabilities papershift_create_absence papershift_review_absence papershift_create_time_tracking papershift_confirm_time_tracking papershift_create_shift papershift_assign_user_to_shift

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-10-31): b52be43c57aebda2. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-usefulapi-papershift/badge.svg)](https://lazaretto.dev/mcp-registry/io-usefulapi-papershift)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.