Server data from the Official MCP Registry
OloLand M&A intelligence — 33 tools for deal analysis, valuation, risk, and cross-deal learning.
About
OloLand M&A intelligence — 33 tools for deal analysis, valuation, risk, and cross-deal learning.
Remote endpoints: streamable-http: https://ma-workbench-api-303576587005.us-central1.run.app/mcp
Security Report
Valid MCP server (1 strong, 0 medium validity signals). 1 code issue detected. No known CVEs in dependencies. Package registry verified. Imported from the Official MCP Registry. 1 finding(s) downgraded by scanner intelligence.
Endpoint verified · Requires authentication · 3 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Permissions Required
This plugin requests these system permissions. Most are normal for its category.
How to Install & Connect
Available as Local & Remote
This plugin can run on your machine or connect to a hosted endpoint. during install.
Documentation
View on GitHubFrom the project's GitHub README.
OloLand Plugins
The verifier stack for buy-side underwriting, as installable agent plugins.
This repo is OloLand's plugin marketplace for Claude Cowork (Claude Desktop), Claude Code (CLI), Codex, and Cursor / Grok Bot. It hosts the OloLand plugins that augment Anthropic's first-party finance plugin lineup (private-equity, financial-analysis, investment-banking, equity-research, wealth-management) and expose the same OloLand MCP server on Cursor-format hosts.
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.29.0 | Institutional due diligence: deterministic financial engines, 311-factor risk taxonomy (67 diligence categories), analytical workbench tools, verified forensic screen workflow, war-game RL strategy simulation, deal and portfolio cockpit reads, virtual deal-team briefings, diligence-request tracking, and a firm's reviewed corrections and recorded outcomes feeding that firm's later risk analysis. |
ololand-forensic-qoe | v0.6.9 | Forensic earnings workflows with explicit evidence and data gaps. Individual MCP tools and self-serve PDF reports have different coverage; reports are included in Pro and above. OpenAI submission export and draft review cases are documented in the submission guide. |
ololand-compliance-hooks | v0.2.6 | 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. |
cim-generator | v1.1.2 | 14-section CIM generator with provenance — sell-side memorandums built from your reconciled deal data (financial snapshots, risk insights, market research), not LLM prose. View, edit, and export the finished CIM (PDF, DOCX, PPTX) from the deal workspace. |
The plugins compose additively with each other and with Anthropic's first-party finance plugins.
Maintainer workflow
This repository generates Claude, Codex, and Cursor / Grok Bot 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
You need an OloLand account with access to the company/workspace and deals you want to use. The published plugins connect through host-managed OAuth. Installing a plugin does not sign you in or grant access; connect the ololand server explicitly and review the requested permissions.
Account and plans
Sign up at https://app.ololand.ai/signup. Every signup starts a 7-day Pro trial with no card. Paid plans are Pro $199/mo, Team $499/mo (2 seats included, +$199 per additional seat), and Enterprise (custom).
When a trial ends without a plan the account becomes read-only: existing deals can be read, but there are no credits and no new deals. Plans are managed in the app under Settings → Billing.
Connect your OloLand account
- Add the marketplace and install the plugin you need.
- Open the plugin's Connectors tab or your host's MCP connection settings and select Connect for
ololand(https://api.ololand.ai/mcp). - Complete the OAuth sign-in on
https://api.ololand.aiyourself. Check the OloLand account and company/workspace and review the requested permissions before approving. - The host manages the authorized connection. Verify access with a read-only request, such as listing the deals available to that connection, before starting analysis.
Do not paste credentials into chat or ask the plugin to read them from local files or environment variables. If the host cannot complete OAuth, report the connection gap and stop dependent work. Installing the plugin, seeing tools listed, or granting scopes does not establish that every workflow has been tested.
Install — Grok Bot and Cursor
Grok Bot installs plugins in the Cursor format. This repo ships a multi-plugin marketplace at .cursor-plugin/marketplace.json. Each plugin reuses its existing skills/, commands/, agents/, assets, and OAuth-native .mcp.json — there is no API key in the repository.
Grok Bot
- Open the bot's plugin settings, or ask:
Install the OloLand plugins from ololand-ai/ololand-plugins - Add the GitHub marketplace
ololand-ai/ololand-plugins - Install
ololand-ddfor the deal, diligence, and valuation MCP tools (get_deal,run_due_diligence,run_lbo_model,generate_ic_package, and the rest of the OloLand server). Optionally installololand-forensic-qoe,cim-generator, andololand-compliance-hooks - When prompted, authorize the
ololandMCP connector via OAuth. No env var or pasted token is required
Cursor
- Settings → Plugins → add a marketplace from GitHub:
ololand-ai/ololand-plugins - Install the plugins you need from the OloLand marketplace
- Authorize the
ololandconnector on first use
After install, check the plugin details for the shared skills and ololand connector. Use the host's supported OAuth connection flow explicitly. If no sign-in flow is available or it fails, report that limitation and stop dependent work; do not substitute a credential from the environment.
Install — Claude Cowork (Claude Desktop)
The recommended path for analysts running deals through the Cowork UI.
Step 1 — Open the plugin manager
- Open Claude Desktop
- Switch to the Cowork tab (top of window)
- Click Customize in the left sidebar
- Click Plugins in the Customize submenu
Step 2 — Add the OloLand marketplace
- Click the
+button next to "Personal plugins" (or the equivalent button in the Plugins panel header) - Choose Create plugin → Add marketplace
- In the URL field, enter:
ololand-ai/ololand-plugins - Click Sync
- After ~5-10 seconds, a new pill
ololand-pluginsappears with four plugin cards:Ololand dd,Ololand forensic qoe,Ololand compliance hooks,Cim generator.
Step 3 — Install the plugins
Click the + button on each card you want. Installed plugins appear in your Personal plugins sidebar:
- Ololand dd
- Ololand compliance hooks
- Ololand forensic qoe
- Cim generator
Step 4 — Verify
Click Ololand dd in the sidebar. The detail view should show:
| Field | Expected value |
|---|---|
| Source | Marketplace (ololand-plugins) |
| Version | The ololand-dd version in the table at the top of this page |
| Author | OloLand |
| Skills tab | 22 skills, and commands including /cockpit, /playbook-recall, /calibrate-vs-history |
| Agents tab | 3 agents: dd-analyst, forensic-screener, war-game-strategist |
| Connectors tab | 1 connector named ololand |
If Agents shows 1 instead of 3, you're on an older version. Remove the marketplace and re-add following Step 2.
Step 5 — Authorize the OloLand connector
Open the plugin's Connectors tab and select Connect for ololand. Complete the OAuth sign-in on https://api.ololand.ai, checking the intended account, company/workspace, and requested access before you approve. Verify with a read-only deal listing. If sign-in is unavailable or fails, report the connection gap before starting any analysis.
Install — Claude Code (CLI)
For developers, IT teams, and anyone running Claude Code locally.
Step 1 — Add the marketplace
In any Claude Code chat session:
/plugin marketplace add ololand-ai/ololand-plugins
Step 2 — Install the plugins
/plugin install ololand-dd@ololand-plugins
/plugin install ololand-forensic-qoe@ololand-plugins
/plugin install ololand-compliance-hooks@ololand-plugins
Step 3 — Reload to activate
/reload-plugins
Step 4 — Verify
/plugin
This opens the plugin manager TUI. Tab to the Installed tab and confirm the OloLand plugins you installed are listed and enabled. Open ololand-dd detail to verify the version matches the table at the top of this page and that it lists the three agents.
Step 5 — Authorize the OloLand connector
Open /mcp, choose the ololand server, and start its OAuth authentication flow. In the browser, sign in to the intended OloLand account and review the company/workspace and requested permissions before approving. Claude Code manages the connection. Verify with a read-only deal listing; if authorization is unavailable or fails, report the error and stop dependent work.
Usage — ololand-dd
The flagship due-diligence plugin. Skills are auto-fired when relevant; commands are explicit invocations.
Commands
Type / in any chat to see autocomplete. Plugin commands are namespaced as /ololand-dd:<command>.
| Command | What it does |
|---|---|
/dd-analyze <deal_id> | Run the deal extraction and risk-analysis pipeline; valuation reads or fresh model candidates are separate explicit /valuation actions |
/new-deal <ticker_or_name> | Create a new deal from a ticker (auto-fetches 10-K) or company name |
/risk-matrix <deal_id> | Render the risk taxonomy (67 categories / 311 risk factors) as an interactive tile |
/risk-report <deal_id> | Structured risk report — severity × likelihood × velocity, with $-impact |
/valuation <deal_id> read [method] | Read governed DCF / LBO and source-backed Comps. To create a fresh model candidate, explicitly use /valuation <deal_id> run <method> or /valuation <deal_id> refresh <method>; bare and legacy method-only calls are read-only. |
| `/qoe-analysis <deal_id> [latest | run]` |
/verify <deal_id> | Defend every number: verify an OloLand artifact against source docs + engine runs, or grade an externally-drafted memo (e.g. from Claude Cowork) per-claim against the deal corpus |
| `/compliance-analysis <deal_id> [ofac | hsr |
| `/scenario-analysis <deal_id> [stress | market |
/earnings-analysis <deal_id> | Analyze earnings-call transcript segments for diligence signals |
| `/verification-marketplace <deal_id> [status | list |
| `/ic-package <deal_id> [status | generate |
| `/value-impact <deal_id | company |
| `/deal-health <deal_id> [actions | create-action]` |
| `/workbook [list | get |
/company-discovery <query> | Search the company-discovery surface from natural-language or structured criteria |
| `/watchlist [list | create |
| `/advisory <deal_id> [list | request]` |
| `/financing <deal_id> [status | analyze |
/managed-context-agent <deal_id> <agent_key> | Launch a configured managed context agent when enabled |
/okf-export <deal_id> | Export a machine-readable OKF deal bundle |
/war-game <deal_id> [scenarios] | 16-quarter MaskablePPO competitive simulation across scenarios |
/similar-deals <deal_id> | Cross-deal memory: find similar past deals, accuracy patterns, valuation ranges |
/playbook-recall <deal_id> | What worked, what didn't, what was missed in similar past deals from your firm's history |
/calibrate-vs-history <deal_id> | Apply your firm's historical projection bias to recalibrate the deal's headline numbers |
/talk-to-deal <deal_id> | The fast conversational answer: a quick read-only question about the deal |
/deal-search <deal_id> | Full-text + semantic search across a deal's data room |
/unit-economics <deal_id> | SaaS cohort retention (NDR/GRR), LTV/CAC, payback, magic number, rule of 40 |
/source <criteria> | Source new M&A/PE deals from criteria; enrich with contact data; dedupe vs CRM |
/cockpit <deal_id> or /cockpit portfolio | Readiness gates, pending approvals, drivers outside tolerance, the dispatch ledger, and the precomputed financial briefing |
| `/deal-team <deal_id> [briefing | proposals |
| `/diligence-requests <deal_id> [list | create |
/strategy <deal_id> <framework> | Porter's five forces, SWOT, value chain, and five more frameworks run against the deal's evidence |
/take-private <deal_id> [target_irr] | Sponsor-side price ceiling for an announced take-private on a per-share football field; not a recommended price |
The full list of 60 commands is in the ololand-dd README.
Sub-agents
In Cowork, click an agent in the Agents tab and it loads as the lead agent for the conversation. In Claude Code CLI, agents auto-fire based on context, or invoke explicitly with /agents and pick one.
| Agent | Use when |
|---|---|
dd-analyst | Full DD workflows, IC memo prep, deep deal investigation. The general-purpose specialist. |
forensic-screener | Pre-LOI forensic deep-dive. Runs all 7 forensic primitives, reconciles findings against source hierarchy, produces an IC-defensible exclusion schedule with severity, $-impact, and citations. |
war-game-strategist | Stress-testing the deal thesis against competitor responses. Runs 4-scenario MaskablePPO simulation, calibrates vs. similar-deal outcomes, overlays on deterministic DCF, and suggests bid sensitivities for human review. |
Example workflow — full Pre-LOI DD
In Cowork (or Claude Code), with a deal in your OloLand account:
/ololand-dd:new-deal ACME-Manufacturing
↓ creates the deal
/ololand-dd:dd-analyze deal_acme_2026
↓ runs the full multi-agent DD
Then for forensic depth:
/ololand-dd:risk-matrix deal_acme_2026
↓ renders the risk-taxonomy tile
@forensic-screener run a Pre-LOI screen on deal_acme_2026
↓ delegates to the forensic specialist sub-agent
For thesis stress-test:
@war-game-strategist test the buyout thesis on deal_acme_2026 across all 4 scenarios
Usage — ololand-forensic-qoe
The standalone Pre-LOI Forensic Screen. Use when you want forensic depth without the full DD plugin.
Commands
| Command | What it does |
|---|---|
/forensic-screen <deal_id> | Full battery: Beneish + Benford + EBITDA bridge + journal-entry + lapping + working-capital + revenue-quality. Returns severity-scored exclusion schedule. |
/beneish <deal_id> | Beneish M-Score (private-company adjusted). 8-variable earnings-manipulation probability. |
/benford <deal_id> | Benford's Law first-digit testing on GL transactions. χ² + MAD. |
/ebitda-bridge <deal_id> | On OpenAI, explicit supplied-input bridge arithmetic and heuristic flags; source verification and accepted normalized earnings remain separate. |
/journal-test <deal_id> | Journal-entry anomaly testing. Period-end concentration, round-numbers, posting authority, weekend entries. |
/lapping-check <deal_id> | AR-lapping fraud detection. Customer-to-cash trace, application gap detection. |
/conflicts <deal_id> | Cross-document conflict detector for mismatched figures, dates, ownership, terms, and obligations. |
/verify <deal_id> | Verify an externally drafted artifact against the ingested deal corpus. |
Required inputs
- Beneish: 2+ years of income statement + balance sheet data
- Benford: GL export with ≥1,000 line items
- EBITDA bridge: on OpenAI, explicit numerical base and adjustment schedule; independent sources and human review are still needed to accept normalized earnings
- Journal-entry tests: GL with timestamps + posting user IDs
- Lapping: AR aging + cash receipts journal with customer-level detail
- Full screen: skip-and-report behavior — runs every primitive whose inputs are present, reports which were skipped and why
Example workflow — $50M EBITDA target screen
/ololand-forensic-qoe:forensic-screen deal_target_2026
Returns an IC-defensible exclusion schedule with:
- Reported EBITDA $X.XM → defensible EBITDA $Y.YM (delta $Z.ZM)
- Each forensic primitive's verdict (pass / warning / fail)
- Adjustments table with $ impact and source citations
- Severity-scored findings (low / medium / high / critical)
- Findings by severity for the deal team to weigh
Usage — ololand-compliance-hooks
The drop-in hooks plugin. Most users don't invoke this directly — it runs automatically once installed.
What it does (passive)
| Hook | Trigger | Action |
|---|---|---|
| PreToolUse: MNPI guard | Bash, Write, Edit, MultiEdit | Blocks tool calls referencing material non-public information patterns ("material non-public", "insider trading window", etc.) unless input contains # mnpi:cleared marker |
| PostToolUse: citation enforcer | After CIM / IC memo / dossier generation | Scans for $-amounts, %, multiples without source citation. Warns by default. |
| PostToolUse: provenance writeback | After every generative output | Appends NDJSON to the local ~/.ololand/provenance/YYYY-MM-DD.ndjson ledger |
| Pre + PostToolUse: audit log | Every mcp__ololand__* call | Mirrors invocations to ~/.ololand/audit/YYYY-MM-DD.ndjson |
| SessionStart: banner | New session | Confirms hooks armed |
Configuration via env vars
| Variable | Default | Purpose |
|---|---|---|
OLOLAND_CITATION_BLOCK | 0 | Set to 1 to upgrade citation enforcer from warn to deny |
The hooks keep these ledgers local and do not require an OloLand credential. Server-side MCP auditing remains authoritative for calls handled by OloLand.
Local logs
Inspect provenance + audit ledgers any time:
jq -c '.' ~/.ololand/provenance/$(date -u +%Y-%m-%d).ndjson
jq -c '.' ~/.ololand/audit/$(date -u +%Y-%m-%d).ndjson
These ledgers are append-only NDJSON. Rotate or compress per-day as needed.
Troubleshooting
Cowork: "Marketplace sync failed. Check the repository URL and try again."
Most common cause: cached marketplace from a prior install attempt. Click ... on the failing pill → Remove. Then re-add.
If still failing, fall back to the Upload plugin path (zip upload). Per Cowork issue #38429, source: "manual" plugins are protected from the auto-removal bug that affects source: "github" plugins.
Cowork: plugin disappears after restart
Known issue #38429 and #39274. RemotePluginManager removes 3rd-party github-sourced plugins on restart. Workarounds:
- Reinstall via "Upload plugin" (zip path) instead of "Add marketplace"
- Or wait for Anthropic to ship the fix
Cowork: chat says "Unknown skill: plugin"
Cowork chat does NOT support /plugin slash commands. Plugin management is UI-only:
- Customize → Plugins → Browse / Add marketplace / Upload plugin
The /plugin command set works in Claude Code CLI only.
Cowork: showing old version (1.4.x) instead of 1.5.x
Likely cached install from before the marketplace rename (was ololand-dd-plugin, now ololand-plugins). Remove the old marketplace pill, add ololand-ai/ololand-plugins fresh, install.
Verify the current version by clicking the plugin → Agents tab should show 3 agents (dd-analyst, forensic-screener, war-game-strategist).
CLI: /plugin install fails with "marketplace not found"
/plugin marketplace update ololand-plugins
Or if that fails:
/plugin marketplace remove ololand-plugins
/plugin marketplace add ololand-ai/ololand-plugins
Tools fail with authentication or authorization errors
For a 401, inspect the ololand connector's connection status. If the user wants to restore the connection, they can start the host's supported OAuth sign-in flow and review the account and requested permissions themselves. Do not automatically disconnect, reconnect, or approve consent.
For a 403 or company-scope error, check that the connected account has access to the requested company/workspace and deal. Do not assume reconnecting will grant missing permissions. Report the specific access gap and stop dependent work until the user resolves it.
Plugin skills not appearing after install
Run:
/reload-plugins
If still missing, clear the plugin cache:
rm -rf ~/.claude/plugins/cache
Then re-install. Restart Claude Code / Claude Desktop after the cache clear.
Why this exists
OloLand's thesis: Anthropic's finance plugins are "reference templates — they get better when you tune them to how your firm works" (their own README). That is exactly what we are: the institutional tuning.
Anthropic ships breadth — five vertical plugins, ten named agents, eleven read-only data connectors. We ship depth — deterministic computation, structured taxonomy, persistent memory, and the compliance hooks Anthropic's first-party plugins ship empty.
For the full positioning, see the comparison page.
Contributing
Each plugin lives under plugins/<name>/ with Claude, Codex, and Cursor manifests that share the same skills, commands, and MCP config. The Claude marketplace catalog at .claude-plugin/marketplace.json and the Cursor marketplace at .cursor-plugin/marketplace.json are generated from marketplace.yaml and must stay in version lockstep with each plugin's plugin.yaml.
Branch from origin/main, open a PR into main (operator ruling 2026-07-14: this repo is main-only — it has no staging environment, so unlike ololand-ai/olo5 there is no staging branch in the flow; the old staging branch is retired and stale). The repo allows merge commits only (rebase/squash disabled).
To bump a plugin version, update both the plugin's plugin.json AND the marketplace.json entry — scripts/check-version-sync.sh (run pre-commit) will fail the commit if they drift.
Support
- Email: support@ololand.ai
- Issues: https://github.com/ololand-ai/ololand-plugins/issues
- Docs: https://ololand.ai
License
Apache-2.0. See LICENSE.
Reviews
No reviews yet
Be the first to review this server!
More Developer Tools MCP Servers
Rea
Freeby Morluto · Developer Tools
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Paperclip
Freeby Paperclipai · Developer Tools
Trending hip-hop artist momentum scores across four cultural dimensions.
Scrapling
Freeby D4Vinci · Developer Tools
Web scraping with stealth HTTP, real browsers, and Cloudflare bypass. CSS selectors supported.
Git
Freeby Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
Toleno
Freeby Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
MCP Marketplace
Freeby mcp-marketplace · Developer Tools
Search and install MCP servers from inside your AI client.
