Is the Ariekogan Ateam MCP server down?

mcp-registry/io.github.ariekogan/ateam-mcp · v0.4.92

Also listed as awesome/ariekogan/ateam-mcp

up · requires sign-in
Last checked 2026-10-25 20:22 UTC · handshake 537ms

As of 2026-10-25 20:22 UTC, the Ariekogan Ateam MCP server is up (it requires sign-in) with a Glimind reliability score of 87/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 22 outages in 90 days, with a median recovery of 2 minutes.

uptime (30d checks)
100%
checks observed
191
outages (90d)
22
tools
71

Build, validate, and deploy multi-agent AI solutions from any AI environment.

Install Ariekogan Ateam MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http ariekogan-ateam-mcp-server https://mcp.ateam-ai.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "ariekogan-ateam-mcp-server": {
      "type": "http",
      "url": "https://mcp.ateam-ai.com/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (70/100)

C (70/100): 0 error(s), 5 warning(s) across 59 tool(s); ~17,910 tokens of tool definitions.
Scores higher than 4% of 15,722 MCP servers Glimind has audited.
Its tool list costs an agent ~17,910 tokens per session — more than 95% of servers.
70 → 70 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints8
Token cost24
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (7)

1 tool definition(s) exceed ~1,200 tokens each (largest: ateam_get_spec, ~1,239).

Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~639 tokens every session. How to fix →

Tools: ateam_get_spec · saves ~639 tokens/session

59 of 59 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: ateam_auth, ateam_bootstrap, ateam_build_and_run, ateam_chain_status, ateam_connector_logs and 54 more

59 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.

Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →

9 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: ateam_build_and_run, ateam_create_connector, ateam_create_plugin, ateam_delete_connector, ateam_delete_skill and 4 more

Loading this server's tool list costs an agent ~17,910 tokens before any work — more than 95% of MCP servers.

Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Requires authentication (Bearer); tool definitions could not be read anonymously.

If discovery should be public, allow initialize + tools/list without credentials and gate only tools/call. Directories and routers can then list your tools.

Auto-fix: 32 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.ariekogan%2Fateam-mcp/fixes

ateam_build_and_run 1 change
{
  "name": "ateam_build_and_run",
  "description": "DEPLOY THE CURRENT MAIN BRANCH TO A-TEAM CORE. ⚠️ HEAVIEST OPERATION (60-180s): validates solution+skills → deploys all connectors+skills to Core (regenerates MCP servers) → health-checks → optionally runs a warm test → auto-pushes to GitHub.\n\n🌳 DEV/PROD WORKFLOW:\n  1. Edit files → ateam_github_patch (writes to `dev` branch by default)\n  2. (Optional) Preview what's about to ship → ateam_github_diff\n  3. Ship dev → main → ateam_github_promote (merges + auto-tags `prod-YYYY-MM-DD-NNN`)\n  4. Depl",
  "inputSchema": {
    "type": "object",
    "required": [],
    "properties": {
      "github": {
        "type": "boolean",
        "description": "Optional: if true, pull connector source code from main. AUTO-DETECTED: if you omit both mcp_store and github, the system checks if a repo exists and pulls from main automatically."
      },
      "skills": {
        "type": "array",
        "items": {
          "type": "object"
        },
        "description": "Optional after first deploy: skill definitions. If omitted, auto-pulled from main (skills/{id}/skill.json)."
      },
      "solution": {
        "type": "object",
        "description": "Full solution definition. Required on first deploy. After first deploy, just pass solution_id instead — everything is auto-pulled from GitHub main."
      },
      "mcp_store": {
        "type": "object",
        "description": "Optional: connector source code files. Key = connector id, value = array of {path, content}."
      },
      "connectors": {
        "type": "array",
        "items": {
          "type": "object"
        },
        "description": "Optional: connector metadata (id, name, transport). Entry points auto-detected from mcp_store."
      },
      "solution_id": {
        "type": "string",
        "description": "The solution ID. Use this INSTEAD of passing the full solution object — the solution definition is auto-pulled from main. Required if solution object is omitted."
      },
      "test_message": {
        "type": "string",
        "description": "Optional: send a test message after deployment to verify the skill works. Returns the full execution result."
      },
      "test_skill_id": {
        "type": "string",
        "description": "Optional: which skill to test (defaults to the first skill)."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
ateam_chain_status 1 change
{
  "name": "ateam_chain_status",
  "description": "SLIM chain status — the chip-quick poll. Given a chain_id (from ateam_conversation), returns the WHOLE-CHAIN aggregate status cheaply: chain_status + chain_done (true only when the ENTIRE chain — root job + every handoff + askAnySkill subcall — is terminal), plus pending_question, result, and a short progress line.\n\nThis is what you poll on a loop after ateam_conversation — NOT ateam_get_chain (that returns the full tree; too heavy for periodic polling). A single job can finish while the chain i",
  "inputSchema": {
    "type": "object",
    "required": [
      "chain_id"
    ],
    "properties": {
      "job_id": {
        "type": "string",
        "description": "Alias for chain_id — any job in the chain resolves to the chain aggregate. The handler has always accepted it; without this declaration MCP stripped it before the handler could see it."
      },
      "actor_id": {
        "type": "string",
        "description": "Optional. WHO is asking. A job belongs to an actor and Core enforces that on per-job reads, so a tenant key alone is refused. Usually unnecessary — the session remembers the actor from ateam_conversation/ateam_test_skill. Pass it to inspect a job run by a DIFFERENT actor (e.g. a real user's)."
      },
      "chain_id": {
        "type": "string",
        "description": "The chain id returned by ateam_conversation (the conversation's identity). Any job id in the chain also works — Core resolves the chain aggregate."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
ateam_create_connector 1 change
{
  "name": "ateam_create_connector",
  "description": "Scaffold a new MCP connector with server.js + package.json + README. Eliminates ~50% of identical boilerplate (MCP server setup, tool registration, stdio transport). You then fill in the tool implementations. Set ui_capable=true to include ui.listPlugins / ui.getPlugin stubs (plugin source files added separately via ateam_create_plugin). After scaffolding, the files are uploaded to Core via the same path as ateam_upload_connector.",
  "inputSchema": {
    "type": "object",
    "required": [
      "solution_id",
      "connector_id"
    ],
    "properties": {
      "name": {
        "type": "string",
        "description": "Human-readable name for the connector (e.g. 'Hue Lights'). Defaults to connector_id."
      },
      "ui_capable": {
        "type": "boolean",
        "description": "If true, include ui.listPlugins/ui.getPlugin handler stubs. Default: false."
      },
      "solution_id": {
        "type": "string",
        "description": "The solution ID"
      },
      "connector_id": {
        "type": "string",
        "description": "Connector ID (lowercase-with-dashes, no spaces). Becomes the directory name."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.ariekogan/ateam-mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.ariekogan/ateam-mcp"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.ariekogan%2Fateam-mcp.svg)](https://glimind.com/server/mcp-registry%2Fio.github.ariekogan%2Fateam-mcp?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.ariekogan%2Fateam-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.ariekogan%2Fateam-mcp.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.ariekogan%2Fateam-mcp.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.ariekogan%2Fateam-mcp?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:5a1278cc46bf128c…, first seen 2026-10-17, included at leaf 14362 of 68,466. Version history · verify what your client received.

Tools (71)

Compare: most reliable devops servers · most reliable knowledge servers · most reliable ml servers · most reliable code servers · most reliable security servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Ariekogan Ateam MCP server down right now?

As of 2026-10-25 20:22 UTC, the Ariekogan Ateam MCP server is up (it requires sign-in) with a Glimind reliability score of 87/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 22 outages in 90 days, with a median recovery of 2 minutes.

How many tools does Ariekogan Ateam MCP server provide?

Ariekogan Ateam MCP server advertises 71 tools, including adas_deploy_connector, adas_deploy_skill, adas_deploy_solution, adas_get_examples, adas_get_solution.

How do I install Ariekogan Ateam MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.ateam-ai.com/mcp

Is the Ariekogan Ateam MCP server safe to connect to an AI agent?

Glimind scanned all 59 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Ariekogan Ateam MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve