Verisk Xactrestore is answering right now. Last checked 1 min ago.
Uptime history
52 days of history
52 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
906 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http
Nothing serious here today
Today is the operative word: we check Verisk Xactrestore every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.
run in your terminal
claude mcp add mcp --transport http https://xactrestore-xactremodelserver-usw2-prod.propsol.io/mcp~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"mcp": {
"url": "https://xactrestore-xactremodelserver-usw2-prod.propsol.io/mcp"
}
}
}~/.codex/config.toml
[mcp_servers.mcp]
url = "https://xactrestore-xactremodelserver-usw2-prod.propsol.io/mcp".cursor/mcp.json
{
"mcpServers": {
"mcp": {
"url": "https://xactrestore-xactremodelserver-usw2-prod.propsol.io/mcp"
}
}
}.vscode/mcp.json
{
"mcpServers": {
"mcp": {
"url": "https://xactrestore-xactremodelserver-usw2-prod.propsol.io/mcp"
}
}
}This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://xactrestore-xactremodelserver-usw2-prod.propsol.io/mcp | streamable-http | sign-in | 890 ms | 1 min ago |
Alternatives to Verisk Xactrestore
same job, measured the same wayVerisk Underwriting Intelligence
by verisk-underwriting-intelligence
I
Policycheck
by vibegpt
AI seller verification and policy risk analysis for any online store.
Quantrisk
by 78degrees
Portfolio risk analytics MCP server — VaR, Monte Carlo, stress testing, and more.
Verisk Xactrestore — questions
Answers built from our own checks of this server.
Why is there no tool list for Verisk Xactrestore?
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 Verisk Xactrestore 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 906 ms. The bar chart above shows every period we have measured.
How do I connect Verisk Xactrestore?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Verisk Xactrestore?
No API key is involved. Verisk Xactrestore answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Verisk Xactrestore?
It answers our handshake in 906 ms on average, which is faster than 12% 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.