MCP HeartbeatTHE MCP OBSERVATORY
Public workspace

Explore

Evidence for your next connection.

Independent measurements of remote MCP servers. Every observation has a timestamp.

Read-only probes

MCP server · Code & DevOps

AiDOOS Virtual Delivery Center

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

Checks passed
11 / 22

3 failed · 8 not measured

Median response
2684 ms

Median of successful probes over 7 days

30-day uptime
Not measured

Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.

Discovered tools
5

Tool definitions returned by this server

Independent monitoring

Health & checks

Status history

Responded

The server completed its last measured handshake. This is an observation, not a guarantee.

Last checked
Check summary by test group
Test areaPassedFailedUnmeasured
ConnectionCan a client connect and discover tools?
500
Reliability & speedDoes it respond consistently and quickly?
004
Access & authenticationWhat is required to use this server?
102
Tool qualityAre the tool definitions usable by an agent?
400
Publisher identityCan the publisher be traced to its source?
132

Unmeasured means there is not enough evidence to decide. How these checks work

Inspect individual checks 22 recorded

Core

  • Pass
    Reachable

    Latest probe returned HTTP 200 in 2684 ms.

  • Pass
    Valid handshake

    protocolVersion 2025-06-18, serverInfo.name AiDOOS Virtual Delivery Center.

  • Pass
    Lists tools

    tools/list returned 5 tools.

  • Pass
    Current protocol

    Negotiated 2025-06-18. The bar is 2025-06-18 or newer.

  • Pass
    HTTPS

    The endpoint URL is https.

Performance

  • Not measured
    Fast (p50)

    Median latency 2684 ms over 1 samples in 7 days. The bar is 1000 ms. Need at least 5 samples.

  • Not measured
    Consistent (p95)

    95th percentile 2684 ms over 1 samples in 7 days. The bar is 3000 ms. Need at least 20 samples.

  • Not measured
    Reliable (uptime)

    1 of 1 attempts returned a tool list in 30 days (100%). The bar is 99%. Need at least 30 samples.

  • Not measured
    Stable tool list

    Fewer than two successful probes in 30 days, so tool-list stability is not measured.

Access

  • Pass
    Open access

    tools/list succeeded with no credential, and the record declares none.

  • Not measured
    Standard auth

    Auth is not required, so the OAuth metadata check does not apply.

  • Not measured
    Free tier cited

    No publisher quote has been checked.

Tools

  • Pass
    Tools described

    Every tool description is at least 20 characters.

  • Pass
    Valid input schemas

    Every inputSchema is a JSON Schema object.

  • Pass
    Parameters documented

    10 of 10 parameters have a description (100%). The bar is 80%.

  • Pass
    Safety hints

    Every tool sets readOnlyHint or destructiveHint.

Publisher

  • Pass
    Verified namespace

    Listed in the Official MCP Registry.

  • Fail
    Website matches publisher

    The website host does not match the reverse-domain namespace.

  • Fail
    Source repo linked

    No repository URL is on file.

  • Not measured
    Repo owner matches

    This namespace is not an io.github login, so the owner comparison does not apply.

  • Fail
    Recently updated

    Updated 2026-05-08T05:54:39.336045Z, which is older than 180 days.

  • Not measured
    Open-source licence

    No GitHub repository to ask about a licence.

Start using AiDOOS Virtual Delivery Center

Connect to this server

Choose your client, copy the configuration, then enable the server in your client’s MCP settings.

Run this command in your terminal, then restart Claude Code.

Claude Code

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

Capabilities

Tools 5

create_delivery_plan

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.

Discovered
estimate_delivery_cost

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.

Discovered
get_delivery_plan

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.

Discovered
recommend_next_step

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.

Discovered
refine_delivery_plan

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.

Discovered

Recent measurements

Probe history

View status
Latest stored probes. Raw probe rows are kept for 14 days.
CheckedResultResponseTools
Connected2684 ms5