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.

PADAM · NOCTURNE memory

PYPI · PADAM-NOCTURNE

Local memory for AI agents: masks secrets, holds injected orders for review, forgets one record

Available components

+4 this week 70 Trust /100

Last scanned (10 hours ago)

Scores higher than 63% of PyPI servers

Category Memory and Knowledge

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 Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 0 of 10 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to MaksimGalatin/padam-nocturne). View diagnostics → Pass
  • Clear OSI-approved license (AGPL-3.0-only).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability68
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 1051 tokens (~87/item across 12 items; 9 tools + 3 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage89
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 61% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (15)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

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.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.

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 →

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.

  • 21 Nov 26 +1
    • Package version: 0.7.0 → 0.7.1 functional
  • 20 Nov 26 −16
    • Malware scan: pass → unverified ▼ security
    • Tool coverage: 80% → 61% ▼ functional
    • Schema quality: fail → pass ▲ functional
    • Schema quality: good → fair functional
    • Package version: 0.6.4 → 0.7.0 functional
    • Package version: 0.6.4 → 0.6.5 functional
  • 19 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 18 Nov 26 +1
    • Package version: 0.6.3 → 0.6.4 functional
  • 17 Nov 26 0
    • Package version: 0.6.2 → 0.6.3 functional
  • 16 Nov 26 −12
    • Malware scan: pass → unverified ▼ security
    • Schema quality: 1266 → 1790 ▼ functional
    • Tool coverage: 69% → 80% ▲ functional
    • First check of Schema quality: 100 functional
    • First check of Tool coverage: 100 functional
    • Package version: 0.5.1 → 0.6.2 functional
    • Package version: 0.5.1 → 0.6.1 functional
    • Package version: 0.5.1 → 0.6.0 functional
    • Package version: 0.5.1 → 0.5.4 functional
  • 15 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
    • Schema quality: 1147 → 1266 ▼ functional
    • Package version: 0.5.0 → 0.5.1 functional
  • 14 Nov 26 +1
    • Malware scan: unverified → pass ▲ security
    • Package version: 0.4.16 → 0.5.0 functional
    • Package version: 0.4.16 → 0.4.18 functional
    • Package version: 0.4.16 → 0.4.17 functional
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 21 Nov 2026 · Analysed pypi/padam-nocturne@0.7.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo MaksimGalatin/padam-nocturne
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/MaksimGalatin/padam-nocturne/.github/workflows/publish.yml@refs/tags/v0.7.1
Rekor log index 4031988041
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:33acc85e6c82e8cc39a2a4ead7ad01b405043a8d5d0cb81da62f7482ecc32800

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Dependencies 10 packages
Packages resolved 10
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~531 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
padam_confirm ~23

Confirm stored record to raise confidence.

NameTypeReqDescription
idstringyes–
NameTypeReqDescription
confirmedbooleanyes–

No examples provided.

padam_export ~68

Export memory JSON. Owner confirms via elicitation when the client supports it; PADAM_MCP_EXPORT_CONFIRM=strict always requires it.

NameTypeReqDescription
include_supersededboolean–Old
limitinteger––
offsetinteger––
scopestring––
NameTypeReqDescription
memoryarrayyes–

No examples provided.

padam_profile ~25

Load owner-signed profile at session start.

NameTypeReqDescription
scopestring––
NameTypeReqDescription
countintegeryes–

No examples provided.

padam_refute ~35

Refute a wrong record to lower confidence.

NameTypeReqDescription
dropnumber–Penalty
idstringyes–
NameTypeReqDescription
refutedbooleanyes–

No examples provided.

padam_search ~134

Search memory facts; returns stored data.

NameTypeReqDescription
agent_idstring––
as_ofstring–As-of ISO
compactboolean–Trim text
graph_hopsinteger–Hops 0..2
kindstring–Kind
known_atstring–Known ISO
limitinteger––
max_tokensinteger–Token cap
modestring–Mode
querystringyes–
reflectboolean–Reflect
scopestring––
scopesarray–Scope list
NameTypeReqDescription
recordsarrayyes–

No examples provided.

padam_sleep ~61

Consolidate episodes; dry_run previews only.

NameTypeReqDescription
batchinteger–Batch
dry_runboolean–Preview
max_insightsinteger–REM cap
remboolean–REM
scopestring––
NameTypeReqDescription
episodes_sampledintegeryes–

No examples provided.

padam_stats ~19

Read-only memory counts, queue and DB path.

Input schema present but exposes no named parameters.

NameTypeReqDescription
activeintegeryes–

No examples provided.

padam_timeline ~25

Read version history of one memory record.

NameTypeReqDescription
idstringyes–
NameTypeReqDescription
versionsarrayyes–

No examples provided.

padam_write ~141

Save fact, decision or fix; masks secrets.

NameTypeReqDescription
agent_idstring––
contentstringyes–
dedup_modestring–Merge
derived_fromarray–Parent ids
importancenumber–0..1
kindstring–Kind
linksarray–Edges
originstring–Origin
scopestring––
textstring––
valid_fromstring–From ISO
valid_tostring–To ISO
visibilitystring–Sharing
workspace_idstring–Workspace
NameTypeReqDescription
idstringyes–

No examples provided.

Install

How do I install the PADAM · NOCTURNE memory MCP server?

PADAM · NOCTURNE memory runs locally as a PyPI package, launched with uvx padam-nocturne. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · padam-nocturne

# add to Claude Code
claude mcp add maksimgalatin-padam-nocturne -- uvx padam-nocturne
Common questions

What is the PADAM · NOCTURNE memory MCP server?

PADAM · NOCTURNE memory is an MCP server listed in the public MCP registry as io.github.MaksimGalatin/padam-nocturne. Local memory for AI agents: masks secrets, holds injected orders for review, forgets one record. This page covers its PyPI package (padam-nocturne).

Is the PADAM · NOCTURNE memory MCP server safe to use?

PADAM · NOCTURNE memory scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. 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 PADAM · NOCTURNE memory MCP server expose?

PADAM · NOCTURNE memory exposes 9 tools: padam_search, padam_write, padam_confirm, padam_refute, padam_timeline, and 4 more. Their descriptions and schemas cost roughly 531 tokens of context every time the server is loaded.

Is the PADAM · NOCTURNE memory MCP server still maintained?

PADAM · NOCTURNE memory 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 PADAM · NOCTURNE memory MCP server under?

PADAM · NOCTURNE memory declares the AGPL-3.0-only 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 PADAM · NOCTURNE memory MCP server?

VerifyMCP ran 15 checks on PADAM · NOCTURNE memory, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about PADAM · NOCTURNE memory: Malware scan. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.