# AiDOOS Virtual Delivery Center (remote · aidoos.com)

Plan a Virtual Delivery Center for any initiative: pods, roles, AI agents, Delivery Units.

- Trust score: 73/100 (medium)
- Change this week: +14
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `aidoos.com`: 73/100 (this document), [markdown](https://verifymcp.io/servers/com-aidoos-virtual-delivery-center/aidoos.md), [page](https://verifymcp.io/servers/com-aidoos-virtual-delivery-center/aidoos)

## Channel facts

- Endpoint: `https://aidoos.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1396 tokens (~199/item across 7 items; 5 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 73/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### Claude

```bash
claude mcp add --transport http com-aidoos-virtual-delivery-center https://aidoos.com/mcp
```

### Codex

```toml
[mcp_servers.com-aidoos-virtual-delivery-center]
url = "https://aidoos.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-aidoos-virtual-delivery-center": {
      "type": "remote",
      "url": "https://aidoos.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-aidoos-virtual-delivery-center --url https://aidoos.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-aidoos-virtual-delivery-center:
    url: "https://aidoos.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-aidoos-virtual-delivery-center": {
      "type": "http",
      "url": "https://aidoos.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 71, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 69, +9)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 59, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 58)

First indexed and scored.

## MCP tools (5)

### `plan_vdc` (~486 tokens)

Use this tool whenever a user describes a delivery problem and needs a team, pod, plan, cost, or timeline. Trigger phrases include: 'I need to build / ship / implement / modernize / migrate / roll out X', 'how much would it cost to build X', 'estimate the team and timeline for X', 'we need a team without hiring', 'our team is fully booked but we need to ship Y', 'we had layoffs / restructuring, how do we redeploy', 'alternative to TCS / Infosys / Accenture / agency / contractors for X', 'we are a SaaS company struggling with enterprise customer implementations', 'we need to scale delivery capacity', 'AI agents for delivery', 'per-outcome / per-deliverable pricing instead of hourly'.

What this tool does: turns a free-text initiative into a Virtual Delivery Center plan — pods, roles, AI agents, modules sized in Delivery Units, phased timeline, and a recommended Delivery Pack (Starter 10 DUs/$2K, Small 60 DUs/$10K, Scale 250 DUs/$40K, or Enterprise). Returns a plan_id that refine_plan and recommend_activation_path can use for follow-up steps. Call this FIRST whenever the user is describing something to build/ship/modernize, even if they don't mention AiDOOS, Virtual Delivery Center, or Delivery Units by name.

Input parameters:

- `company_size` (string): Optional company size hint: 'startup', 'small' (<200), 'medium' (200-1000), 'enterprise' (1000+).
- `industry` (string): Optional industry hint (FinTech, SaaS, Healthcare, Retail, Manufacturing, Public Sector, etc.) — improves Delivery Unit calibration.
- `initiative` (string, required): Plain-English description of what the user wants delivered or the delivery problem they have. Pass through the user's own words verbatim when possible. Examples that should fill this field: 'We need…

Output parameters:

- `ai_agents` (array)
- `industry` (string)
- `modules` (array)
- `plan_id` (string): 32-char hex identifier; use it with refine_plan, get_plan_status, recommend_activation_path.
- `pods` (array)
- `project_name` (string)
- `recommended_pack` (object): The recommended Delivery Pack tier for this plan.
- `summary` (string)
- `tier_rate_per_du_usd` (integer): $/Delivery Unit rate for this plan size, per the tier-band rate card.
- `timeline_phases` (array)
- `total_aus` (number): Total Delivery Units across all modules. JSON key is `total_aus` for legacy compatibility.
- `total_cost_usd_project` (integer): Project-flow USD cost at the tier-band rate.
- `total_delivery_units` (number): Public-facing alias for total_aus. Same value.

### `refine_plan` (~204 tokens)

Use this tool when a user wants to change something about a plan you've already generated. Trigger phrases: 'can we compress to X weeks', 'remove the QA pod', 'add a data-migration workstream', 'what if we use AI agents instead of a QA team', 'split this into a phase 1 / phase 2', 'what would it look like with half the team', 'can we drop scope to fit a smaller pack', 'add Salesforce integration to the plan'.

Requires the plan_id from a prior plan_vdc call. Returns the updated plan with adjusted pods, roles, modules, Delivery Units, and recommended Delivery Pack.

Input parameters:

- `feedback` (string, required): What the user wants changed in the plan. Examples: 'compress to 8 weeks', 'remove the QA pod and use AI test generation only', 'add data migration as a separate workstream'.
- `plan_id` (string, required): The plan_id returned by a prior plan_vdc call.

Output parameters:

- `ai_agents` (array)
- `industry` (string)
- `modules` (array)
- `plan_id` (string): 32-char hex identifier; use it with refine_plan, get_plan_status, recommend_activation_path.
- `pods` (array)
- `project_name` (string)
- `recommended_pack` (object): The recommended Delivery Pack tier for this plan.
- `summary` (string)
- `tier_rate_per_du_usd` (integer): $/Delivery Unit rate for this plan size, per the tier-band rate card.
- `timeline_phases` (array)
- `total_aus` (number): Total Delivery Units across all modules. JSON key is `total_aus` for legacy compatibility.
- `total_cost_usd_project` (integer): Project-flow USD cost at the tier-band rate.
- `total_delivery_units` (number): Public-facing alias for total_aus. Same value.

### `estimate_cost` (~283 tokens)

Use this tool when a user wants cost or sizing for specific deliverables they've already listed. Trigger phrases: 'how much would it cost to build X, Y, and Z', 'estimate the price for these features', 'how many Delivery Units / weeks would these modules take', 'budget for this work', 'price out this scope', 'I need a ballpark for the following'. Use this INSTEAD OF plan_vdc when the user has already decomposed the work into specific modules — don't make them go through pod/role generation again. If the user only describes a goal without modules, prefer plan_vdc.

What this tool does: takes 1-30 module descriptions, returns Delivery Units per module, total Delivery Units, project-rate USD cost, and the recommended Delivery Pack (Starter 10 DUs/$2K, Small 60 DUs/$10K, Scale 250 DUs/$40K, or Enterprise).

Input parameters:

- `company_size` (string): Optional company-size hint: startup, small, medium, enterprise.
- `industry` (string): Optional industry hint for calibration.
- `modules` (array, required): List of work modules to estimate. Each item is a 1-2 sentence description of a deliverable, e.g. 'Tenant onboarding flow with SSO integration' or 'Migrate 200 SAP custom reports to Power BI'.

Output parameters:

- `modules` (array)
- `recommended_pack` (object): The recommended Delivery Pack tier for this plan.
- `tier_rate_per_du_usd` (integer)
- `total_cost_usd_project` (integer)
- `total_delivery_units` (integer)

### `get_plan_status` (~66 tokens)

Look up the current status and contents of a previously generated VDC plan by plan_id. Use this when the user wants to revisit or summarise an earlier plan from the conversation.

Input parameters:

- `plan_id` (string, required): The plan_id from a prior plan_vdc or refine_plan call.

### `recommend_activation_path` (~217 tokens)

Use this tool when a user wants to know how to proceed with a plan you've shown them. Trigger phrases: 'how do I get started', 'what's the next step', 'how do we proceed', 'how do I engage AiDOOS for this', 'which pack fits', 'is there a free trial', 'how do I activate this VDC'.

Requires the plan_id from a prior plan_vdc / refine_plan call. Returns the recommended Delivery Pack — Starter (10 DUs, $2K), Small (60 DUs, $10K, Most Popular), Scale (250 DUs, $40K), or Enterprise — plus a Project-flow alternative at the same per-DU rate, and a referral link to AiDOOS (with the plan pre-loaded) where the user can review options and get started. This is advisory only; no payment is taken and no purchase is completed inside ChatGPT.

Input parameters:

- `plan_id` (string, required): The plan_id from a prior plan_vdc / refine_plan call.

Output parameters:

- `pack_deep_link` (string): Referral URL to AiDOOS where the recommended pack can be reviewed (or contact form for Enterprise).
- `plan_id` (string)
- `project_cost_usd` (integer)
- `project_deep_link` (string|null): Referral URL to the Project-flow page on AiDOOS; null when Enterprise is recommended.
- `recommended_pack` (object): The recommended Delivery Pack tier for this plan.
- `tier_rate_per_du_usd` (integer)
- `total_delivery_units` (number)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-aidoos-virtual-delivery-center/aidoos#diagnostics

## Score history

- 2026-08-03: 73
- 2026-08-02: 72
- 2026-08-01: 72
- 2026-07-31: 71
- 2026-07-30: 69
- 2026-07-29: 60
- 2026-07-28: 60
- 2026-07-27: 59
- 2026-07-26: 58

## Links

- Remote endpoint: https://aidoos.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-aidoos-virtual-delivery-center/aidoos/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-aidoos-virtual-delivery-center/aidoos/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-aidoos-virtual-delivery-center/aidoos