Wiv MCP Server

by wiv Your server? Claim it

answering

Wiv is answering right now. Last checked 11 min ago.

Automate FinOps workflows, cases, and cloud ops via the Wiv Workflow API.

Uptime history 48 days of history

48 days agonow

100.0%

Uptime 24h

182 of 182 checks

—

Tools

hidden behind auth

589 ms

Response time

average over 24h

API key

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Wiv 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 11 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add mcp --transport http https://mcp.wiv.ai/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.wiv.ai/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.mcp]
url = "https://mcp.wiv.ai/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.wiv.ai/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.wiv.ai/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but you need an API key from its owner to call it.

This server publishes 1 more address. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.wiv.ai/mcp	streamable-http	needs key	531 ms	11 min ago
https://mcp.wiv.ai/sse	sse	needs key	598 ms	11 min ago

Alternatives to Wiv

same job, measured the same way

Files Com

by mcparmory

Manage files, users, and automated workflows across cloud storage and protocols

247 installs/wk local only

HaloPSA

by wyre-technology

MCP server for HaloPSA — clients, tickets, and PSA workflows via the HaloPSA REST API.

local only

HaloPSA

by wyre-ai

MCP server for HaloPSA — clients, tickets, and PSA workflows via the HaloPSA REST API.

local only

Testrigor

by testrigor

Manage test suites, run tests, view results, and automate QA workflows via AI with testRigor.

answering

Tallyfy Workflow Automation

by tallyfy

Automate tasks, processes, and approvals with AI.

answering

Github

by mcparmory

Manage repositories, users, releases, and automate GitHub workflows

291 installs/wk local only

Obscuraai MCP Server

by madeinphantom

Generate visual AI automation workflows from any MCP client. No API key required.

52 installs/wk local only

DottedSign

by dottedsign-official

Automate eSignature workflows and signing tasks via natural language commands.

answering

Wiv — questions

Answers built from our own checks of this server.

Why is there no tool list for Wiv?

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 Wiv working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 182 of 182 checks got a reply (100.0%), average response time 589 ms. The bar chart above shows every period we have measured.

How do I connect Wiv?

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 will need your own key: it refuses anonymous clients.

Does Wiv need an API key?

Yes. Every time we knock, Wiv 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 Wiv?

It answers our handshake in 589 ms on average, which is faster than 22% 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.