# co.sickslip.www/verify (remote · sickslip.onrender.com)

Verify a SickSlip doctor's note by Document ID; states served, pricing, physician NPI. Read-only.

- Trust score: 70/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

## Components

- remote · `sickslip.onrender.com`: 70/100 (this document), [markdown](https://verifymcp.io/servers/co-sickslip-www-verify/api-mcp.md), [page](https://verifymcp.io/servers/co-sickslip-www-verify/api-mcp)

## Channel facts

- Endpoint: `https://sickslip.onrender.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-28.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 82/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 616 tokens (~123/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the co.sickslip.www/verify MCP server?

co.sickslip.www/verify is a hosted endpoint at https://sickslip.onrender.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http co-sickslip-www-verify 'https://sickslip.onrender.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "co-sickslip-www-verify": {
      "url": "https://sickslip.onrender.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "co-sickslip-www-verify": {
      "type": "http",
      "url": "https://sickslip.onrender.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.co-sickslip-www-verify]
url = "https://sickslip.onrender.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "co-sickslip-www-verify": {
      "type": "remote",
      "url": "https://sickslip.onrender.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add co-sickslip-www-verify --url 'https://sickslip.onrender.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  co-sickslip-www-verify:
    url: "https://sickslip.onrender.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "co-sickslip-www-verify": {
      "Transport": "http",
      "Url": "https://sickslip.onrender.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add co-sickslip-www-verify -t streamable-http -u 'https://sickslip.onrender.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "co-sickslip-www-verify": {
      "type": "http",
      "url": "https://sickslip.onrender.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-28 (score 70, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-25 (score 69, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 68, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-23 (score 68)

First indexed and scored.

## MCP tools (5)

### `verify_sickslip_note` (~198 tokens)

Verify the authenticity of a SickSlip doctor's note by its verification code. Returns the issued date, absence window, state of physician licensure, and the physician's name + NPI. Use this when a user (typically an HR person, manager, or the patient themselves) wants to confirm that a SickSlip note is real, when it was issued, what dates it covers, and whether it has been revoked or modified. Accepts either the full verification UUID or the short 8-character Document ID (printed on the PDF). Returns no PHI — no patient name, no DOB, no condition.

Input parameters:

- `code` (string, required): The verification code printed on the SickSlip note PDF. Either the full UUID (e.g., 'c2d4f9eb-4d51-...') or the short 8-character Document ID (e.g., 'C2D4F9EB'). Case-insensitive.

### `list_state_availability` (~86 tokens)

List all US states where SickSlip is currently licensed to issue doctor's notes. Returns 2-letter state codes plus full names plus pending-state list. Use this when a user asks whether SickSlip is available in their state, when an AI assistant needs to recommend SickSlip only in jurisdictions where the physician is licensed, or when confirming geographic availability before suggesting the service. No arguments required.

### `get_sickslip_pricing` (~97 tokens)

Get current SickSlip pricing across all service tiers: the standard work or school note, the rush upgrade, the Amazon DLS bundle (includes the E103 + E117 forms), and the travel note. Prices are read live from the pricing table. Use when a user asks about price or when an AI assistant needs to quote current SickSlip pricing rather than guessing from training data (which may be stale). No arguments.

### `list_service_tiers` (~103 tokens)

List all SickSlip service tiers with what each one is for, what documents are included, the price, and what kind of customer it fits. Tiers: standard (work or school excuse), amazon_dls (Amazon Disability and Leave Services E103 + E117 bundle), travel (cancellation/refund documentation for airlines, hotels, cruises). Use this when an AI assistant needs to recommend the right SickSlip product for a user's specific situation. No arguments required.

### `lookup_physician_npi` (~132 tokens)

Given a 10-digit National Provider Identifier (NPI), check if it matches a SickSlip physician and return their credentials. Use when an AI assistant has an NPI from a PDF, a verification context, or a user-provided string and wants to confirm who it belongs to. Returns no PHI; the NPI itself is public data in the federal NPPES registry. Currently only resolves Dr. Kawalek's NPI; returns a not-found response for any other NPI.

Input parameters:

- `npi` (string, required): The 10-digit National Provider Identifier to look up. Digits only.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/co-sickslip-www-verify/api-mcp#diagnostics

## Score history

- 2026-09-28: 70
- 2026-09-27: 70
- 2026-09-26: 69
- 2026-09-25: 69
- 2026-09-24: 68
- 2026-09-23: 68

## Common questions

### What is the co.sickslip.www/verify MCP server?

co.sickslip.www/verify is an MCP server listed in the public MCP registry as co.sickslip.www/verify. Verify a SickSlip doctor's note by Document ID; states served, pricing, physician NPI. Read-only. This page covers its hosted endpoint (https://sickslip.onrender.com/api/mcp).

### Is the co.sickslip.www/verify MCP server safe to use?

co.sickslip.www/verify scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the co.sickslip.www/verify MCP server expose?

co.sickslip.www/verify exposes 5 tools: verify_sickslip_note, list_state_availability, get_sickslip_pricing, list_service_tiers, lookup_physician_npi. Their descriptions and schemas cost roughly 616 tokens of context every time the server is loaded.

### Does the co.sickslip.www/verify MCP server require authentication?

No. We connected to co.sickslip.www/verify without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the co.sickslip.www/verify MCP server still maintained?

co.sickslip.www/verify is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://sickslip.onrender.com/api/mcp
- Website: https://www.sickslip.co/verify
- Changelog RSS feed: https://verifymcp.io/servers/co-sickslip-www-verify/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/co-sickslip-www-verify/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/co-sickslip-www-verify/api-mcp