io.github.ariekogan/ateam-mcp
NPM · @ATEAM-AI/MCP · 2 COMPONENTS · SCANNED SEP 22
Build, validate, and deploy multi-agent AI solutions from any AI environment.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 10 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 876 tokens (~73/item across 12 items; 12 tools + 0 resources), lean.Pass
- 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
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "adas_deploy_solution" implies "deploy" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.ariekogan/ateam-mcp server?
io.github.ariekogan/ateam-mcp runs locally as an npm package, launched with npx -y @ateam-ai/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @ateam-ai/mcp
claude mcp add ariekogan-ateam-mcp -- npx -y @ateam-ai/mcp
{
"mcpServers": {
"ariekogan-ateam-mcp": {
"command": "npx",
"args": [
"-y",
"@ateam-ai/mcp"
]
}
}
} {
"servers": {
"ariekogan-ateam-mcp": {
"command": "npx",
"args": [
"-y",
"@ateam-ai/mcp"
]
}
}
} codex mcp add ariekogan-ateam-mcp -- npx -y @ateam-ai/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ariekogan-ateam-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@ateam-ai/mcp"
],
"enabled": true
}
}
} openclaw mcp add ariekogan-ateam-mcp --command npx --arg -y --arg @ateam-ai/mcp
mcp_servers:
ariekogan-ateam-mcp:
command: "npx"
args: ["-y", "@ateam-ai/mcp"] {
"McpServers": {
"ariekogan-ateam-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@ateam-ai/mcp"
]
}
}
} assistant mcp add ariekogan-ateam-mcp -t stdio -c npx -a -y @ateam-ai/mcp
{
"mcpServers": {
"ariekogan-ateam-mcp": {
"command": "npx",
"args": [
"-y",
"@ateam-ai/mcp"
]
}
}
} 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.
- 22 Sept 26 +1
- Stability: 0.97 → pass security
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Stability: pass → 0.80 functional
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 22 Sept 2026 · Analysed npm/@ateam-ai/mcp@0.1.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
adas_deploy_connector ~47
Deploy a connector — registers in the Skill Builder catalog and connects in ADAS Core.
| Name | Type | Req | Description |
|---|---|---|---|
| connector | object | yes | Connector metadata (id, name, transport, command, args) |
No output schema declared.
No examples provided.
adas_deploy_skill ~47
Deploy a single skill into an existing solution.
| Name | Type | Req | Description |
|---|---|---|---|
| skill | object | yes | Full skill definition |
| solution_id | string | yes | The existing solution ID to add the skill to |
No output schema declared.
No examples provided.
adas_deploy_solution ~125
Deploy a complete solution to ADAS Core — identity, connectors, skills. The Skill Builder auto-generates MCP servers from tool definitions. This is the main deployment action.
| Name | Type | Req | Description |
|---|---|---|---|
| connectors | array | – | Array of connector metadata (id, name, transport, command, args) |
| mcp_store | object | – | Optional: connector source code files. Key = connector id, value = array of {path, content} |
| skills | array | yes | Array of full skill definitions |
| solution | object | yes | Solution architecture — identity, grants, handoffs, routing |
No output schema declared.
No examples provided.
adas_get_examples ~83
Get complete working examples that pass validation. Study these before building your own.
| Name | Type | Req | Description |
|---|---|---|---|
| type | string | yes | Example type: 'skill' = Order Support Agent, 'connector' = stdio MCP connector, 'connector-ui' = UI-capable connector, 'solution' = full 3-skill e-commerce solution, 'index' = list all available exam… |
No output schema declared.
No examples provided.
adas_get_solution ~131
Read solution state — definition, skills, health, status, or export. Use this to inspect deployed solutions.
| Name | Type | Req | Description |
|---|---|---|---|
| skill_id | string | – | Optional: read a specific skill by ID (original or internal) |
| solution_id | string | yes | The solution ID |
| view | string | yes | What to read: 'definition' = full solution def, 'skills' = list skills, 'health' = live health check, 'status' = deploy status, 'export' = exportable bundle, 'validate' = re-validate from stored stat… |
No output schema declared.
No examples provided.
adas_get_spec ~85
Get the ADAS specification — schemas, validation rules, system tools, agent guides, and templates. Use this to understand how to build skills and solutions.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | yes | What to fetch: 'overview' = API overview + endpoints, 'skill' = full skill spec, 'solution' = full solution spec, 'enums' = all enum values |
No output schema declared.
No examples provided.
adas_list_solutions ~20
List all solutions deployed in the Skill Builder.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
adas_redeploy ~63
Re-deploy after making updates. Regenerates MCP servers and pushes to ADAS Core.
| Name | Type | Req | Description |
|---|---|---|---|
| skill_id | string | – | Optional: redeploy a single skill. Omit to redeploy all skills. |
| solution_id | string | yes | The solution ID |
No output schema declared.
No examples provided.
adas_solution_chat ~56
Send a message to the Solution Bot — an AI assistant that understands your deployed solution and can help with modifications.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | Your message to the Solution Bot |
| solution_id | string | yes | The solution ID |
No output schema declared.
No examples provided.
adas_update ~113
Update a deployed solution or skill incrementally using PATCH. Supports dot notation for scalar fields and _push/_delete/_update for arrays.
| Name | Type | Req | Description |
|---|---|---|---|
| skill_id | string | – | Required when target is 'skill' |
| solution_id | string | yes | The solution ID |
| target | string | yes | What to update: 'solution' or 'skill' |
| updates | object | yes | The update payload — use dot notation for scalars (e.g. 'problem.statement'), and tools_push/tools_delete/tools_update for array operations |
No output schema declared.
No examples provided.
adas_validate_skill ~45
Validate a skill definition through the 5-stage ADAS validation pipeline. Returns errors and suggestions to fix.
| Name | Type | Req | Description |
|---|---|---|---|
| skill | object | yes | The full skill definition object to validate |
No output schema declared.
No examples provided.
adas_validate_solution ~61
Validate a solution definition — cross-skill contracts, grant economy, handoffs, and LLM quality scoring.
| Name | Type | Req | Description |
|---|---|---|---|
| skills | array | – | Array of skill definitions included in the solution |
| solution | object | yes | The full solution definition object to validate |
No output schema declared.
No examples provided.
What is the io.github.ariekogan/ateam-mcp server?
io.github.ariekogan/ateam-mcp is listed in the public MCP registry as io.github.ariekogan/ateam-mcp. Build, validate, and deploy multi-agent AI solutions from any AI environment. This page covers its npm package (@ateam-ai/mcp).
Is the io.github.ariekogan/ateam-mcp server safe to use?
io.github.ariekogan/ateam-mcp scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 2026. It declares no install or post-install scripts. 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 io.github.ariekogan/ateam-mcp server expose?
io.github.ariekogan/ateam-mcp exposes 12 tools: adas_get_spec, adas_get_examples, adas_validate_skill, adas_validate_solution, adas_deploy_solution, and 7 more. Their descriptions and schemas cost roughly 876 tokens of context every time the server is loaded.
Is the io.github.ariekogan/ateam-mcp server still maintained?
io.github.ariekogan/ateam-mcp is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.ariekogan/ateam-mcp server under?
io.github.ariekogan/ateam-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.