loremfile
PYPI · LOREMFILE · 2 COMPONENTS
CC0 sample files and test fixtures: find one, get its URL and SHA-256, check a copy on disk.
Available components
Last scanned (54 minutes ago)
Scores higher than 74% of PyPI servers
Category Documents and Files
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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to kumarprabhashanand/loremfile). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 20 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 360 tokens (~120/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 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
- 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 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 current MCP spec version (2026-07-28).Pass
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 +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.
- 3 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- 1 Nov 26 +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.
- 31 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 29 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- 27 Oct 26 +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.
- 25 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 24 Oct 26 −15
- Malware scan: pass → unverified ▼ security
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 pypi/loremfile@0.2.0
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 | kumarprabhashanand/loremfile |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/kumarprabhashanand/loremfile/.github/workflows/publish-client.yml@refs/tags/client-v0.2.0 |
| Rekor log index | 3135489167 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:0c3a25a174b185cc436917bdb29fe8a14524d4fae100e7315a727043df76331c |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
describe_fixture Describe one loremfile.dev fixture ~64
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.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | A fixture path, e.g. "pdf/minimal.pdf". |
| Name | Type | Req | Description |
|---|---|---|---|
| added_in | string|null | yes | – |
| bytes | integer | yes | – |
| catalog_version | string | yes | – |
| description | string | yes | – |
| format | string | yes | – |
| mime | string | yes | – |
| path | string | yes | – |
| props | object|null | yes | – |
| sha256 | string | yes | – |
| size_class | string|null | yes | – |
| tags | array | yes | – |
| url | string | yes | – |
No examples provided.
list_fixtures List loremfile.dev fixtures ~148
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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"]. |
| Name | Type | Req | Description |
|---|---|---|---|
| catalog_version | string | yes | – |
| count | integer | yes | – |
| fixtures | array | yes | – |
| limit | integer | yes | – |
| next_offset | integer|null | yes | – |
| offset | integer | yes | – |
| total | integer | yes | – |
No examples provided.
verify_file Verify a local copy of a loremfile.dev fixture ~88
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.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | The local file: absolute, or relative to where the server was started. |
| path | string | yes | The fixture path, e.g. "pdf/minimal.pdf". |
| Name | Type | Req | Description |
|---|---|---|---|
| actual_bytes | integer|null | yes | – |
| actual_sha256 | string|null | yes | – |
| expected_bytes | integer | yes | – |
| expected_sha256 | string | yes | – |
| file | string | yes | – |
| path | string | yes | – |
| status | string | yes | – |
No examples provided.
How do I install the loremfile MCP server?
loremfile runs locally as a PyPI package, launched with uvx loremfile. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · loremfile
claude mcp add kumarprabhashanand-loremfile -- uvx loremfile
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 PyPI package (loremfile).
Is the loremfile MCP server safe to use?
loremfile scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 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.