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.

Multimeter

NPM · MMT-MCP · SCANNED SEP 25

Scaffold, validate, format, and run YAML .mmt API tests. Do not invent syntax.

Available components

npm · mmt-mcp 77
+3 this week 77 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
  • 45 of 145 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 1 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
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
  • Tool/resource definitions use about 1421 tokens (~45/item across 31 items; 9 tools + 22 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
  • Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 94% 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 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "run" 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 10 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 Multimeter MCP server?

Multimeter runs locally as an npm package, launched with npx -y mmt-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 · mmt-mcp

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

  • 25 Sept 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
  • 24 Sept 26 +1

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

  • 22 Sept 26 +1

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

  • 19 Sept 26 +1

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

  • 17 Sept 26 +35
    • Injection markers: unverified → pass ▲ security
    • Tool coverage: unverified → 100 ▲ functional
    • Schema quality: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Stability: unverified → 0.30 ▲ functional
    • Package version: 1.42.2-pre → 1.42.4 functional
  • 16 Sept 26 −30
    • Tool safety: pass → unverified ▼ 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: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Schema quality: 100 → unverified ▼ functional
    • Stability: unverified → 0.27 ▲ functional
    • Package version: 1.42.2-pre → 1.42.4 functional
  • 9 Sept 26 +15
    • Malware scan: unverified → pass ▲ security
  • 8 Sept 26 54

    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 25 Sept 2026 · Analysed npm/mmt-mcp@1.42.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 145 packages
Packages resolved 145
Stale 45
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~1,129 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
api_card ~112

Return a small API summary (method, url, inputs, outputs, suggested paths) without dumping the full file. Prefer this over reading the whole .mmt or OpenAPI when generating or planning a test. Next step for a new test: scaffold_test. Do not use testlight, npx, npm, shell, or node dist/mcp/server.js.

NameTypeReqDescription
apiPathstringyesAPI .mmt file path relative to workspaceRoot or absolute
workspaceRootstringyesWorkspace root directory

No output schema declared.

No examples provided.

discover_api ~124

Call when listing APIs or inspecting one API before scaffolding a test. For a single API, prefer api_card. For new tests, prefer scaffold_test once apiPath is known. selectedApi omits full file content unless includeContent is true. Do not use testlight, npx, npm, shell, or node dist/mcp/server.js.

NameTypeReqDescription
apiPathstring–Optional API .mmt file path relative to workspaceRoot
includeContentboolean–Include full API file content (default false)
workspaceRootstringyesWorkspace root directory

No output schema declared.

No examples provided.

format ~80

Format a Multimeter file using canonical field ordering and style rules. Call after validate passes when normalizing generated or edited YAML. Do not use testlight, npx, npm, shell, or node dist/mcp/server.js.

NameTypeReqDescription
filestringyesPath to the .mmt file
workspaceRootstring–Workspace root for relative paths

No output schema declared.

No examples provided.

list_examples ~118

Call when you need example .mmt structure before creating or modifying a file. Prefer this over searching the repo or guessing YAML layout. Do not use testlight, npx, npm, shell, or node dist/mcp/server.js.

NameTypeReqDescription
categorystring–Filter by category such as basic or intermediate
includeContentboolean–Include full example file contents
maxItemsinteger–Maximum number of examples to return
typestring–Filter by document type such as test, api, or loadtest

No output schema declared.

No examples provided.

read_documentation ~113

Call when you need Multimeter YAML syntax rules. Defaults to pack "min" (small). Use pack "full" only for rare/advanced syntax. For new tests from an API, prefer scaffold_test over loading docs. Do not use testlight, npx, npm, shell, or node dist/mcp/server.js.

NameTypeReqDescription
packstring–min (default, low token) or full
topicstring–Documentation topic. Use workflow for MCP-first edit/run steps. Defaults to overview.

No output schema declared.

No examples provided.

run ~133

Execute a Multimeter test or API file and return structured pass/fail output, logs, and errors. ONLY supported way to run .mmt files from Copilot — call this directly when the user asks to run or execute. Do NOT use testlight CLI, npx, npm install, shell scripts, or node dist/mcp/server.js.

NameTypeReqDescription
envobject––
filestringyesPath to the .mmt file to run
inputsobject––
quietboolean–Reduce run logs in the response
workspaceRootstring–Workspace root for relative paths

No output schema declared.

No examples provided.

scaffold_test ~161

REQUIRED first step when generating a new Multimeter test from an existing API .mmt. Returns valid smoke (or example) test YAML, suggested path, import alias, and a compact apiCard. Write the yaml, apply only minimal edits, then validate. Do not invent a blank test from scratch. Do not use testlight, npx, npm, shell, or node dist/mcp/server.js.

NameTypeReqDescription
aliasstring–Optional import alias override
apiPathstringyesAPI .mmt file path relative to workspaceRoot or absolute
outPathstring–Optional suggested output test path (relative)
strategystring–smoke (default) or example inputs
workspaceRootstringyesWorkspace root directory

No output schema declared.

No examples provided.

suggest_assertions ~178

Suggest compact expect/assert YAML patches from API outputs and/or a JSON response body. Use after a run or when tightening a scaffolded smoke test — patch only, do not rewrite the file. Do not use testlight, npx, npm, shell, or node dist/mcp/server.js.

NameTypeReqDescription
apiPathstring–API .mmt to read outputs from
body––Parsed JSON response body
bodyFilestring–Path to a JSON response file
maxFieldsinteger–Max body fields to suggest
statusnumber–HTTP status to expect
stepIdstring–Call step id for ${id.field} asserts
stylestring–Patch style (default both)
workspaceRootstring–Workspace root (required with apiPath or bodyFile)

No output schema declared.

No examples provided.

validate ~110

REQUIRED after every create or modify operation on a .mmt file. Call immediately after editing a file and before telling the user the task is done. Returns structured errors and fix suggestions. Do not use testlight, npx, npm, shell, or node dist/mcp/server.js.

NameTypeReqDescription
expectedTypestring–Optional expected document type
filestringyesPath to the .mmt file relative to workspaceRoot or absolute
workspaceRootstring–Workspace root for relative paths

No output schema declared.

No examples provided.

Common questions

What is the Multimeter MCP server?

Multimeter is an MCP server listed in the public MCP registry as io.github.mshobeyri/multimeter. Scaffold, validate, format, and run YAML .mmt API tests. Do not invent syntax. This page covers its npm package (mmt-mcp).

Is the Multimeter MCP server safe to use?

Multimeter scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 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 Multimeter MCP server expose?

Multimeter exposes 9 tools: read_documentation, list_examples, discover_api, api_card, scaffold_test, and 4 more. Their descriptions and schemas cost roughly 1,129 tokens of context every time the server is loaded.

Is the Multimeter MCP server still maintained?

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

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