Skip to content
priorcase logo

priorcase MCP server

Which MCP servers are priorcase's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-27

← Back to priorcase

Whose server it is
  • Registry namecom.priorcase/priorcaseverified in the MCP registry

The registry name sits under priorcase.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-27
  • Staterequires sign-inchecked 2026-10-27

On 2026-10-27 the server answered and asked for a sign-in with a priorcase account (OAuth). It shows its tool list only to signed-in users, so we list none here.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 9, the first on 2026-10-27
  • INITE MCP score94 of 100answers 100 · definitions 83 · context 95 · connects 100
  • Answered100% of days9 of 9 daily checks
  • Median first answer732 ms
  • Space in an agent's context≈ 3,603 tokensthe definitions of all its tools (11), which an agent carries on every turn
  • Tool definitionsB · 83 of 100
  • Typed results0 of 11 toolsdeclared outputSchema: results come typed, read once
  • Not saying whether it only reads or can destroy: 11 of 11

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "priorcase": {
      "type": "http",
      "url": "https://priorcase.com/mcp/"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http priorcase https://priorcase.com/mcp/

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://priorcase.com/mcp/ as a custom connector in the settings.

The first time it connects, the client opens a priorcase sign-in.

OpenAPI spec

24 paths, read 2026-10-27. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.