_ registry / mcp http-sse · checked 49m ago

sickslip-verify

https://sickslip.onrender.com

Registry code: 9c0de507f222e5cd

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://sickslip.onrender.com/api/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is sickslip-verify live?
Yes — it answered the hub's last check (checked 49m ago). It answered 99% of checks over the last 30 days.
Is sickslip-verify free to use?
Yes — the hub reached it with no key and no payment.
What tools does sickslip-verify have?
5 tools: verify_sickslip_note, lookup_physician_npi, get_sickslip_pricing, list_service_tiers, list_state_availability.
Is sickslip-verify safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.4%

90 days 99.1%· all time 99.1%

latency
248ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 344 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • verify a doctor's note by its code
  • check a physician npi
  • list states where notes are available
  • get pricing of note tiers
takes → gives
text → data
tools
5 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
3 open 2 never probed 3 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_sickslip_pricing reads open 49m ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {}
    }
    arguments 5 lines
  • list_service_tiers reads open 49m ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {}
    }
    arguments 5 lines
  • list_state_availability reads open 49m ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {}
    }
    arguments 5 lines
  • verify_sickslip_note reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "code"
      ],
      "properties": {
        "code": {
          "type": "string",
          "maxLength": 64,
          "minLength": 4,
          "description": "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."
        }
      }
    }
    arguments 14 lines
  • lookup_physician_npi reads unknown 7h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "npi"
      ],
      "properties": {
        "npi": {
          "type": "string",
          "pattern": "^[0-9]{10}$",
          "maxLength": 10,
          "minLength": 10,
          "description": "The 10-digit National Provider Identifier to look up. Digits only."
        }
      }
    }
    arguments 15 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 9c0de507f222e5cd.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/9c0de507f222e5cd/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/9c0de507f222e5cd/badge.svg)](https://brick.blue/agent/9c0de507f222e5cd?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.