# Linq (npm · @linqapp/sdk-mcp)

Send and manage iMessage, RCS, and SMS conversations through the Linq API.

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

## Components

- npm · `@linqapp/sdk-mcp`: 79/100 (this document), [markdown](https://verifymcp.io/servers/linq-team-linq/linqapp-sdk-mcp.md), [page](https://verifymcp.io/servers/linq-team-linq/linqapp-sdk-mcp)

## Channel facts

- Registry: `npm`
- Package: `@linqapp/sdk-mcp`
- Version: `0.82.2`
- 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-21.

- **Supply Chain Security**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - Dependency health was assessed across the 156 of 157 dependencies we could resolve, so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to linq-team/linq-node).
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 1 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 561 tokens (~280/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 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**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "execute" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 3 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 Linq MCP server?

Linq runs locally as an npm package, launched with npx -y @linqapp/sdk-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 linq-team-linq -- npx -y @linqapp/sdk-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "linq-team-linq": {
      "command": "npx",
      "args": [
        "-y",
        "@linqapp/sdk-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "linq-team-linq": {
      "command": "npx",
      "args": [
        "-y",
        "@linqapp/sdk-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add linq-team-linq -- npx -y @linqapp/sdk-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add linq-team-linq --command npx --arg -y --arg @linqapp/sdk-mcp
```

### Hermes

```yaml
mcp_servers:
  linq-team-linq:
    command: "npx"
    args: ["-y", "@linqapp/sdk-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "linq-team-linq": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@linqapp/sdk-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add linq-team-linq -t stdio -c npx -a -y @linqapp/sdk-mcp
```

### Other

```json
{
  "mcpServers": {
    "linq-team-linq": {
      "command": "npx",
      "args": [
        "-y",
        "@linqapp/sdk-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-20 (score 79, +1)

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

### 2026-11-18 (score 78, +1)

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

### 2026-11-16 (score 77, +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-11-13 (score 76, +1)

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

### 2026-11-11 (score 75, +1)

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

### 2026-11-09 (score 74, +6)

- [security improvement] Source repository: unverified → pass

### 2026-11-08 (score 68, +10)

- [security regression] Provenance: pass → unverified
- [security improvement] Malware scan: unverified → pass

### 2026-11-07 (score 58, −14)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 0.79.0 → 0.82.2

## MCP tools (2)

### `execute` (~274 tokens)

Runs JavaScript code to interact with the Linq API V3 API.

You are a skilled TypeScript programmer writing code to interface with the service.
Define an async function named "run" that takes a single parameter of an initialized SDK client and it will be run.
For example:

\```
async function run(client) {
  const chat = await client.chats.create({
    from: '+12052535597',
    message: {},
    to: ['+12052532136'],
  });

  console.log(chat.chat);
}
\```

You will be returned anything that your function returns, plus the results of any console.log statements.
Do not add try-catch blocks for single API calls. The tool will handle errors for you.
Do not add comments unless necessary for generating better code.
Code will run in a container, and cannot interact with the network outside of the given SDK client.
Variables will not persist between calls, so make sure to return or log any data you might need later.
Remember that you are writing TypeScript code, so you need to be careful with your types.
Always type dynamic key-value stores explicitly as Record<string, YourValueType> instead of {}.

Input parameters:

- `code` (string, required): Code to execute.
- `intent` (string): Task you are trying to perform. Used for improving the service.

### `search_docs` (~80 tokens)

Search SDK documentation to find methods, parameters, and usage examples for interacting with the API. Use this before writing code when you need to discover the right approach.

Input parameters:

- `detail` (string): The amount of detail to return.
- `language` (string, required): The language for the SDK to search for.
- `query` (string, required): The query to search for.

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/linq-team-linq/linqapp-sdk-mcp#diagnostics

## Score history

- 2026-11-21: 79
- 2026-11-20: 79
- 2026-11-19: 78
- 2026-11-18: 78
- 2026-11-17: 77
- 2026-11-16: 77
- 2026-11-15: 76
- 2026-11-14: 76
- 2026-11-13: 76
- 2026-11-12: 75
- 2026-11-11: 75
- 2026-11-10: 74
- 2026-11-09: 74
- 2026-11-08: 68
- 2026-11-07: 58
- 2026-11-06: 72
- 2026-11-05: 72

## Common questions

### What is the Linq MCP server?

Linq is an MCP server listed in the public MCP registry as io.github.linq-team/linq. Send and manage iMessage, RCS, and SMS conversations through the Linq API. This page covers its npm package (@linqapp/sdk-mcp).

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

Linq scores 79 out of 100 on VerifyMCP. We recorded 2 known advisories against it as of 21 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 Linq MCP server expose?

Linq exposes 2 tools: execute, search_docs. Their descriptions and schemas cost roughly 354 tokens of context every time the server is loaded.

### Is the Linq MCP server still maintained?

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

Linq 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.

### What did VerifyMCP test on the Linq MCP server?

VerifyMCP ran 16 checks on Linq, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@linqapp/sdk-mcp
- Socket report: https://socket.dev/npm/package/@linqapp/sdk-mcp
- Repository: https://github.com/linq-team/linq-node
- Changelog RSS feed: https://verifymcp.io/servers/linq-team-linq/linqapp-sdk-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/linq-team-linq/linqapp-sdk-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/linq-team-linq/linqapp-sdk-mcp.json
- HTML version of this page: https://verifymcp.io/servers/linq-team-linq/linqapp-sdk-mcp
