@pipeworx/mcp-chronicling-america
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Contacts while installing and starting: gateway.pipeworx.io
What it contacted
gateway.pipeworx.io
Hosts it looked up or connected to while installing and starting with no input, watched from outside its sandbox. The npm registry is left out. Says nothing about what its tools contact when called.
Starting it
npx -y @pipeworx/mcp-chronicling-america@0.2.1
Installing a package runs its code. Use a sandbox for anything you have not read.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
search_newspapers query, date_from, date_to, state, limit
Full-text search of digitized historical U.S. newspapers (~1690s–present) from the Library of Congress "Chronicling America" collection. Find primary-source newspaper coverage of any person, event, place, or topic in history — returns the total match count, then for each page the newspaper, publication date, city/state and a link to the digitized page (plus an OCR text excerpt of the matching page for covered states such as Montana). Filter by date range and U.S. state; every response carries data_as_of. Example: search_newspapers({ query: "influenza epidemic", date_from: "1918", date_to: "1919", state: "oklahoma" }).Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Install facts
| License | MIT |
|---|---|
| Needs | node >=18 |
| Source | github.com/pipeworx-io/mcp-chronicling-america |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-mcquRY8y9V1ZLTxNucAcRyHhXOMuudrqblJUHnuMJJIghOUHIOnDK6Jec2ac9p37Z0mvp86qOKgdP7JY14nd6g== |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/%40pipeworx/mcp-chronicling-america)
New version out? Ask for a fresh report.