Other · Remote MCP server

Ololand Dd

OloLand M&A intelligence - 33 tools for deal analysis, valuation, risk, and cross-deal learning.

What the MCP Registry states

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

Registry name
io.github.aniebyl/ololand-dd
Version
1.0.1
Status
Active
Category
other
Transport
Streamable HTTP, stdio (local process)
Package
npm
Published
2026-04-01
Updated
2026-04-01
Publisher
aniebyl (GitHub)
Namespace
Namespace verified by the MCP Registry via GitHub (github.com/aniebyl) · how
Repository
github.com/ololand-ai/ololand-dd-plugin
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://ma-workbench-api-303576587005.us-central1.run.app/mcpNone

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.

Reachable
Yes (HTTP 401)
Handshake
Not completed: sign-in required
Sign-in required
Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
Checked on
2026-10-05

How the live check works

Packages

RegistryPackageVersionTransportEnvironment variables
npm@ololand/mcp-server1.0.1stdioNone declared

How to connect Ololand Dd

Ololand Dd is a remote MCP server: there is nothing to install. Its endpoint is https://ma-workbench-api-303576587005.us-central1.run.app/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.

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.

It can also run locally from a Node.js package published to the npm registry: @ololand/mcp-server version 1.0.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @ololand/mcp-server@1.0.1.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "ololand-dd": {
      "command": "npx",
      "args": [
        "-y",
        "@ololand/mcp-server@1.0.1"
      ]
    }
  }
}

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 other servers

All 8,395 →
ServerRunsEndpoint or package
okrTeam OKRs from your AI workspace: objectives, key results, and weekly check-ins.Remote · HTTPokr.basenull.com
Oku-Akasaka Sushi TanjiOmakase courses at a sushi counter in Akasaka, Tokyo, with a pre-filled link to the booking page.Remote · HTTPLive check: ✓ handshakesushi-tanji.com
OleaDesk MailYour own AI reads, searches and drafts in your mailbox, on your Windows computer.Remote · HTTPLive check: sign-in requiredapp.oleadesk.com
Ollama / vLLM BridgeCall your local Ollama or vLLM model over MCP with schema-validated JSON output.Local · stdioPyPI: mcp-ollama-vllm
OLVM AIopsGoverned OLVM / oVirt 4.5 ops - 17 MCP tools: inventory, health, capacity, diagnosis; audited.Local · stdioPyPI: olvm-aiops
OMEMMemory for AI agents that tracks beliefs over time and surfaces contradictions.Local · stdioPyPI: omem-infrastructure
OmentirFind LinkedIn prospects, draft outreach, and run human-paced campaigns from your AI agent.Remote · HTTPLive check: sign-in requiredomentir.com
Omiss MCPOMISS MCP server. Net schedule, nets on the air, members, check-in history, awards.Local · stdioPyPI: omiss-mcp