{
  "markdown": "# mcp-quotes\n\nQuotes MCP — citation-grade quote API for public-domain authors.\n\nPart of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1476+ live data sources.\n\n## Tools\n\n| Tool | Description |\n|------|-------------|\n| `random_quote` | Return a random quote from the corpus, optionally filtered by author, fame, verification status, or tag. Each result includes citation: work, year, speaker (for plays/fiction), and source URL. |\n| `search_quotes` | Search quotes by substring. Matches both canonical text and known popular paraphrases — searching for 'protest' finds Hamlet's 'The lady doth protest too much, methinks' even though the popular form 'Methinks the lady doth protest too much' is what most people remember. |\n| `check_attribution` | Given a quote and (optionally) the author it is claimed to be by, return one of four verdicts: \"verified\" (genuine, with citation), \"misattributed\" (no primary source — popular but fake), \"paraphrase_of_verified\" (popular corruption of a real quote, returns the actual text), or \"no_match\" (not in corpus). Useful for journalists, researchers, and anyone tired of fake Mark Twain quotes. |\n| `quote_by_location` | Look up quotes by structural address within a work — act/scene for plays, chapter for novels. Example: author_id=\"william-shakespeare\", work_title=\"Hamlet\", act=3, scene=1 returns the \"To be, or not to be\" line. |\n| `list_authors` | Return all authors available in the corpus — each entry includes author id (used as input to other tools), display name, birth/death dates, and public-domain status. |\n| `list_full_text_works` | List works for which the full text (every scene, speech, and line) is loaded — beyond just the famous-quote excerpts. Use this to discover what is available for deep structural lookup via get_scene and get_act. |\n| `get_scene` | Return the full text of a specific scene from a play (every speech, every line, in order). Example: author_id=\"william-shakespeare\", work_slug=\"hamlet\", act=3, scene=1 returns the entire \"To be, or not to be\" scene including all of Hamlet's soliloquy and the subsequent dialogue with Ophelia. Useful for context, citation, or close reading. |\n| `get_act` | Return the full text of an entire act (all scenes within it). Use this to read a full structural unit at once. Returned object contains nested scenes with their speeches and lines. |\n| `get_chapter` | Return the full text of a chapter from a novel/prose work (all paragraphs in order). Example: author_id=\"oscar-wilde\", work_slug=\"the-picture-of-dorian-gray\", chapter=2 returns the entire chapter where Lord Henry tempts Dorian. Use list_full_text_works to discover which works are chapter-based. |\n\n## Quick Start\n\nAdd to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):\n\n```json\n{\n  \"mcpServers\": {\n    \"quotes\": {\n      \"url\": \"https://gateway.pipeworx.io/quotes/mcp\"\n    }\n  }\n}\n```\n\n### What this endpoint actually serves\n\n`tools/list` at `https://gateway.pipeworx.io/quotes/mcp` returns the tools in the table\nabove **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,\n`discover_tools`, `search_within`, `remember`/`recall` and the rest of the\ngateway-wide set. So the tool count you see is larger than this table: a\nsingle-pack endpoint currently lists roughly 30 shared tools alongside the\npack's own. The connection's `initialize` response states its exact scope, and\nis the authoritative answer for a given day.\n\nThis is deliberate, not multiplexing by accident. The meta-tools are what let a\nscoped connection answer a question this pack does not cover — via\n`ask_pipeworx`, which routes across the whole catalog — without you adding a\nsecond MCP server. There is currently no way to mount a pack endpoint without\nthem; if the extra schemas cost you more context than the routing is worth,\nconnect to the full gateway once rather than to several pack endpoints.\n\nOr connect to the full Pipeworx gateway to get every pack's tools listed\ndirectly, instead of just this one's:\n\n```json\n{\n  \"mcpServers\": {\n    \"pipeworx\": {\n      \"url\": \"https://gateway.pipeworx.io/mcp\"\n    }\n  }\n}\n```\n\nBoth URLs reach the same gateway and the same 1476+ data sources. The\nonly difference is which pack's tools are listed **directly**; `ask_pipeworx`\nreaches all of them from either one.\n\n## Using with ask_pipeworx\n\nInstead of calling tools directly, you can ask questions in plain English —\nthis works on the pack endpoint above as well as on the full gateway:\n\n```\nask_pipeworx({ question: \"your question about Quotes data\" })\n```\n\nThe gateway picks the right tool and fills the arguments automatically.\n\n## More\n\n- [Docs and guides](https://pipeworx.io/docs)\n- [pipeworx.io](https://pipeworx.io)\n\n## License\n\nMIT\n",
  "bytes": 4726,
  "sha": "802c52709f61c8ee27950a1b6dbe88eea5c4108bf04e806f34007717300e7545",
  "repo_slug": "pipeworx-io/mcp-quotes",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_pipeworx_io_quotes_7a936aaf/readme"
}