Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.artifacta/mcp

NPM · @ARTIFACTA-MCP/MCP · 3 COMPONENTS · SCANNED SEP 20

Artifact store for AI agents. Hosted OAuth at mcp.artifacta.io/mcp; local stdio via npm/PyPI.

0 this week 80 Trust /100
Trust breakdown (7 categories)

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 97 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability78
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1582 tokens (~143/item across 11 items; 10 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 14% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "publish_artifact" implies "publish" 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 11 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
Install

How do I install the io.artifacta/mcp server?

io.artifacta/mcp runs locally as an npm package, launched with npx -y @artifacta-mcp/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 · @artifacta-mcp/mcp

# add to Claude Code
claude mcp add io-artifacta-mcp -- npx -y @artifacta-mcp/mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "io-artifacta-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@artifacta-mcp/mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "io-artifacta-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@artifacta-mcp/mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add io-artifacta-mcp -- npx -y @artifacta-mcp/mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-artifacta-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@artifacta-mcp/mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add io-artifacta-mcp --command npx --arg -y --arg @artifacta-mcp/mcp
# ~/.hermes/config.yaml
mcp_servers:
  io-artifacta-mcp:
    command: "npx"
    args: ["-y", "@artifacta-mcp/mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "io-artifacta-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@artifacta-mcp/mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add io-artifacta-mcp -t stdio -c npx -a -y @artifacta-mcp/mcp
// mcp.json
{
  "mcpServers": {
    "io-artifacta-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@artifacta-mcp/mcp"
      ]
    }
  }
}
Changelog

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.

  • 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
    • Security disclosure: unverified → fail functional
    • Stability: pass → 0.80 functional
  • 15 Sept 26 +1
    • Stability: 0.97 → pass security
    • Security disclosure: fail → unverified functional
  • 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.

  • 10 Sept 26 0
    • Security disclosure: unverified → fail functional
  • 9 Sept 26 −3
    • Security disclosure: fail → unverified functional
    • Stability: pass → 0.80 functional
Diagnostics

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/@artifacta-mcp/mcp@1.0.4

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 97 packages
Packages resolved 97
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 10 exposed · ~1,545 tokens

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 →

Tool Tokens
complete_upload ~99

Finalize an artifact previously reserved via `request_upload_url` after the bytes have been PUT to the presigned URL. Server verifies the blob, computes the content hash, transitions the artifact from `pending` to `active`, and increments tenant usage. Calling this on an already-active artifact is idempotent and returns the existing record. Calling before the PUT completes returns `upload_not_found` — wait and retry.

NameTypeReqDescription
artifact_idstringyes

No output schema declared.

No examples provided.

get_artifact ~108

Fetch metadata for a single artifact by ID: filename, content type, size, content hash, session/agent IDs, custom metadata, expiry, creation timestamp. Does NOT return the file bytes — call `get_artifact_download_url` for that. Returns `artifact_not_found` for unknown IDs, `artifact_already_deleted` (HTTP 410) for soft-deleted ones, `artifact_expired` (410) for those past their TTL.

NameTypeReqDescription
artifact_idstringyes

No output schema declared.

No examples provided.

get_artifact_download_url ~93

Generate a short-lived presigned URL (1 hour) the agent can use to download the artifact's bytes directly from Cloudflare R2. Use this when the agent itself needs to consume the file. For sharing with humans, use `create_download_link` instead — that produces a stable `dl.artifacta.io/lnk_…` URL with configurable expiry.

NameTypeReqDescription
artifact_idstringyes

No output schema declared.

No examples provided.

list_artifacts ~191

List artifacts owned by the calling tenant, newest first. Supports filters by `session_id`, `agent_id`, `filename` (exact match), `content_type`, `created_after` / `created_before` (ISO 8601), and one or more `metadata.<key>=<value>` pairs (multi-key requires Pro). Returns a page of artifact records and a `next_cursor` to fetch the next page. Use this to discover what an agent or pipeline produced when you only know a session or agent ID.

NameTypeReqDescription
agent_idstring
content_typestring
created_afterstring
created_beforestring
cursorstringOpaque cursor from previous page's next_cursor.
filenamestring
limitinteger
metadataobject
session_idstring

No output schema declared.

No examples provided.

list_sessions ~87

List session IDs synthesized from the calling tenant's artifacts, ordered by most recent activity. Each entry includes artifact count, seal status, and first/last activity timestamps. Sessions are not first-class — they exist only as long as artifacts reference them.

NameTypeReqDescription
created_afterstring
created_beforestring
cursorstring
limitinteger

No output schema declared.

No examples provided.

publish_artifact ~127

Publish an existing artifact as a polished, shareable public page at https://artifacta.io/a/{slug}. Composes with store_artifact (store first, then publish). Returns a public_url anyone can open without an Artifacta account. Default visibility is unlisted (link-only); pass visibility:"public" for gallery-eligible later. Idempotent: re-publishing the same artifact_id updates the existing page and keeps the same URL.

NameTypeReqDescription
accessstring
artifact_idstringyes
titlestring
visibilitystring

No output schema declared.

No examples provided.

request_upload_url ~241

Reserve a presigned R2 PUT URL for a file too large to send through `store_artifact` (over 500 MB up to 5 GB). Returns an `upload_url`, headers to include in the PUT, and an `artifact_id` in `pending` state. The agent (or its environment) PUTs the bytes directly to R2, then calls `complete_upload`. Pro plan only. Most agents should use `store_artifact` and let the MCP server pick the path automatically. Not retry-safe: this endpoint does not support idempotency keys, so on an HTTP 5xx or network error the reservation may or may not have been created. Do NOT blindly retry — the error guidance tells you to first call `list_artifacts` with the same `session_id`/`agent_id` to detect any pending artifact, so you don't create a duplicate.

NameTypeReqDescription
agent_idstring
content_typestringyes
filenamestringyes
metadataobject
session_idstring
size_bytesintegeryes
ttlstring

No output schema declared.

No examples provided.

store_artifact ~462

Upload a file as a new artifact in a single call. Provide EITHER up to ~10 MB of base64-encoded bytes via `content`, OR a local filesystem `path` that the MCP server reads and streams as multipart/form-data (up to 500 MB). For files larger than 500 MB, use `request_upload_url` (Pro only) instead — `store_artifact` returns `file_too_large` for them. Tags the artifact with `session_id` / `agent_id` / `metadata` for later retrieval and returns the full artifact record including its new `artifact_id` and `content_hash`. Path uploads are confined. The `path` argument is constrained to the launcher-configured allow-list (default: the MCP server's CWD). Paths outside the allow-list, paths traversing symlinks out of it, and paths to known-sensitive locations (`~/.ssh`, `~/.aws`, `/etc/`, etc.) are refused with `invalid_request`. For crash-safe retries, supply your own `idempotency_key` (any string ≤256 chars): a replay within 24h returns the original artifact and never double-bills. If you omit it, the server auto-generates one and returns it under `_meta.idempotency_key`, but that key protects only in-process retries within a single call — it is lost if the server restarts, so pre-commit your own key when durability matters.

NameTypeReqDescription
agent_idstring
contentstringBase64-encoded bytes. Use for content under 10 MB or when no local path is available.
content_typestringMIME type. If omitted, guessed from filename.
filenamestringyes
idempotency_keystring
metadataobject
pathstringAbsolute local path inside the launcher-configured allow-list. The MCP server reads and streams this as multipart. Mutually exclusive with `content`. Paths outside the allow-list are refused.
session_idstring
ttlstringDuration suffix (e.g. `7d`, `30d`) or `never` (Pro only). Defaults to plan default.

No output schema declared.

No examples provided.

unpublish_artifact ~72

Remove the public page for an artifact, making the public URL inaccessible. The artifact itself is not deleted — only its shareable page is taken down. The URL stops resolving immediately. Idempotent: calling unpublish on an already-unpublished artifact is a no-op.

NameTypeReqDescription
artifact_idstringyes

No output schema declared.

No examples provided.

whoami ~65

Return the calling tenant's identity, plan tier, current usage counters (storage bytes, monthly requests, active links), and rate limits. Use this once at the start of an agent run to confirm authentication and to size subsequent operations against quota. Free of side effects and quota-cheap.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the io.artifacta/mcp server?

io.artifacta/mcp is listed in the public MCP registry as io.artifacta/mcp. Artifact store for AI agents. Hosted OAuth at mcp.artifacta.io/mcp; local stdio via npm/PyPI. This page covers its npm package (@artifacta-mcp/mcp).

Is the io.artifacta/mcp server safe to use?

io.artifacta/mcp scores 80 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. 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.artifacta/mcp server expose?

io.artifacta/mcp exposes 10 tools: whoami, list_artifacts, get_artifact, get_artifact_download_url, list_sessions, and 5 more. Their descriptions and schemas cost roughly 1,545 tokens of context every time the server is loaded.

Is the io.artifacta/mcp server still maintained?

io.artifacta/mcp 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.

What licence is the io.artifacta/mcp server under?

io.artifacta/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.