Is io.github.aniebyl/ololand-dd safe to use?

io.github.aniebyl/ololand-dd has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.

How do I install io.github.aniebyl/ololand-dd?

io.github.aniebyl/ololand-dd can be installed by cloning its GitHub repository and following the setup instructions in the README.

What AI clients work with io.github.aniebyl/ololand-dd?

io.github.aniebyl/ololand-dd is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse transport.

Is io.github.aniebyl/ololand-dd actively maintained?

io.github.aniebyl/ololand-dd is actively maintained — last commit was 3 days ago.

io.github.aniebyl/ololand-dd

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

0 tools GitHub

No known CVEs

No license

Actively maintained

Last commit 3d ago

Works with most clients

Transport: stdio, sse

0 tools

Grade F

Edit this pageView history

Finance Analytics

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio, sse · Node 18+

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

{
  "mcpServers": {
    "io-github-aniebyl-ololand-dd": {
      "command": "<see-readme>",
      "args": []
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-aniebyl-ololand-dd)](https://mcppedia.org/s/io-github-aniebyl-ololand-dd)

Read me

What io.github.aniebyl/ololand-dd does

The underwriting layer inside Claude. Every hour of your diligence survives into the deal record.

Test This Server

No automated test available for this server. Check the GitHub README for setup instructions.

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

36/100across 5 weighted dimensions

How we score →

0255075100

−64

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

No package registry to scan.

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.aniebyl/ololand-dd safe to use?: io.github.aniebyl/ololand-dd has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install io.github.aniebyl/ololand-dd?: io.github.aniebyl/ololand-dd can be installed by cloning its GitHub repository and following the setup instructions in the README.
What AI clients work with io.github.aniebyl/ololand-dd?: io.github.aniebyl/ololand-dd is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse transport.
Is io.github.aniebyl/ololand-dd actively maintained?: io.github.aniebyl/ololand-dd is actively maintained — last commit was 3 days ago.

Similar servers

Others in finance / analytics

View all →

Observability Mcp95

MCP Server for GCP environment for interacting with various Observability APIs.

790 10

Alpha Vantage Mcp93

Real-time financial market data: stocks, forex, crypto, commodities, and economic indicators

150 3

Spreedly Mcp92

A Model Context Protocol (MCP) server that provides AI assistants with direct access to the Spreedly payments API. Enables LLMs to manage gateways, process transactions, tokenize payment methods, and more, through structured, validated tool calls.

9 8

io.github.rezmeplxrf/insightsentry_mcp91

MCP server for InsightSentry financial data API - market data, options, screeners, and more

MCP Security Weekly

Get CVE alerts and security updates for io.github.aniebyl/ololand-dd and similar servers.

Community

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

Edit this pageView history

Finance Analytics

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio, sse · Node 18+

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

{
  "mcpServers": {
    "io-github-aniebyl-ololand-dd": {
      "command": "<see-readme>",
      "args": []
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-aniebyl-ololand-dd)](https://mcppedia.org/s/io-github-aniebyl-ololand-dd)

Read me

What io.github.aniebyl/ololand-dd does

The underwriting layer inside Claude. Every hour of your diligence survives into the deal record.

Test This Server

No automated test available for this server. Check the GitHub README for setup instructions.

README

OloLand Plugins

The verifier stack for buy-side underwriting, as Claude plugins.

This repo is OloLand's plugin marketplace for Claude Cowork (Claude Desktop) and Claude Code (CLI). It hosts the OloLand plugins that augment Anthropic's first-party finance plugin lineup (private-equity, financial-analysis, investment-banking, equity-research, wealth-management).

Anthropic ships breadth. OloLand ships depth. Same Cowork session. Deterministic computation. Defensible record.

Plugins in this marketplace

Plugin	Status	What it does
`ololand-dd`	v1.6.1	Institutional due diligence: deterministic financial engines, 246-category risk taxonomy, cross-document reconciliation, war-game RL strategy simulation, and a flywheel that retrains from analyst corrections.
`ololand-forensic-qoe`	v0.2.0	Forensic Quality-of-Earnings primitives as a standalone wedge SKU: Beneish, Benford, EBITDA bridge, journal-entry testing, lapping detection, working-capital deep dive. The Pre-LOI Forensic Screen — $7,500 / 72 hours, IC-defensible, vs Big-4 QoE at $150-500K / 4-8 weeks.
`ololand-compliance-hooks`	v0.2.0	Drop-in compliance, citation, and provenance hooks for Anthropic's Claude Cowork finance plugins. PreToolUse MNPI guard, PostToolUse citation enforcer, audit-log writeback. Populates the empty `hooks/` scaffold Anthropic's verticals ship with.

The plugins compose additively with each other and with Anthropic's first-party finance plugins.

Maintainer workflow

This repository generates Claude and Codex plugin artifacts from canonical YAML metadata. Edit marketplace.yaml and plugins/*/plugin.yaml, then run:

python3 -m pip install -r scripts/requirements.txt
python3 scripts/generate-plugin-artifacts.py
./scripts/check-plugin-artifacts.sh

See docs/plugin-publishing.md for the full release process.

Prerequisites

The only thing you need is a free OloLand account. No env var setup, no manual API key creation. The plugins handle authentication via OAuth automatically when you install them.

Two account rails

Rail	Cost	Access
Developer (free)	Sign up at https://app.ololand.ai/signup	Sandbox-only — full MCP tool access against the included sample deal (`Paragon Flight School (Sample)`). Unlimited calls. No payment, no credit card.
Platform (paid)	Pro $199/mo, Firm $800/seat/mo, or per-deal SKUs (see pricing)	Access to your own deals + cross-deal memory + outcome flywheel + production volumes

You can install the plugins on a free Developer account and explore everything against the sample deal — DCF, LBO, Monte Carlo, forensic QoE, risk taxonomy, war-game, all of it. When you're ready to run on your own data, upgrade to a paid plan.

What happens on first install (no env var setup needed)

Add the marketplace and install a plugin (steps in the Install sections below)
The plugin defines an ololand MCP connector that points at OloLand's backend
On first invocation, your Cowork / Claude Code prompts you to Authorize the connector via OAuth
Click Authorize — your browser opens to OloLand's auth page, you sign in, accept the scopes
OloLand's backend auto-provisions a scoped agent key, bound to your OAuth client. Cowork / Claude Code stores it for you
Subsequent calls use the stored credential. No env var, no manual setup.

That's it. The OAuth flow happens once and the connector is authenticated for that session and future ones.

Power user / headless setup (optional)

If you're running the plugins in a headless environment (CI, server-side automation, custom MCP client that can't run OAuth), you can bypass OAuth with a manual agent key:

Sign in at https://app.ololand.ai
Settings → Agent keys → Cre

... View full README on GitHub

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

36/100across 5 weighted dimensions

How we score →

0255075100

−64

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

No package registry to scan.

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.aniebyl/ololand-dd safe to use?: io.github.aniebyl/ololand-dd has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install io.github.aniebyl/ololand-dd?: io.github.aniebyl/ololand-dd can be installed by cloning its GitHub repository and following the setup instructions in the README.
What AI clients work with io.github.aniebyl/ololand-dd?: io.github.aniebyl/ololand-dd is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse transport.
Is io.github.aniebyl/ololand-dd actively maintained?: io.github.aniebyl/ololand-dd is actively maintained — last commit was 3 days ago.