mcpbeat Sign in

Nivelrisk MCP Server

by nivelrisk Your server? Claim it
answering

Nivelrisk is answering right now. Last checked 14 min ago.

Commercial auto insurance MCP server for NYC TLC for-hire vehicles. 33 tools, submission to bind.

Uptime history 91 days of history · worst day 95%
91 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
570 ms
Response time
average over 24h
authentication required
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Nivelrisk every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

run in your terminal
claude mcp add mcp-server --transport http https://mcp.nivelrisk.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://mcp.nivelrisk.com/mcp
~/.codex/config.toml
[mcp_servers.mcp-server]
url = "https://mcp.nivelrisk.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp-server": {
      "url": "https://mcp.nivelrisk.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "mcp-server": {
      "type": "http",
      "url": "https://mcp.nivelrisk.com/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URLTransportStateLatencyChecked
https://mcp.nivelrisk.com/mcp streamable-http needs auth 549 ms 14 min ago

Alternatives to Nivelrisk

same job, measured the same way
Poldex
by lordolami

MCP server exposing PolDex commercial insurance extraction tools to AI agents.

34 installs/wk local only
Cork
by wyre-ai

MCP server for Cork's cyber-insurance API for MSPs.

local only
Slimcontext MCP Server
by agentailor

MCP Server for SlimContext - AI chat history compression tools

68 installs/wk local only
VertoDigital MCP Server
by vertodigital

B2B marketing intelligence and lead-capture tools for vertodigital.com.

6 tools answering
Hedge Broker
by hedgespecialty-www

Wholesale commercial insurance appetite, submissions, policies, payments, and broker workflows.

answering
Bilibili MCP Server
by xzxzzx-ai

Bilibili MCP tool for video metadata, transcripts, subtitles, and comment summarization

1 625 installs/wk local only
Wheel Fitment API
by driveate

Official MCP server for vehicle wheel and tire fitment data from wheel-size.com

119 installs/wk local only
Sms Ru MCP
by theyahia

MCP server for SMS.RU API — send SMS, check status, balance. 3 tools.

34 installs/wk local only

Nivelrisk — questions

Answers built from our own checks of this server.

Why is there no tool list for Nivelrisk?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Nivelrisk working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 570 ms. The bar chart above shows every period we have measured.
How do I connect Nivelrisk?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.
Does Nivelrisk need an API key?
Yes. Every time we knock, Nivelrisk answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is Nivelrisk?
It answers our handshake in 570 ms on average, which is faster than 20% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.