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.

Sec Nmfp

NPM · @PIPEWORX/MCP-SEC-NMFP · 2 COMPONENTS

SEC Form N-MFP — money market fund portfolio holdings.

+3 this week 83 Trust /100

Last scanned (13 hours ago)

Scores higher than 77% of npm servers

Category Finance and Payments

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 Security100
  • 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
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-sec-nmfp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 477 tokens (~159/item across 3 items; 3 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 Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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
What we tested

Checks we ran (16)

  • Malware scan
  • 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

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.

  • 5 Nov 26 +3
    • Stability: unverified → 0.23 ▲ functional
    • Package version: 0.2.0 → 0.2.1 functional
  • 30 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 29 Oct 26 80

    First indexed and scored.

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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-sec-nmfp@0.2.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 npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-sec-nmfp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-sec-nmfp/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3692342107
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:5774a483767afb0dae2b19fba99e2faa144306af27b4c6b43cc889777a037829b6ff0a9376a5e9dd86bcc653030d62735045379d9b42e135c5af3d90f

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~421 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
nmfp_fund_holdings ~171

The portfolio a US money market fund reported to the SEC on Form N-MFP for one month: every security it held, with issuer, title, investment category (Treasury debt, government agency debt, repurchase agreement, financial company commercial paper, certificate of deposit) and maturity dates. Give the fund or series name ("Fidelity Government Money Market", "Vanguard Federal"). Answers "what is this money market fund invested in", "how much Treasury paper does it hold".

NameTypeReqDescription
fundstringyesFund registrant or series name, or a fragment of it.
limitnumber–Maximum holdings to return, 1-500 (default 100).
periodstring–Reporting period id from nmfp_periods. Omit for the most recent published month.

No output schema declared.

No examples provided.

nmfp_periods ~65

Which SEC Form N-MFP monthly reporting periods are published, newest first, with the date range each covers. Money market funds file monthly and SEC posts a period a few days after it closes. Use this to pick a period argument or to see how current the data is.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

nmfp_security_holders ~185

Which US money market funds hold paper from a given issuer, from SEC Form N-MFP monthly portfolio filings — the reverse of a fund fact sheet, which makes you name the fund first. Give an issuer name (e.g. "Federal Home Loan Bank", "JPMorgan") or a CUSIP. Returns each fund holding it, the fund family, the security title, investment category and maturity dates. Answers "which money market funds are exposed to this issuer", "who holds this bank's commercial paper".

NameTypeReqDescription
issuerstringyesIssuer name or fragment ("Federal Home Loan Bank"), or a 9-character CUSIP.
limitnumber–Maximum holdings to return, 1-200 (default 50).
periodstring–Reporting period id from nmfp_periods. Omit for the most recent published month.

No output schema declared.

No examples provided.

Install

How do I install the Sec Nmfp MCP server?

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

npm · @pipeworx/mcp-sec-nmfp

# add to Claude Code
claude mcp add pipeworx-io-sec-nmfp -- npx -y @pipeworx/mcp-sec-nmfp
Common questions

What is the Sec Nmfp MCP server?

Sec Nmfp is an MCP server listed in the public MCP registry as io.github.pipeworx-io/sec-nmfp. SEC Form N-MFP, money market fund portfolio holdings. This page covers its npm package (@pipeworx/mcp-sec-nmfp).

Is the Sec Nmfp MCP server safe to use?

Sec Nmfp scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 Sec Nmfp MCP server expose?

Sec Nmfp exposes 3 tools: nmfp_security_holders, nmfp_fund_holdings, nmfp_periods. Their descriptions and schemas cost roughly 421 tokens of context every time the server is loaded.

Is the Sec Nmfp MCP server still maintained?

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

Sec Nmfp 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 Sec Nmfp MCP server?

VerifyMCP ran 16 checks on Sec Nmfp, 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.