sickslip-verify
Verify the authenticity of a SickSlip doctor's note from your AI assistant. SickSlip is a U.S. asynchronous telehealth service operated by SickSlip P.A., reviewed and signed by Dr. Adam Z. Kawalek, MD (NPI 1326223306, board-certified internal medicine, 30+ states). Every note is QR-verifiable by the recipient employer. This MCP server exposes one tool — `verify_sickslip_note(code)` — that any MCP-compliant client can call to verify a SickSlip note's authenticity. Returns the issued date, absence window, state of physician licensure, and physician name + NPI. No PHI is exposed (no patient name, DOB, or condition). **Use cases:** - HR person verifying an employee's note from Claude Desktop - Manager confirming a sick-leave document mid-conversation - Patient confirming their own note is registered + valid - Employment attorneys researching workplace dispute facts **Links:** - SickSlip: https://www.sickslip.co - Physician bio + NPI: https://www.sickslip.co/about/dr-adam-kawalek - npm
No outside reports on file
sickslip-verify links no public source repository on GitHub, npm, or PyPI; verify its origin and permissions before installing.
Based on public adoption and transparency signals as of Oct 22, 2026. Our opinion, not a code audit or security guarantee.
What it can access
- Local filesNo local folder access notedLOW
- Command executionNo shell command runner notedLOW
- Network reachLocal or standard API callsLOW
- CredentialsNo API token requiredLOW
- Package sourceSource repository onlyPUBLIC
Inferred from this listing’s public package details and description. Check the project’s source before installing.
Install
We hold no install steps for this listing. Follow the project’s own instructions.
About Sickslip Verify
Sickslip Verify is an MCP server focused on Developer tools and Web & browsing: Verify the authenticity of a SickSlip doctor's note from your AI assistant. SickSlip is a U.S. asynchronous telehealth service operated by SickSlip P.A., reviewed and signed by Dr. Adam Z. Kawalek, MD (NPI 1326223306, board-certified internal medicine, 30+ states). Every note is QR-verifiable by the recipient employer. This MCP server exposes one tool — verify_sickslip_note(code) — that any MCP-compliant client can call to verify a SickSlip note's authenticity. Returns the issued date, absence window, state of physician licensure, and physician name + NPI. No PHI is exposed (no patient name, DOB, or condition). Use cases: - HR person verifying an employee's note from Claude Desktop - Manager confirming a sick-leave document mid-conversation - Patient confirming their own note is registered + valid - Employment attorneys researching workplace dispute facts Links: - SickSlip: https://www.sickslip.co (opens external site) - Physician bio + NPI: https://www.sickslip.co/about/dr-adam-kawalek (opens external site) - npm.
No standalone npm or PyPI registry package is linked on file; review the project links before installing. Based on its public metadata, it operates with standard local or API scope without broad shell execution flags noted.
Setup
We hold no install steps for Sickslip Verify. Follow the project’s own instructions.
Why this grade
Signal-based grade (0/7 points): no public source code found. This reflects adoption and transparency, not a code review.
Popularity and upkeep
- Listing last refreshed
- 2026-10-22
These are public popularity signals, not a maintenance check. Look at the repository’s commit history and open issues.
Security reports
We could not reach our research just now, so this list may be incomplete. Try again later.
Risks to watch for
- Unlinked source code repository: No public GitHub repository or registry package is linked on file. Verify the publisher identity and inspect the code before running it locally.
How to lower the risk
Least-privilege permissions
- Give it access only to the specific folders, accounts or projects it needs, never your whole drive or admin account.
- Use a separate, limited API key or login just for this tool so you can switch it off without affecting anything else.
Network isolation
- Run it on a work computer or sandbox account, not one holding personal or company-sensitive data.
- If your IT team can, limit which websites and services it is allowed to contact.
Monitoring
- Check its activity history or logs weekly at first, and look at what it changed or sent.
- Turn on alerts for new logins or unusual usage on any account it connects to.
Red flags to watch for
- It asks for more access than its job requires, or prompts you to paste passwords.
- It suddenly updates with new owners, or starts contacting unfamiliar websites.
Questions
How do I install Sickslip Verify?
No standalone npm or PyPI package is listed for Sickslip Verify. Use the project links in the Key facts section on this page for installation steps.
Are there security reports about Sickslip Verify?
No reports found for this package in our research. Sickslip Verify currently holds Grade F (Many risk signals) based on public adoption and transparency signals. Review the permissions and source repository before granting access to local files, shell commands, or API keys.
Is Sickslip Verify actively maintained?
We do not have star or download counts on file for Sickslip Verify yet (listing refreshed 2026-10-22). Check the commit history and open issues before relying on it.
What are alternatives to Sickslip Verify?
Compare Sickslip Verify side by side with similar MCP servers in the Related tools section on this page, or browse all MCP servers on AgentArmorHQ.
Key facts
- Type
- App connector
- Est. context load
- ~1.2k tokens / turn (~5 tool schemas, 0.57% of 200k context)
- Last updated
- 2026-10-22
- Last graded
- 2026-10-22
Community
Discussions for Sickslip Verify
Ask questions or share configuration tips. Governed by our Community Rules & Terms.
No posts match this filter yet.
Be the first to ask a question or share a working tip.
Check before you install, in Claude
Your assistant answers Block, Review or No known issues for any package before it installs it.
Get this check inside Claude