# Notol (npm · @notol/mcp)

Free payee check for AI agents paying USDC: flags lookalike, reserved and own addresses.

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

## Components

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

## Channel facts

- Registry: `npm`
- Package: `@notol/mcp`
- Version: `0.1.4`
- 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**: 98/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.
  - 31 of 108 dependencies flagged as unhealthy.
- **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 9 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 353 tokens (~176/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**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **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; "notol_transfer_status" implies "transfer" and declares readOnlyHint instead, contradicting what its own name says it does.
  - 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.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

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

Notol runs locally as an npm package, launched with npx -y @notol/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-notol-mcp -- npx -y @notol/mcp
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "app-notol-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@notol/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-12 (score 63)

First indexed and scored.

## MCP tools (2)

### `notol_check_payee` (~292 tokens)

Check a payee

Check how Notol would handle a USDC payment from the paying address (sender) to an address. Useful before paying an address that has not been paid before, or one taken from transaction history, where a lookalike is easy to miss. Answers direct (a payee verified in Notol's on-chain registry), escrow (new payee: a Notol send would be held until the recipient proves control of the address, else refunded) or blocked. It catches: lookalike (the address imitates a verified payee, the pattern used in address poisoning), self, reserved (system address). A blocked or lookalike answer is a reason to stop and ask the user. Limits: a hint, and a Notol send re-checks on chain. It only knows payees verified in Notol's registry on Arc; it says nothing about payees verified elsewhere or on other chains, and escrow/new_payee is not a verdict that an address is safe. Read-only, free, moves no money. Checking an address does not make it trustworthy: the address to pay should still come from the user's own records.

Input parameters:

- `recipient` (string, required): Destination address to check, 0x + 40 hex
- `sender` (string): The address that would pay, 0x + 40 hex. Optional when the server has a default (NOTOL_SENDER).

### `notol_transfer_status` (~61 tokens)

Transfer status

Status of a transfer: Pending, Released or Refunded, with the amount as a decimal USDC string and the expiry (unix seconds).

Input parameters:

- `transferId` (string, required): Transfer id, 0x + 64 hex, from notol_send

## Diagnostics

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

## Score history

- 2026-11-21: 63
- 2026-11-20: 63
- 2026-11-19: 63
- 2026-11-18: 63
- 2026-11-17: 63
- 2026-11-16: 63
- 2026-11-15: 63
- 2026-11-14: 63
- 2026-11-13: 63
- 2026-11-12: 63

## Common questions

### What is the Notol MCP server?

Notol is an MCP server listed in the public MCP registry as app.notol/mcp. Free payee check for AI agents paying USDC: flags lookalike, reserved and own addresses. This page covers its npm package (@notol/mcp).

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

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

Notol exposes 2 tools: notol_check_payee, notol_transfer_status. Their descriptions and schemas cost roughly 353 tokens of context every time the server is loaded.

### Is the Notol MCP server still maintained?

Notol 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 Notol MCP server under?

Notol declares the MIT 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 Notol MCP server?

VerifyMCP ran 14 checks on Notol, covering Malware scan, Known CVEs, Install scripts, Dependency health and 10 more. 2 items could not be completed, a gap on our side rather than a finding about Notol: Security disclosure and Stability. One category scores 0 for that reason, because we only credit what we can confirm. 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/@notol/mcp
- Socket report: https://socket.dev/npm/package/@notol/mcp
- Website: https://www.notol.app/docs#mcp
- Changelog RSS feed: https://verifymcp.io/servers/app-notol-mcp/notol-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-notol-mcp/notol-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/app-notol-mcp/notol-mcp.json
- HTML version of this page: https://verifymcp.io/servers/app-notol-mcp/notol-mcp
