Notol
NPM · @NOTOL/MCP
Free payee check for AI agents paying USDC: flags lookalike, reserved and own addresses.
Available components
Last scanned (12 hours ago)
Scores higher than 32% of npm servers
Category Crypto and Web3
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 108 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 9 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
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; "notol_transfer_status" implies "transfer" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- An AI judge read all 2 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
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.
Checks we ran (14)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (2)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 12 Nov 26 63
First indexed and scored.
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 21 Nov 2026 · Analysed npm/@notol/mcp@0.1.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 108 packages
| Packages resolved | 108 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
notol_check_payee Check a payee ~292
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.
| Name | Type | Req | Description |
|---|---|---|---|
| recipient | string | yes | 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). |
No output schema declared.
No examples provided.
notol_transfer_status Transfer status ~61
Status of a transfer: Pending, Released or Refunded, with the amount as a decimal USDC string and the expiry (unix seconds).
| Name | Type | Req | Description |
|---|---|---|---|
| transferId | string | yes | Transfer id, 0x + 64 hex, from notol_send |
No output schema declared.
No examples provided.
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.
npm · @notol/mcp
claude mcp add app-notol-mcp -- npx -y @notol/mcp
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.