Provides access to a library of CC0 sample files and test fixtures across various formats for testing and development.
Also known as kumarprabhashanand/loremfile
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- 206
- Latest version
- 0.2.1
- Last commit
- Nov 14, 2026
- License
- MIT
What is loremfile MCP?
loremfile provides access to a library of CC0 sample files and test fixtures across various formats for testing and development.
Summary generated from the project's README
About loremfile MCP server
Loremfile provides a library of CC0 sample files and test fixtures for developers needing diverse data formats. It offers 228 files across 78 formats, including PDFs, images, audio, video, office documents, archives, and even deliberately malformed edge cases. Users can access these files via a remote host at loremfile.dev, which supports hotlinking and byte-range requests without requiring accounts or tracking cookies.
Developers can integrate this service into their workflows using the Python or npm command-line clients, or via a GitHub Action for CI environments. The MCP server implementation runs over stdio and provides three read-only tools: list_fixtures, describe_fixture, and verify_file. This allows AI clients to browse the catalog and validate file integrity using SHA-256 hashes provided in a machine-readable manifest.json file.
What you can do with it
- 1Browse available test filesAn AI agent can search the library to find specific file types for testing purposes.
- 2Verify file integrity in CIA developer can automate the process of downloading fixtures and checking them against known hashes in a GitHub workflow.
- 3Test edge case handlingDevelopers can retrieve corrupted or incomplete files to test how their applications handle errors.
Written from the project's README. Every use case is checked against a quote from it.
How to install loremfile MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall loremfile MCP in Claude Code
$ claude mcp add loremfile -- npx -y loremfileInstall loremfile MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"loremfile": {
"command": "npx",
"args": [
"-y",
"loremfile"
]
}
}
}Install loremfile MCP in VS Code
.vscode/mcp.json
{
"servers": {
"loremfile": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"loremfile"
]
}
}
}Install loremfile MCP in VS Code CLI
$ code --add-mcp '{"name":"loremfile","type":"stdio","command":"npx","args":["-y","loremfile"]}'Install loremfile MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"loremfile": {
"command": "npx",
"args": [
"-y",
"loremfile"
]
}
}
}Install loremfile MCP in Codex
$ codex mcp add loremfile -- npx -y loremfileInstall loremfile MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.loremfile] command = "npx" args = ["-y", "loremfile"]
Install loremfile MCP in Gemini CLI
$ gemini mcp add -s user loremfile npx -- -y loremfileInstall loremfile MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"loremfile": {
"command": "npx",
"args": [
"-y",
"loremfile"
]
}
}
}Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablekumarprabhashanand/loremfile is public and reachablegithub.com/kumarprabhashanand/loremfile ↗Pass
- Package names this repository as its sourceloremfile, loremfile name kumarprabhashanand/loremfile as sourcenpmjs.com/package/loremfile ↗Pass
- Build provenance (Sigstore attestation)Sigstore attestation for loremfile, loremfilenpmjs.com/package/loremfile/v/0.2.1#provenance ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-13github.com/kumarprabhashanand/loremfile ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from loremfile, loremfilePass
- No critical advisory in the package or its dependenciesthe package checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubloremfile
Free, CC0, hotlink-friendly sample files for every file type. Lorem Picsum, but for PDFs, images, audio, video, office documents, data files, archives, fonts, text encodings, raw byte blobs and deliberately malformed edge cases.
https://loremfile.dev/pdf/a4-3pages.pdf
https://loremfile.dev/bin/10mb.bin
https://loremfile.dev/mp4/720p-5s.mp4
https://loremfile.dev/edge/jpg-truncated-50pct.jpg
No ads, no accounts, no rate-limit surprises, no attribution required. Open CORS, byte-range
support, one-year immutable caching, and a machine-readable
manifest.json with SHA-256 hashes for every file.
228 files across 78 formats plus the edge/ set are live, at catalog version 1.2.0. The
specification lives in docs/.
Canonical host
The canonical host is https://loremfile.dev.
This README is the out-of-band pointer: if loremfile.dev is ever unavailable or moves, the
current canonical host is stated here first. Do not rely on any other mirror.
What you can rely on
- The bytes at a published path do not change. Hash, byte count and MIME type stay as
they are; a fix is a new path, and the old entry records
supersededBy. A file may be withdrawn for legal reasons, and the manifest then keeps a tombstone for it. There is no promise of availability; see the terms. - Hotlinking is welcome. That is what this is for. Please keep automated traffic under 30 requests per second per client (the edge rate-limits at 300 requests / 10 s per IP).
- No tracking cookies, no analytics scripts, no accounts.
For agents and CI
/llms.txt: what this service is, in one file./manifest.json: every fixture with path, bytes,sha256, MIME type, tags and format-specific properties./sha256sums.txt: verify downloads withsha256sum -c./{format}/index.json: one format at a time.
GitHub Action
Pull fixtures into a workflow and check each one against its sha256 in the manifest:
- uses: kumarprabhashanand/loremfile/action@action-v1
with:
paths: pdf/minimal.pdf mp4/720p-5s.mp4
formats: svg
It writes to loremfile-fixtures/ and outputs dir and count. A file whose bytes do not
match the manifest fails the step and names the file. catalog-version: "1.2.0" refuses to
run if loremfile.dev has moved on.
The action is shell only and talks to nothing but loremfile.dev. It downloads one file at a
time with a pause between them and backs off on a 429, because the published rate limit
applies to it like any other client. Linux and macOS runners only: it needs sha256sum
or shasum, and Windows is not supported rather than half-supported.
action-v1 is a major tag that moves as the action changes; it is deliberately not a v*
release tag, because those name a catalog version and are frozen once pushed. Pinning a
commit SHA works too and is the strictest option.
Command-line clients
loremfile on PyPI (Python 3.11 or newer) and
loremfile on npm take named files or a whole
format, and write a file only after checking it against its sha256:
npx loremfile get --format pdf
loremfile get pdf/minimal.pdf mp4/720p-5s.mp4 # after pip install loremfile
Neither has a dependency. The Python package declares dependencies = [] and uses only the
standard library; the npm package's package.json lists no dependencies and uses only Node's
built-ins. Installing either installs that one package.
MCP server
Both packages also run a Model Context Protocol server over stdio, with three read-only
tools: list_fixtures, describe_fixture and verify_file. With Node:
{ "mcpServers": { "loremfile": { "command": "npx", "args": ["-y", "loremfile", "mcp"] } } }
With Python, without an install:
{ "mcpServers": { "loremfile": { "command": "uvx", "args": ["loremfile", "mcp"] } } }
It is listed in the
MCP Registry
as io.github.kumarprabhashanand/loremfile, and loremfile.dev/docs/mcp
describes the tools.
Licences
| What | Licence |
|---|---|
Every file served under a format path (/pdf/…, /bin/…, /edge/…) |
CC0 1.0 Universal: public domain, no attribution needed |
| Generators, site and tooling in this repository | MIT |
| Website text and graphics | CC BY 4.0, attribute "loremfile.dev" |
Third-party tools used to generate the files are listed in THIRD_PARTY.md.
No third-party media is redistributed: everything is generated.
Repository
| Path | What |
|---|---|
docs/ |
The full specification, 00–19. Start with docs/README.md. |
catalog/ |
Declarative fixture definitions, one YAML per format. |
src/loremfile/ |
Generators, validators, site builder, uploader, infrastructure code. |
infra/ |
Cloudflare desired state, applied by workflow. |
manifest.json |
Generated lock file, never hand-edited. |
Contributing
Fixture requests and bug reports go in Issues; see
CONTRIBUTING.md for the naming grammar and what makes a good fixture.
Security reports: SECURITY.md.
By opening a pull request you agree that generator code is MIT and any resulting fixtures are CC0.
loremfile MCP questions
How do I add loremfile MCP to Claude Code?
Run claude mcp add loremfile -- npx -y loremfile in your terminal. Add --scope user to make it available in every project.
How do I add loremfile MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What kind of files are available?
The service provides PDFs, images, audio, video, office documents, data files, archives, fonts, text encodings, raw byte blobs, and malformed edge cases.
Do I need to provide attribution for the files?
No, all files served under a format path are licensed under CC0 1.0 Universal, which is public domain and requires no attribution.
Are there any rate limits for automated traffic?
Yes, please keep automated traffic under 30 requests per second per client.