io.github.b1ff/atlassian-dc-mcp-confluence
NPM · @ATLASSIAN-DC-MCP/CONFLUENCE · SCANNED SEP 20
MCP server for Atlassian Confluence Data Center - access and manage content
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 Security99
- 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
- 33 of 129 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency84
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to b1ff/atlassian-dc-mcp). View diagnostics → Pass
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 17 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
- Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →
How do I install the io.github.b1ff/atlassian-dc-mcp-confluence server?
io.github.b1ff/atlassian-dc-mcp-confluence runs locally as an npm package, launched with npx -y @atlassian-dc-mcp/confluence. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @atlassian-dc-mcp/confluence
claude mcp add b1ff-atlassian-dc-mcp-confluence -- npx -y @atlassian-dc-mcp/confluence
{
"mcpServers": {
"b1ff-atlassian-dc-mcp-confluence": {
"command": "npx",
"args": [
"-y",
"@atlassian-dc-mcp/confluence"
]
}
}
} {
"servers": {
"b1ff-atlassian-dc-mcp-confluence": {
"command": "npx",
"args": [
"-y",
"@atlassian-dc-mcp/confluence"
]
}
}
} codex mcp add b1ff-atlassian-dc-mcp-confluence -- npx -y @atlassian-dc-mcp/confluence
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"b1ff-atlassian-dc-mcp-confluence": {
"type": "local",
"command": [
"npx",
"-y",
"@atlassian-dc-mcp/confluence"
],
"enabled": true
}
}
} openclaw mcp add b1ff-atlassian-dc-mcp-confluence --command npx --arg -y --arg @atlassian-dc-mcp/confluence
mcp_servers:
b1ff-atlassian-dc-mcp-confluence:
command: "npx"
args: ["-y", "@atlassian-dc-mcp/confluence"] {
"McpServers": {
"b1ff-atlassian-dc-mcp-confluence": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@atlassian-dc-mcp/confluence"
]
}
}
} assistant mcp add b1ff-atlassian-dc-mcp-confluence -t stdio -c npx -a -y @atlassian-dc-mcp/confluence
{
"mcpServers": {
"b1ff-atlassian-dc-mcp-confluence": {
"command": "npx",
"args": [
"-y",
"@atlassian-dc-mcp/confluence"
]
}
}
} 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.
- 18 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 17 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 5 Sept 26 −1
No change was recorded against any check on this day. Supply Chain Security went from 99 to 98.
- 3 Sept 26 0
- Stability: Stability not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to compare. security
- Tool safety: Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool text to scan. security
- Schema quality: Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to assess. functional
- Capabilities: Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we never saw its MCP handshake. functional
- Tool coverage: Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool definitions to assess. functional
- 2 Sept 26 0
- Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
- Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Package version: 0.33.0 → 0.34.0 functional
- 30 Aug 26 0
- Known CVEs: pass → partial ▼ security
- Security disclosure: unverified → fail ▼ functional
- Dependency health: 0.89 → partial functional
- Package version: 0.29.0 → 0.33.0 functional
- Package version: 0.29.0 → 0.32.0 functional
- 29 Aug 26 0
- Security disclosure: fail → unverified ▼ functional
- 26 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
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 20 Sept 2026 · Analysed npm/@atlassian-dc-mcp/confluence@0.34.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | b1ff/atlassian-dc-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/b1ff/atlassian-dc-mcp/.github/workflows/npm-publish.yml@refs/heads/master |
| Rekor log index | 2690904390 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:0dae76ded7e7c0ef1e736536e52bf0c829e719a453e4dcb230b7b05c5856d86dfa2ea1091cf49a53a6b96a03a91d9509424b58c90533c94804ef710e4 |
Background: How many MCP packages publish verified provenance →
Dependencies 129 packages
| Packages resolved | 129 |
|---|---|
| Stale | 33 |
| 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 →
Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.
What is the io.github.b1ff/atlassian-dc-mcp-confluence server?
io.github.b1ff/atlassian-dc-mcp-confluence is listed in the public MCP registry as io.github.b1ff/atlassian-dc-mcp-confluence. MCP server for Atlassian Confluence Data Center - access and manage content. This page covers its npm package (@atlassian-dc-mcp/confluence).
Is the io.github.b1ff/atlassian-dc-mcp-confluence server safe to use?
io.github.b1ff/atlassian-dc-mcp-confluence scores 47 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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.
Is the io.github.b1ff/atlassian-dc-mcp-confluence server still maintained?
io.github.b1ff/atlassian-dc-mcp-confluence is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.