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.

Replicate

NPM · @PIPEWORX/MCP-REPLICATE · 2 COMPONENTS

Replicate MCP.

+4 this week 80 Trust /100

Last scanned (7 hours ago)

Scores higher than 65% of npm servers

Category AI and Machine Learning

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 Security100
  • 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
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-replicate). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 762 tokens (~47/item across 16 items; 16 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 17 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
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.

  • 5 Nov 26 +1
    • Security disclosure: unverified → fail ▼ functional
  • 4 Nov 26 0
    • Tool safety: pass → unverified ▼ security
    • Stability: 0.17 → unverified ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Security disclosure: fail → unverified ▼ functional
    • First check of Schema quality: unverified functional
    • Package version: 0.2.0 → 0.2.1 functional
  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 76

    First indexed and scored.

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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-replicate@0.2.1

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 pipeworx-io/mcp-replicate
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-replicate/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3691882021
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:71987aff65c074fb75aec378e7428c6d97636e0965b644b55f29117bfb90d36173238baea45882f2b972a5debe97f59ad613ed5a042649564ec674e8c

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 16 exposed · ~710 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
account ~26

Fetch your Replicate account details including username, name, GitHub URL, and account type.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

cancel_prediction ~19

Cancel a prediction.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

collection ~45

Fetch models belonging to a specific Replicate collection by slug (e.g. "text-to-image"); returns the collection description and a list of model objects.

NameTypeReqDescription
slugstringyes–

No output schema declared.

No examples provided.

collections ~37

List all curated Replicate model collections (e.g. "text-to-image", "speech-to-text"); returns collection slug, name, and description.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

create_deployment_prediction ~57

Run via a deployment.

NameTypeReqDescription
input–yes–
namestringyes–
ownerstringyes–
streamboolean––
webhookstring––
webhook_events_filterarray––

No output schema declared.

No examples provided.

create_prediction ~78

Start a Replicate model run by submitting a version id and input object; returns a prediction id and status that can be polled with the prediction tool until output is ready.

NameTypeReqDescription
input–yes–
streamboolean––
versionstringyes–
webhookstring––
webhook_events_filterarray––

No output schema declared.

No examples provided.

deployment ~24

Deployment detail.

NameTypeReqDescription
namestringyes–
ownerstringyes–

No output schema declared.

No examples provided.

hardware ~36

List available Replicate hardware types (CPU, GPU SKUs) with their names and SKU identifiers; use to select hardware when creating a deployment.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_deployments ~50

List your Replicate model deployments (dedicated, auto-scaled endpoints), paginated via cursor; returns owner, name, current model version, and scaling config.

NameTypeReqDescription
cursorstring––

No output schema declared.

No examples provided.

list_models ~47

List all public models available on Replicate, paginated via cursor; returns owner, name, description, run count, and latest version id for each model.

NameTypeReqDescription
cursorstring––

No output schema declared.

No examples provided.

list_predictions ~44

List your recent Replicate predictions in reverse chronological order, paginated via cursor; returns prediction id, model version, status, and creation timestamp.

NameTypeReqDescription
cursorstring––

No output schema declared.

No examples provided.

model ~50

Fetch metadata for a specific Replicate model by owner and name, including description, visibility, run count, latest version, and GitHub URL.

NameTypeReqDescription
namestringyes–
ownerstringyes–

No output schema declared.

No examples provided.

model_version ~61

Fetch full metadata for a specific Replicate model version by owner, name, and version_id, including the complete input/output OpenAPI schema and Cog version.

NameTypeReqDescription
namestringyes–
ownerstringyes–
version_idstringyes–

No output schema declared.

No examples provided.

model_versions ~51

List all published versions of a Replicate model by owner and name; returns version ids, creation timestamps, and input/output schema for each version.

NameTypeReqDescription
namestringyes–
ownerstringyes–

No output schema declared.

No examples provided.

prediction ~47

Poll the status and retrieve output for a Replicate prediction by id; returns status (starting/processing/succeeded/failed/canceled), output URLs, and logs.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

search_models ~38

Search public Replicate models by keyword query; returns matching models with owner, name, description, and run count.

NameTypeReqDescription
querystringyes–

No output schema declared.

No examples provided.

Install

How do I install the Replicate MCP server?

Replicate runs locally as an npm package, launched with npx -y @pipeworx/mcp-replicate. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pipeworx/mcp-replicate

# add to Claude Code
claude mcp add pipeworx-io-replicate -- npx -y @pipeworx/mcp-replicate
Common questions

What is the Replicate MCP server?

Replicate is an MCP server listed in the public MCP registry as io.github.pipeworx-io/replicate. Replicate MCP. This page covers its npm package (@pipeworx/mcp-replicate).

Is the Replicate MCP server safe to use?

Replicate scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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.

What tools does the Replicate MCP server expose?

Replicate exposes 16 tools: list_models, model, model_versions, model_version, search_models, and 11 more. Their descriptions and schemas cost roughly 710 tokens of context every time the server is loaded.

Is the Replicate MCP server still maintained?

Replicate is still listed as active in the MCP registry. We last reached this channel on 5 November 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 Replicate MCP server under?

Replicate declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.