MCP servers › com.copado › agentia-cli
MCP server · registry snapshot 2026-11-19 · last checked 2026-11-19
agentia-cli MCP server
Registry name com.copado/agentia-cli
Copado Agentia — the publisher's title
by copado.com · domain (the registry's namespace rule)repository owner on GitHub: CopadoSolutions (organization)Source ↗npm ↗Website ↗
Run Copado DevOps tasks from MCP-capable AI agents through the Agentia CLI local MCP server. — the publisher's description
Summary
com.copado/agentia-cli is a local MCP server listed in the official MCP registry at version 1.13.0, under the namespace of the domain copado.com. Its linked repository is github.com/CopadoSolutions/agentia-cli-mcp; GitHub reports its owner as CopadoSolutions, an organization.
Record checks
- met: Registry entry is active and says how to run it
- met: Source repository link opens
- met: Repository is not archived
- met: Code pushed to the repository in the 90 days before our check
- met: Repository publishes a security policy (SECURITY.md)
- not met: Package names its licence with a standard (SPDX) identifier
- met: The version the registry lists can be installed and is not withdrawn
- not met: npm package carries build provenance (attestation)
- met: No known critical or high advisory in the package or its dependencies
- #396 of 20,610 packages by monthly downloads
- Not ranked by stars: 0 stars (ranked from 10)
From public records, not a safety rating. Each check with its reason · Is it safe to install?
Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it
Key facts
- Runs
- local package
- Transport
- standard input/output
- Your own values
- none declared (not a guarantee)
- Package
- npm · listed version behind the latest release
- Dependencies
- no known high or critical advisories
- Repository
- public
- Last tested
- not tested
Tool list
Not read: It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's. So there is no tool-list size and no result from the three APIs.
Worth knowing before you connect it
- The registry lists 1.13.0; 1.14.0 is newer (1 release).
Each line comes from a section below, with its source and date.
How fresh this is
- Live-tested
- no
- Last tested
- not tested
- Latest version
- 1.13.0, published 2026-11-18 (registry, as of the 2026-11-19 snapshot)
- First listed version
- 2026-11-16 (earliest version still in the registry; older removed versions would be earlier)
- Version history
- 4 versions listed, 2026-11-16 to 2026-11-18; 4 in the 90 days before the 2026-11-19 snapshot.(versions still listed in the registry only)
Most recent 4 versions
1.13.0· 2026-11-181.12.0· 2026-11-181.11.0· 2026-11-171.10.0· 2026-11-16
- Registry data
- snapshot 2026-11-19
- Package and repository
- checked 2026-11-19
Dead or stale signals
None found in the records we hold
Looked for and not found: deprecated in the registry; listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.
Changes since the last refresh
Version 1.11.0 (published 2026-11-17) → 1.13.0 (published 2026-11-18), between the registry lists of 2026-11-18 and 2026-11-19.
The publisher published no GitHub release note for this version: its repository publishes no GitHub releases.
Source: the official MCP Registry list on 2026-11-18 and on 2026-11-19; release notes from the GitHub Releases API, checked 2026-11-19.
What it is
How do I add it to my client?
Config from the registry entry
From the npm package @copado/agentia-cli
Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.
Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)
{
"mcpServers": {
"agentia-cli": {
"command": "npx",
"args": [
"-y",
"@copado/agentia-cli@1.13.0",
"mcp",
"start"
]
}
}
}Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"agentia-cli": {
"command": "npx",
"args": [
"-y",
"@copado/agentia-cli@1.13.0",
"mcp",
"start"
]
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"agentia-cli": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@copado/agentia-cli@1.13.0",
"mcp",
"start"
]
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"agentia-cli","type":"stdio","command":"npx","args":["-y","@copado/agentia-cli@1.13.0","mcp","start"]}'Claude Code
claude mcp add --transport stdio agentia-cli -- npx -y @copado/agentia-cli@1.13.0 mcp start
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
"mcpServers": {
"agentia-cli": {
"command": "npx",
"args": [
"-y",
"@copado/agentia-cli@1.13.0",
"mcp",
"start"
],
"disabled": false,
"autoApprove": []
}
}
}Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
"mcpServers": {
"agentia-cli": {
"command": "npx",
"args": [
"-y",
"@copado/agentia-cli@1.13.0",
"mcp",
"start"
]
}
}
}OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.agentia-cli] command = "npx" args = ["-y", "@copado/agentia-cli@1.13.0", "mcp", "start"]
Zed · Zed settings file (command: zed: open settings file)
{
"context_servers": {
"agentia-cli": {
"command": "npx",
"args": [
"-y",
"@copado/agentia-cli@1.13.0",
"mcp",
"start"
]
}
}
}Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 -- npx -y @copado/agentia-cli@1.13.0 mcp start
- Arguments are written as the registry entry gives them; a named one as “--name value”, the form the registry documentation shows.
- This runs the publisher's code on your machine (npx). Read its README first.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
Can it be installed, and is it up to date?
Version pin · advisories
Listed version
- Registry lists
- 1.13.0
- Latest stable
- 1.14.0
- Status
- behind the latest release (1 releases, 1 days)
- Withdrawn
- no
Source: registry.npmjs.org · 2026-11-19. About the version the registry lists; a manual install may resolve to a different one.
Dependency advisories
Counted in the full dependency tree as resolved on 2026-11-19 (npm audit; each bar counts packages with an advisory, not advisories). Bars share one scale. The package itself has no known vulnerability (OSV.dev).
Integrity, provenance, license
- Integrity
- sha512-JSaFJjw0KH5N75k1X…
- Signature
- signed
Source: the package registry · 2026-11-19.
Usage
- Downloads
- 7,786 in the last month
Source: api.npmjs.org · 2026-11-19.
What do the published files and outside lists say?
Read as text · nothing run · no tool called
Package files
- Install-time script (npm). No install-time script in the published package.json (version 1.13.0). Source: read 2026-11-19.
- Operating systems and processors (npm). The npm package sets no os or cpu limit (package.json). Source: read 2026-11-19.
- Node.js version (npm). Needs Node 22 or later (engines.node
>=22.22.2). Source: read 2026-11-19. - MCP SDK in the package files. Lists
@modelcontextprotocol/sdkas a dependency (package.json). Source: read 2026-11-19. - Build workflow. No build provenance published for this version. Source: read 2026-11-19.
Registry entry
- Same package in other registry entries. No other registry entry lists this entry's npm or PyPI package at a newer version. Source: own registry snapshot · read 2026-11-19.
Outside lists
- CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-19. This product uses the NVD API but is not endorsed or certified by the NVD.
- GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-19. GitHub Advisory Database, CC BY 4.0
- Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-19. Source: read 2026-11-19.
- Cline marketplace. Not in the Cline marketplace on 2026-11-19. Source: read 2026-11-19.
Own host
- security.txt. No security.txt at https://developer.copado.com/.well-known/ (HTTP 404, 2026-11-19). Source: developer.copado.com/.well-known/security.txt · read 2026-11-19.
- A2A agent card. No A2A agent card at https://developer.copado.com/.well-known/ (HTTP 404, 2026-11-19). Source: developer.copado.com/.well-known/agent-card.json · read 2026-11-19.
Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read
Does the registry listing match what we found?
Feature #6The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Version 1.13.0 on npm | Exists and can be installed | matches | npm · 2026-11-19 |
| Repository github.com/CopadoSolutions/agentia-cli-mcp | Opens publicly | matches | api.github.com · 2026-11-19 |
Who made it?
Feature #7 · lineage
Facts about the publisher. We do not turn them into a trust score.
- Namespace
- com.copado
- GitHub owner
- an organization (CopadoSolutions)
- Build record
- signed
- Repository
- github.com/CopadoSolutions/agentia-cli-mcp
- Stars
- 0
- Repository age
- 0–30 days
- Last push
- 0–30 days ago
- Archived
- no
- Security policy
- SECURITY.md
Source: the registry entry and api.github.com · 2026-11-19; security policy read from GitHub · 2026-11-17.
Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.
Choosing
Record checks
Public records · not a safety rating7 of 9 record checks met
- #396 of 20,610 packages by monthly downloads
- Not ranked by stars: 0 stars (ranked from 10)
- MetRegistry entry is active and says how to run itActive, with a package or a remote address.
- MetSource repository link opensThe linked GitHub repository is public.
- MetRepository is not archivedNot archived.
- MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
- MetRepository publishes a security policy (SECURITY.md)SECURITY.md found.
- Not metPackage names its licence with a standard (SPDX) identifierA licence is mentioned, but not as a standard identifier (for example "SEE LICENSE IN …").What changes this check: For an npm package, the documentation describes naming the licence in the license field of package.json with a current SPDX license identifier. npm: package.json license field
- MetThe version the registry lists can be installed and is not withdrawnThe listed version exists; a newer one is out.
- Not metnpm package carries build provenance (attestation)Signed by npm, but no build attestation.What changes this check: npm's documentation describes publishing with provenance from a cloud-hosted runner of a supported CI/CD provider, using npm CLI 9.5.0 or newer and npm publish --provenance. npm: generating provenance statements
- MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-19 (security policy 2026-11-17). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral
Common questions about com.copado/agentia-cli
Answered from the data aboveWho publishes com.copado/agentia-cli?
The registry ties the namespace com.copado to the domain copado.com; only its owner can publish under it. Its linked repository is github.com/CopadoSolutions/agentia-cli-mcp; GitHub reports its owner as CopadoSolutions, an organization. These are facts from the registry and GitHub, not a rating.
Is com.copado/agentia-cli safe to install?
We do not rate servers as safe or unsafe. 7 of its 9 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. A newer stable release exists than the one listed. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has packages with advisories (38 moderate; npm audit). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.
Has com.copado/agentia-cli been security tested?
No. It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's.
Does com.copado/agentia-cli publish a security policy?
Yes: its repository has a public security policy (github.com/copadosolutions/agentia-cli-mcp/blob/HEAD/SECURITY.md). That is the publisher's statement, not permission for us to test the server, and we call none of its tools.
Is the listed version current?
No. The registry lists 1.13.0; the latest stable release on npm is 1.14.0.
Where is the source code of com.copado/agentia-cli?
In github.com/CopadoSolutions/agentia-cli-mcp, which opens publicly.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
Has it been tested?
Feature #1It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's. — our limit
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “com.copado/agentia-cli: MCP server record.” Data checked 2026-11-19. https://protocolprobe.com/mcp/servers/com.copado/agentia-cli
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/com.copado/agentia-cli)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).
Write to hello@protocolprobe.com · corrections log · methodology