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.

PictMCP

NPM · PICTMCP · SCANNED SEP 20

Provides pairwise combinatorial testing capabilities to AI assistants.

Available components

npm · pictmcp 91
0 this week 91 Trust /100

Deprecated

This server is marked deprecated in the MCP registry.

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 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to takeyaqa/PictMCP). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 181 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 57 tokens (~57/item across 1 items; 1 tools + 0 resources), lean.Pass
  • 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 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "generate-test-cases" implies "execute" 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 1 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 PictMCP MCP server?

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

npm · pictmcp

# add to Claude Code
claude mcp add takeyaqa-pictmcp -- npx -y pictmcp
// .cursor/mcp.json
{
  "mcpServers": {
    "takeyaqa-pictmcp": {
      "command": "npx",
      "args": [
        "-y",
        "pictmcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "takeyaqa-pictmcp": {
      "command": "npx",
      "args": [
        "-y",
        "pictmcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add takeyaqa-pictmcp -- npx -y pictmcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "takeyaqa-pictmcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "pictmcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add takeyaqa-pictmcp --command npx --arg -y --arg pictmcp
# ~/.hermes/config.yaml
mcp_servers:
  takeyaqa-pictmcp:
    command: "npx"
    args: ["-y", "pictmcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "takeyaqa-pictmcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "pictmcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add takeyaqa-pictmcp -t stdio -c npx -a -y pictmcp
// mcp.json
{
  "mcpServers": {
    "takeyaqa-pictmcp": {
      "command": "npx",
      "args": [
        "-y",
        "pictmcp"
      ]
    }
  }
}
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
    • Security disclosure: unverified → pass ▲ functional
  • 19 Sept 26 −1
    • Security disclosure: pass → unverified ▼ functional
  • 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.

  • 17 Sept 26 −2
    • Stability: pass → 0.83 functional
  • 16 Sept 26 0
    • Stability: 0.97 → pass security
  • 15 Sept 26 +1

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

  • 12 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 −2
    • 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/pictmcp@0.6.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 takeyaqa/PictMCP
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/takeyaqa/PictMCP/.github/workflows/publish.yml@refs/tags/v0.6.0
Rekor log index 1155019666
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:6c4fbef29a90af572300504b43285daa33ecfb0da7634a8902741a99fae83d8bb981bf1cf0f0a5b9acc6b51e0178ff1406e5c5764a41a8ddf138812e5

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 1 exposed · ~57 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
generate-test-cases ~57

Executes PICT with the given parameters and options to generate test cases.

NameTypeReqDescription
constraintsTextstring–PICT constraint expressions to filter invalid combinations.
parametersarrayyesRepresents a parameter definition for PICT test case generation.
NameTypeReqDescription
messagestring–Optional message output from PICT, typically containing information.
modelFilestringyesThe complete model file content that was passed to PICT.
resultobjectyesRepresents the parsed result of PICT test case generation.

No examples provided.

Common questions

What is the PictMCP MCP server?

PictMCP is an MCP server listed in the public MCP registry as io.github.takeyaqa/PictMCP. Provides pairwise combinatorial testing capabilities to AI assistants. This page covers its npm package (pictmcp).

Is the PictMCP MCP server safe to use?

PictMCP scores 91 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.

What tools does the PictMCP MCP server expose?

PictMCP exposes 1 tool: generate-test-cases. Their descriptions and schemas cost roughly 57 tokens of context every time the server is loaded.

Is the PictMCP MCP server still maintained?

PictMCP is marked deprecated 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 PictMCP MCP server under?

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