Storage, privacy & limits
Temporary by design
Section titled “Temporary by design”iiiftools is not an archive. Downloaded images exist only to serve the current working session:
- Each
resolveopens an extraction with a 2-hour TTL. releasedeletes an extraction’s images immediately; the dashboard has a Release button too.- A background sweeper runs every few minutes: it deletes the files of expired extractions and removes orphaned directories.
- The store has a global cap (5 GB); when full, downloads fail with a clear message until space is released.
What persists after cleanup is only metadata: the source URL, the manifest URL, canvas labels/dimensions of what was fetched, sizes, and checksums — the record of what was accessed, not the images themselves.
Signed links
Section titled “Signed links”delivery="url" returns links like:
https://iiiftools.pangur.io/files/<token>/<filename>The token is an HMAC signature over the file identity and an expiry timestamp — the link is the credential. That is deliberate: assistants fetch these with a plain GET, no OAuth. Properties:
- Scoped to exactly one file.
- Expire after ~30 minutes (tampering or expiry → HTTP 410).
- Unguessable without the server’s signing key.
Treat a signed link like a capability: anyone holding it can fetch that one image until it expires. Re-request links rather than saving them.
Authentication & audit
Section titled “Authentication & audit”- The MCP endpoint is an OAuth 2.1 protected resource; every tool call carries your token, validated against the iiiftools auth realm.
- Extractions are per-account: your tools only see your own sessions.
- Every tool invocation is written to an audit log (tool, arguments, status).
Limits at a glance
Section titled “Limits at a glance”| Limit | Value |
|---|---|
| Extraction TTL | 2 hours |
| Signed-link TTL | ~30 minutes |
| Inline image size | ≤1568px long edge, ~1.5 MB encoded |
Batch size (get_page_range) | 10 canvases |
| Temp store cap | 5 GB total |
Copyright
Section titled “Copyright”iiiftools fetches images the source library already serves publicly over IIIF, on your instruction, for transient use. The source libraries’ terms of use apply to what you do with the images — check the licence noted in each manifest’s metadata.