Quick Verdict
SansFiction is a hosted book catalog and reading-library service with a Streamable HTTP MCP endpoint at https://sansfiction.com/api/mcp. Its clearest use is letting Claude, Cursor, or another MCP client search public books, authors, editions, series, and curated collections. After account authorization, tools can read or change a user’s shelves, reading progress, and statistics. Public catalog tools are anonymous; personal-library tools require OAuth 2.1 or a user-created bearer token.
As of July 21, 2026, access is publicly free, but the site does not clearly disclose a legal operator, SLA, retention periods, a complete privacy policy, catalog-data licensing, or a source-code license for the hosted server. It is reasonable for low-risk personal experiments, but not yet a strong default for sensitive reading records, institutional research, or commercial redistribution. The correct category is MCP rather than agent: SansFiction supplies hosted tools and catalog data that an agent can call.
Best For
- MCP learners who want a hosted Streamable HTTP example without local deployment
- Individual readers who want conversational book search and shelf management
- Workflow developers testing OAuth, catalog queries, and personal-library writes
- Catalog prototypes using public metadata for low-risk discovery experiments
- Not ideal for organizations requiring an SLA, data-processing terms, auditable server source, sensitive-note storage, or explicit commercial data rights
Key Features
- Anonymous catalog search for books, authors, ISBNs, editions, series, and curated collections
- Public content retrieval for available metadata, reviews, journals, and collection pages
- Personal library tools to list shelves, change status, log progress, and inspect statistics after authorization
- Hosted MCP endpoint whose Server Card advertises tools, but not resources, prompts, or logging capabilities
- OAuth and manual tokens with OAuth 2.1 recommended and account-scoped bearer tokens available for clients without OAuth
- Explicit scopes:
library:readandlibrary:write, with write access capable of changing personal data - Discovery documents including an API catalog, OpenAPI description, authentication metadata, MCP Server Card, and agent instructions
Use Cases
- Search for an author, publication year, ISBN, edition, or series from an MCP client
- Retrieve available edition details, page counts, public reviews, and curated collections
- List currently reading books, log a page, or mark a title finished after user consent
- Test
library:read,library:write, revocation, and error handling with a restricted account - Combine public catalog queries with research tools such as OpenAlex MCP Server without assuming their licenses are interchangeable
Pricing
The site offered the public catalog and MCP access for free at the cutoff date. It did not publish plan tiers, quotas, a paid roadmap, or an availability commitment. Do not infer an unannounced premium tier. A free hosted service can change rate limits, fields, scopes, or its business model, so production clients need timeouts, caching, retries, quota handling, and a fallback source.
The MCP Server Card reports version 1.0.0, but that is a service version, not a licensed source release. The site does not clearly grant rights to bulk-copy catalog data, reviews, journals, or collections, use them for model training, or redistribute them commercially. Public accessibility is not the same as an open-data license.
Pros
- No local deployment required for Streamable HTTP MCP testing
- Anonymous public catalog tools lower the trial barrier
- Personal access uses explicit
library:readandlibrary:writescopes - Good machine-discovery surface with Server Card, OpenAPI, and auth metadata
- OAuth is recommended and manual-token revocation is documented
Cons
- Legal operator, business address, and service responsibility are not clearly disclosed
- No sufficiently detailed privacy, request-log, retention, deletion, or backup policy
- No public SLA, rate-limit commitment, status page, or paid support terms
- Catalog provenance and reuse rights for metadata, reviews, and collections are unclear
- No explicit open-source license for the hosted server
library:writecreates real risk from mistaken calls, prompt injection, or token leakage- A young service should not be the only copy of a long-term reading history
Alternatives
| Tool | Best for | Strength | Limitation |
|---|---|---|---|
| BGG MCP | Board-game catalog users | Direct vertical catalog MCP | Not a book-reading library |
| OpenAlex MCP Server | Scholarly works and author discovery | Better fit for research metadata | Does not manage a general personal bookshelf |
| Filesystem MCP Server | Locally controlled reading records | Files and storage location remain under user control | You design the schema and discovery workflow |
| Google Drive MCP Server | Teams already keeping lists in Drive | Reuses existing documents | Broader permissions and weaker catalog specialization |
SansFiction is more convenient when you want catalog and personal-library tools together. Filesystem MCP Server offers more data control, while OpenAlex MCP Server is more aligned with scholarly discovery.
FAQ
Is SansFiction MCP free?
It was publicly free as of July 21, 2026, with no published paid tiers. Pricing, quotas, and available tools can still change.
Does public catalog search require login?
No. Official documentation says public catalog tools are anonymous. Personal shelves, progress, and statistics require authorization.
What do library:read and library:write mean?
library:read reads personal-library data. library:write can change shelf state and progress. Clients should request only the minimum scope required.
How long does SansFiction retain queries and reading data?
The public documents available at the cutoff do not provide a sufficiently clear log and retention schedule. Privacy-sensitive users should ask the operator rather than assuming OAuth or HTTPS means no logging.
Can catalog data be used commercially or for model training?
Public API access does not establish those rights. Catalog provenance, review copyright, bulk extraction, training, and redistribution permissions need explicit clarification.
How can I reduce write-tool risk?
Start anonymous or read-only, test with a separate account, secure the token outside source control, require visible approval for writes, and revoke unused tokens.
Bottom Line
SansFiction is a convenient hosted MCP service for experimenting with book discovery and authorized personal-library actions. Anonymous catalog access, OAuth, and explicit library scopes are useful. The limiting factor is policy maturity: operator identity, privacy, retention, SLA, provenance, and licensing remain insufficiently clear. Start with anonymous search, keep exports or a fallback, and obtain explicit rights and processing terms before institutional or commercial use.