# loremfile (npm · loremfile)

CC0 sample files and test fixtures: find one, get its URL and SHA-256, check a copy on disk.

- Trust score: 92/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `loremfile`: 92/100 (this document), [markdown](https://verifymcp.io/servers/kumarprabhashanand-loremfile/loremfile.md), [page](https://verifymcp.io/servers/kumarprabhashanand-loremfile/loremfile)
- pypi · `loremfile`: 77/100, [markdown](https://verifymcp.io/servers/kumarprabhashanand-loremfile/loremfile-2.md), [page](https://verifymcp.io/servers/kumarprabhashanand-loremfile/loremfile-2)

## Channel facts

- Registry: `npm`
- Package: `loremfile`
- Version: `0.2.0`
- 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-05.

- **Supply Chain Security**: 100/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.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to kumarprabhashanand/loremfile).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 28 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 360 tokens (~120/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

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

loremfile runs locally as an npm package, launched with npx -y loremfile. 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 kumarprabhashanand-loremfile -- npx -y loremfile
```

### Cursor

```json
{
  "mcpServers": {
    "kumarprabhashanand-loremfile": {
      "command": "npx",
      "args": [
        "-y",
        "loremfile"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "kumarprabhashanand-loremfile": {
      "command": "npx",
      "args": [
        "-y",
        "loremfile"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add kumarprabhashanand-loremfile -- npx -y loremfile
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add kumarprabhashanand-loremfile --command npx --arg -y --arg loremfile
```

### Hermes

```yaml
mcp_servers:
  kumarprabhashanand-loremfile:
    command: "npx"
    args: ["-y", "loremfile"]
```

### Netclaw

```json
{
  "McpServers": {
    "kumarprabhashanand-loremfile": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "loremfile"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add kumarprabhashanand-loremfile -t stdio -c npx -a -y loremfile
```

### Other

```json
{
  "mcpServers": {
    "kumarprabhashanand-loremfile": {
      "command": "npx",
      "args": [
        "-y",
        "loremfile"
      ]
    }
  }
}
```

## 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-05 (score 92, +1)

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

### 2026-11-03 (score 91, +1)

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

### 2026-11-01 (score 90, +1)

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

### 2026-10-29 (score 89, +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-10-27 (score 88, +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-10-25 (score 87, +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-10-23 (score 86, +1)

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

### 2026-10-22 (score 85, +3)

- [functional improvement] Stability: unverified → 0.27

## MCP tools (3)

### `list_fixtures` (~148 tokens)

List loremfile.dev fixtures

One page of the published sample files, filtered by format, tag and size. Each comes with its URL and a description of what it is for. `total` counts every match and `next_offset` fetches the next page; it is null on the last.

Input parameters:

- `format`: Formats to include, any of, e.g. ["pdf", "png"].
- `limit` (integer): Fixtures per page, 50 unless set, at most 250.
- `max_bytes` (integer): Only files of at most this size.
- `offset` (integer): Matches to skip.
- `tag`: Tags to include, any of, e.g. ["encrypted"].

Output parameters:

- `catalog_version` (string)
- `count` (integer)
- `fixtures` (array)
- `limit` (integer)
- `next_offset` (integer|null)
- `offset` (integer)
- `total` (integer)

### `describe_fixture` (~64 tokens)

Describe one loremfile.dev fixture

The published manifest entry for one fixture: its URL, MIME type, size, SHA-256, tags, description and measured properties. Metadata only; fetch the URL for the file.

Input parameters:

- `path` (string, required): A fixture path, e.g. "pdf/minimal.pdf".

Output parameters:

- `added_in` (string|null)
- `bytes` (integer)
- `catalog_version` (string)
- `description` (string)
- `format` (string)
- `mime` (string)
- `path` (string)
- `props` (object|null)
- `sha256` (string)
- `size_class` (string|null)
- `tags` (array)
- `url` (string)

### `verify_file` (~88 tokens)

Verify a local copy of a loremfile.dev fixture

Hash a file on this machine and compare it with the published SHA-256 and size of a fixture. `status` is ok, changed or missing. The file is read only to hash it.

Input parameters:

- `file` (string, required): The local file: absolute, or relative to where the server was started.
- `path` (string, required): The fixture path, e.g. "pdf/minimal.pdf".

Output parameters:

- `actual_bytes` (integer|null)
- `actual_sha256` (string|null)
- `expected_bytes` (integer)
- `expected_sha256` (string)
- `file` (string)
- `path` (string)
- `status` (string)

## Diagnostics

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

## Score history

- 2026-11-05: 92
- 2026-11-04: 91
- 2026-11-03: 91
- 2026-11-02: 90
- 2026-11-01: 90
- 2026-10-31: 89
- 2026-10-30: 89
- 2026-10-29: 89
- 2026-10-28: 88
- 2026-10-27: 88
- 2026-10-26: 87
- 2026-10-25: 87
- 2026-10-24: 86
- 2026-10-23: 86
- 2026-10-22: 85
- 2026-10-21: 82
- 2026-10-20: 82
- 2026-10-19: 82
- 2026-10-18: 82
- 2026-10-17: 82
- 2026-10-16: 82
- 2026-10-15: 82
- 2026-10-14: 82
- 2026-10-13: 50
- 2026-10-12: 49
- 2026-10-11: 34

## Common questions

### What is the loremfile MCP server?

loremfile is an MCP server listed in the public MCP registry as io.github.kumarprabhashanand/loremfile. CC0 sample files and test fixtures: find one, get its URL and SHA-256, check a copy on disk. This page covers its npm package (loremfile).

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

loremfile scores 92 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 loremfile MCP server expose?

loremfile exposes 3 tools: list_fixtures, describe_fixture, verify_file. Their descriptions and schemas cost roughly 300 tokens of context every time the server is loaded.

### Is the loremfile MCP server still maintained?

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

loremfile declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/loremfile
- Socket report: https://socket.dev/npm/package/loremfile
- Repository: https://github.com/kumarprabhashanand/loremfile
- Website: https://loremfile.dev/
- Changelog RSS feed: https://verifymcp.io/servers/kumarprabhashanand-loremfile/loremfile.xml
- Changelog JSON feed: https://verifymcp.io/servers/kumarprabhashanand-loremfile/loremfile.json
- HTML version of this page: https://verifymcp.io/servers/kumarprabhashanand-loremfile/loremfile