# Paramability (npm · @paramability/mcp)

Links your AI assistant app to the Paramability tab open in Chrome. Runs on your computer only.

- Trust score: 68/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- npm · `@paramability/mcp`: 68/100 (this document), [markdown](https://verifymcp.io/servers/app-paramability-mcp/paramability-mcp.md), [page](https://verifymcp.io/servers/app-paramability-mcp/paramability-mcp)

## Channel facts

- Registry: `npm`
- Package: `@paramability/mcp`
- Version: `1.0.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-04.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 19/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 12 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 59/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 358 tokens (~358/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Paramability MCP server?

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

### Claude

```bash
claude mcp add app-paramability-mcp -- npx -y @paramability/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "app-paramability-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@paramability/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-paramability-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@paramability/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add app-paramability-mcp -- npx -y @paramability/mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-paramability-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@paramability/mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-paramability-mcp --command npx --arg -y --arg @paramability/mcp
```

### Hermes

```yaml
mcp_servers:
  app-paramability-mcp:
    command: "npx"
    args: ["-y", "@paramability/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "app-paramability-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@paramability/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-paramability-mcp -t stdio -c npx -a -y @paramability/mcp
```

### Other

```json
{
  "mcpServers": {
    "app-paramability-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@paramability/mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-02 (score 68, +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.

### 2026-10-31 (score 67, +1)

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

### 2026-10-29 (score 66, +1)

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

### 2026-10-27 (score 65, +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.

### 2026-10-25 (score 64, +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.

### 2026-10-23 (score 63, +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.

### 2026-10-22 (score 62)

First indexed and scored.

## MCP tools (1)

### `paramability_connect` (~84 tokens)

Connect to Paramability

Links this assistant to the open Paramability tab in Chrome. Call it first, and whenever other Paramability tools are missing or say Paramability is not connected. It answers with a code to give the person, or confirms the tab is connected.

Input parameters:

- `newCode` (boolean): Only when a tab is already connected: get a code to move the connection to another tab.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/app-paramability-mcp/paramability-mcp#diagnostics

## Score history

- 2026-11-04: 68
- 2026-11-03: 68
- 2026-11-02: 68
- 2026-11-01: 67
- 2026-10-31: 67
- 2026-10-30: 66
- 2026-10-29: 66
- 2026-10-28: 65
- 2026-10-27: 65
- 2026-10-26: 64
- 2026-10-25: 64
- 2026-10-24: 63
- 2026-10-23: 63
- 2026-10-22: 62

## Common questions

### What is the Paramability MCP server?

Paramability is an MCP server listed in the public MCP registry as app.paramability/mcp. Links your AI assistant app to the Paramability tab open in Chrome. Runs on your computer only. This page covers its npm package (@paramability/mcp).

### Is the Paramability MCP server safe to use?

Paramability scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 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 Paramability MCP server expose?

Paramability exposes 1 tool: paramability_connect. Their descriptions and schemas cost roughly 84 tokens of context every time the server is loaded.

### Is the Paramability MCP server still maintained?

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

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

## Links

- npm package: https://www.npmjs.com/package/@paramability/mcp
- Socket report: https://socket.dev/npm/package/@paramability/mcp
- Website: https://paramability.app/
- Changelog RSS feed: https://verifymcp.io/servers/app-paramability-mcp/paramability-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-paramability-mcp/paramability-mcp.json
- HTML version of this page: https://verifymcp.io/servers/app-paramability-mcp/paramability-mcp