AiDOOS Virtual Delivery Center
REMOTE · AIDOOS.COM · SCANNED SEP 24
Plan a Virtual Delivery Center for any initiative: pods, roles, AI agents, Delivery Units.
Available components
Recent critical change
Authorization (25 Aug 2026). See the changelog before you install this server.
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (refine_delivery_plan). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 902 tokens (~128/item across 7 items; 5 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities73
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
- Supports UI / widget rendering.Pass
How do I install the AiDOOS Virtual Delivery Center MCP server?
AiDOOS Virtual Delivery Center is a hosted endpoint at https://aidoos.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · aidoos.com
claude mcp add --transport http com-aidoos-virtual-delivery-center 'https://aidoos.com/mcp'
{
"mcpServers": {
"com-aidoos-virtual-delivery-center": {
"url": "https://aidoos.com/mcp"
}
}
} {
"servers": {
"com-aidoos-virtual-delivery-center": {
"type": "http",
"url": "https://aidoos.com/mcp"
}
}
} [mcp_servers.com-aidoos-virtual-delivery-center] url = "https://aidoos.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-aidoos-virtual-delivery-center": {
"type": "remote",
"url": "https://aidoos.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-aidoos-virtual-delivery-center --url 'https://aidoos.com/mcp' --transport streamable-http
mcp_servers:
com-aidoos-virtual-delivery-center:
url: "https://aidoos.com/mcp" {
"McpServers": {
"com-aidoos-virtual-delivery-center": {
"Transport": "http",
"Url": "https://aidoos.com/mcp"
}
}
} assistant mcp add com-aidoos-virtual-delivery-center -t streamable-http -u 'https://aidoos.com/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 24 Sept 26 +14
- Stability: fail → pass ▲ security
- 26 Aug 26 65
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Authorization: partial → fail ▼ critical
- Stability: 0.97 → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “estimate_cost” was removed ▼ security
- Tool “get_plan_status” was removed ▼ security
- Tool “plan_vdc” was removed ▼ security
- Tool “recommend_activation_path” was removed ▼ security
- Tool “refine_plan” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- New tool “refine_delivery_plan”, which the server declares destructive security
- Schema quality: 199 → 128 ▲ functional
- New tool “create_delivery_plan” functional
- New tool “estimate_delivery_cost” functional
- New tool “get_delivery_plan” functional
- New tool “recommend_next_step” functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Probed https://aidoos.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=aidoos.com | CN=YE2,O=Let's Encrypt,C=US | 25 Jul 2026 | 23 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 5b07f3b33b0bdc59780e65efbcedbb29ac5 |
| SANs: aidoos.com, www.aidoos.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of aidoos.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| aidoos.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://aidoos.com/mcp | Verified | 200 | |
| http (plaintext) | http://aidoos.com/mcp | HTTPS enforced | 301 | https://aidoos.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_delivery_plan ~243
Create a structured delivery plan for an initiative the user describes. Given a plain-language description of something to build, implement, modernize, migrate, or scale, this returns a plan with teams (pods), roles, AI agents, work modules sized in Delivery Units, a phased timeline, and a recommended plan size. Use this tool when a user describes a project or initiative and wants to understand the team, scope, timeline, or cost to deliver it. Returns a plan_id that the other tools use to reference this plan.
| Name | Type | Req | Description |
|---|---|---|---|
| company_size | string | – | Optional company size hint: 'startup', 'small' (<200), 'medium' (200-1000), 'enterprise' (1000+). |
| industry | string | – | Optional industry hint (for example FinTech, SaaS, Healthcare, Retail, Manufacturing, or Public Sector). Improves sizing accuracy. |
| initiative | string | yes | A plain-language description of what the user wants to build, implement, modernize, migrate, or scale. Pass through the user's own words when possible. For example: 'Build a customer portal in 12 wee… |
| Name | Type | Req | Description |
|---|---|---|---|
| ai_agents | array | – | – |
| industry | string | – | – |
| modules | array | yes | – |
| plan_id | string | yes | Identifier for this plan; use it with refine_delivery_plan, get_delivery_plan, or recommend_next_step. |
| pods | array | yes | – |
| project_name | string | yes | – |
| recommended_pack | object | yes | The recommended Delivery Pack tier for this plan. |
| summary | string | yes | – |
| 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 | yes | Public-facing alias for total_aus. Same value. |
No examples provided.
estimate_delivery_cost ~171
Estimate the size and cost of a specific list of work items. Given short descriptions of deliverables, this returns each item sized in Delivery Units, a total, an indicative cost, and a recommended plan size. Use this tool when the user has already broken the work into specific items and wants sizing. When the user describes an overall goal without a breakdown, use create_delivery_plan instead.
| Name | Type | Req | Description |
|---|---|---|---|
| company_size | string | – | Optional company-size hint: startup, small, medium, enterprise. |
| industry | string | – | Optional industry hint for calibration. |
| modules | array | yes | 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'. |
| Name | Type | Req | Description |
|---|---|---|---|
| modules | array | yes | – |
| recommended_pack | object | yes | The recommended Delivery Pack tier for this plan. |
| tier_rate_per_du_usd | integer | – | – |
| total_cost_usd_project | integer | – | – |
| total_delivery_units | integer | yes | – |
No examples provided.
get_delivery_plan ~70
Retrieve a previously created delivery plan by its plan_id. Returns the plan's current status and contents. Use this tool when the user wants to revisit or summarize a plan created earlier in the conversation.
| Name | Type | Req | Description |
|---|---|---|---|
| plan_id | string | yes | The plan_id from a prior create_delivery_plan or refine_delivery_plan call. |
Structured output declared, but exposes no named fields.
No examples provided.
recommend_next_step ~125
Summarize how to proceed with a delivery plan. Given a plan_id, this returns the plan size, an indicative cost, the available plan tiers, and referral links to the AiDOOS website where the user can review options and get started. Use this tool when the user asks how to proceed or what the next step is for a plan created earlier in the conversation. This tool is advisory only: it does not take payment or complete any purchase inside ChatGPT.
| Name | Type | Req | Description |
|---|---|---|---|
| plan_id | string | yes | The plan_id from a prior create_delivery_plan / refine_delivery_plan call. |
| Name | Type | Req | Description |
|---|---|---|---|
| pack_deep_link | string | yes | Referral URL to AiDOOS where the recommended pack can be reviewed (or contact form for Enterprise). |
| plan_id | string | yes | – |
| 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 | yes | The recommended Delivery Pack tier for this plan. |
| tier_rate_per_du_usd | integer | – | – |
| total_delivery_units | number | yes | – |
No examples provided.
refine_delivery_plan ~142
Revise an existing delivery plan based on the user's requested changes. Given a plan_id and instructions such as adjusting the timeline, adding or removing scope, or changing the team composition, this returns the updated plan and replaces the stored plan with the revised version. Use this tool when the user wants to modify a plan created earlier in the conversation.
| Name | Type | Req | Description |
|---|---|---|---|
| feedback | string | yes | 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 | yes | The plan_id returned by a prior create_delivery_plan call. |
| Name | Type | Req | Description |
|---|---|---|---|
| ai_agents | array | – | – |
| industry | string | – | – |
| modules | array | yes | – |
| plan_id | string | yes | Identifier for this plan; use it with refine_delivery_plan, get_delivery_plan, or recommend_next_step. |
| pods | array | yes | – |
| project_name | string | yes | – |
| recommended_pack | object | yes | The recommended Delivery Pack tier for this plan. |
| summary | string | yes | – |
| 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 | yes | Public-facing alias for total_aus. Same value. |
No examples provided.
What is the AiDOOS Virtual Delivery Center MCP server?
AiDOOS Virtual Delivery Center is an MCP server listed in the public MCP registry as com.aidoos/virtual-delivery-center. Plan a Virtual Delivery Center for any initiative: pods, roles, AI agents, Delivery Units. This page covers its hosted endpoint (https://aidoos.com/mcp).
Is the AiDOOS Virtual Delivery Center MCP server safe to use?
AiDOOS Virtual Delivery Center scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the AiDOOS Virtual Delivery Center MCP server expose?
AiDOOS Virtual Delivery Center exposes 5 tools: create_delivery_plan, refine_delivery_plan, estimate_delivery_cost, get_delivery_plan, recommend_next_step. Their descriptions and schemas cost roughly 751 tokens of context every time the server is loaded.
Does the AiDOOS Virtual Delivery Center MCP server require authentication?
No. We connected to AiDOOS Virtual Delivery Center without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AiDOOS Virtual Delivery Center MCP server still maintained?
AiDOOS Virtual Delivery Center is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.