Developer · Remote MCP server

Wiv

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

Visit Wiv's website

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
ai.wiv/mcp
Version
5.0.1
Status
Active
Category
developer
Transport
Streamable HTTP, SSE (HTTP + Server-Sent Events)
Published
2026-07-31
Updated
2026-07-31
Publisher
ai.wiv
Namespace
Namespace verified by the MCP Registry via the domain wiv.ai · how
Website
wiv.ai
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://mcp.wiv.ai/mcpNone
SSE (HTTP + Server-Sent Events)https://mcp.wiv.ai/sseNone

Live check

This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.

Endpoint
https://mcp.wiv.ai/mcp (HTTP)
Reachable
Yes (HTTP 401)
Handshake
Not completed: sign-in required
Sign-in required
Yes - HTTP 401; a Bearer token is asked for
Checked on
2026-10-05
Endpoint
https://mcp.wiv.ai/sse (SSE)
Reachable
Yes (HTTP 401)
SSE stream
Not opened: sign-in required
Sign-in required
Yes - HTTP 401; a Bearer token is asked for
Checked on
2026-10-05

How the live check works

How to connect Wiv

Wiv is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.wiv.ai/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

It also lists an endpoint on the older SSE transport https://mcp.wiv.ai/sse. Clients that support remote servers generally still accept SSE endpoints, though the protocol now favours Streamable HTTP.

No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.

Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More developer servers

All 5,152 →
ServerRunsEndpoint or package
WisdomgraphNeo4j-native DIKW memory for Claude Code - knowledge that compounds across sessions.Local · stdionpm: wisdomgraph
WisegitExtracts decision intent from git history and protects intentional code from AI modification.Local · stdionpm: @sandip124/wisegit
Wishfinity MCP PluswSave any product URL to your Wishfinity wishlist. Works with any MCP client.Local · stdionpm: wishfinity-mcp-plusw
WitWikiA shared team wiki your coding agents read and write - across every repo and every MCP client.Remote · HTTPLive check: sign-in requiredapi.witwiki.app
WjttcF1-grade MCP certification. 52 tests, 9 tiers (49 scored + T9 Receipt validation). Ecosystem: #2759.Local · stdionpm: wjttc
wontopos.comWontopos (WOS) long-term memory (beta) - one memory across Claude Code, Cursor, and your agents.Local · stdionpm: wontopos-mcp
Woodpecker CIRead Woodpecker CI repositories, pipelines and logs, and drive builds, secrets and crons.Local · stdionpm: @ni-c/woodpecker-ci-mcp
Wopee MCPAI testing agents for web apps - dispatch test runs, crawls, fetch artifacts and status.Local · stdionpm: wopee-mcp