{
  "markdown": "# CiteWire\n\n[![npm](https://img.shields.io/npm/v/citewire)](https://www.npmjs.com/package/citewire)\n[![CI](https://github.com/Openly-Useful/citewire/actions/workflows/ci.yml/badge.svg)](https://github.com/Openly-Useful/citewire/actions)\n[![license](https://img.shields.io/badge/license-MIT-green)](LICENSE)\n\n[citewire.org](https://citewire.org) · [Openly Useful](https://openlyuseful.org)\n\nAttribution-first MCP infrastructure for news and research discovery.\n\nCiteWire gives agents structured, read-only access to news and research\nmetadata while preserving credit and traffic for the original publisher. It\ncan expose a compatible news platform as typed MCP tools, query optional public\nprovider APIs, or do both in one server.\n\nThe Community edition is useful on its own. It includes the MCP core, stdio and\nHTTP transports, the generic platform adapter, and every provider adapter in\nthis repository under the MIT license. Commercial product direction is\nadditive and focused on managed operations, personalization, workflows,\ncollaboration, retained history, and support. See\n[Product tiers](docs/product-tiers.md).\n\n## What CiteWire is for\n\n- **News platform operators** can expose a compatible read API through\n  `news.list`, `news.get`, `news.topics`, and `news.about`.\n- **Researchers and agent builders** can enable only the public news and\n  research providers they want to query.\n- **Self-hosters** can run the same server over stdio, stateless HTTP, or inside\n  a Node serverless function.\n- **Provider contributors** can add a focused adapter without introducing a\n  runtime dependency.\n\nCiteWire is not a full-text ingestion service, crawler, publisher, editorial\nsystem, or rights-clearance service. It does not store or republish article\nbodies. Provider reachability does not replace review of the provider's current\nterms for your use case.\n\n## Quick start\n\nRequirements: Node.js 18 or newer. Community is an ESM-only Node package; it\ndoes not provide a CommonJS entry point.\n\nCreate `citewire.config.json` with one provider enabled:\n\n```json\n{\n  \"providers\": {\n    \"openalex\": { \"enabled\": true }\n  }\n}\n```\n\nRun the server over stdio:\n\n```sh\nnpx -y citewire --config citewire.config.json\n```\n\nstdio is the default transport and is the usual choice when an MCP client\nlaunches citewire as a local process.\n\n### MCP client configuration\n\nUse an absolute config path because clients do not always launch from the\nproject directory:\n\n```json\n{\n  \"mcpServers\": {\n    \"citewire\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"citewire\",\n        \"--config\",\n        \"/absolute/path/to/citewire.config.json\"\n      ]\n    }\n  }\n}\n```\n\n### HTTP transport\n\nRun the stateless HTTP transport on port 8722:\n\n```sh\nnpx -y citewire --config citewire.config.json --http 8722\n```\n\nThe local endpoint accepts JSON-RPC over `POST /`. It does not offer sessions\nor an event stream.\n\n## Two ways to use it\n\n### 1. Wrap a compatible news platform\n\nDeclare a platform with a display name, site URL, and read API base:\n\n```json\n{\n  \"platform\": {\n    \"name\": \"Example Industry News\",\n    \"siteUrl\": \"https://news.example\",\n    \"apiBase\": \"https://news.example/api/v1/news\"\n  }\n}\n```\n\nThat configuration exposes four tools:\n\n| Tool | Purpose |\n| --- | --- |\n| `news.list` | List items newest first, with optional topic, industry, text, date-window, and pagination filters. |\n| `news.get` | Get one item by slug, including attribution and related coverage returned by the platform. |\n| `news.topics` | Read the platform's active topic taxonomy. |\n| `news.about` | Read static platform facts and the attribution policy. |\n\nThe required HTTP surface is documented in the\n[platform read-API contract](docs/platform-contract.md).\n\n### 2. Enable public provider tools\n\nProvider adapters are included in Community and are disabled by default. A\nprovider becomes active only when its config entry sets `enabled` to `true`.\n\n```json\n{\n  \"providers\": {\n    \"gdelt-doc\": { \"enabled\": true },\n    \"arxiv\": { \"enabled\": true },\n    \"crossref\": {\n      \"enabled\": true,\n      \"mailto\": \"operator@example.com\"\n    }\n  }\n}\n```\n\nCrossref requires the deployer's own contact email so requests can identify the\noperator to its polite pool. citewire sends that address only to Crossref in\nthe request `mailto` parameter and `User-Agent`. Do not copy the example\naddress.\n\nThe current adapters are:\n\n| Provider | Tools | Focus |\n| --- | --- | --- |\n| GDELT DOC 2.0 | `gdelt.search` | Worldwide news article metadata |\n| GDELT Context 2.0 | `gdelt.context` | Snippet-level context around a term |\n| arXiv | `arxiv.search` | Preprint metadata |\n| OpenAlex | `openalex.search` | Scholarly works, authors, and venues |\n| Crossref | `crossref.search` | DOI registration metadata |\n| Semantic Scholar | `semanticscholar.search` | Papers and author graph metadata |\n| Europe PMC | `europepmc.search` | Life-sciences literature metadata |\n| dblp | `dblp.search` | Computer-science bibliography records |\n| Hacker News | `hackernews.top`, `hackernews.item` | Stories and items from the official API |\n| DEV | `devto.search` | Published DEV article metadata |\n\nRead [Providers](docs/providers.md) before enabling one. That document records\nthe endpoint, documentation, free-access basis, and known courtesy limits for\neach adapter. The provider's own documentation remains the source of truth.\n\n## Configuration behavior\n\n- `platform` is optional.\n- `providers` is optional.\n- A provider omitted from the config remains disabled.\n- An empty config is valid and exposes no tools.\n- Invalid config fails at startup with the field named in the error.\n- `tools/list` is the authoritative tool list for a running deployment because\n  enabled tools depend on that deployment's config.\n\nA deployment can combine a platform and provider tools:\n\n```json\n{\n  \"platform\": {\n    \"name\": \"Example Industry News\",\n    \"siteUrl\": \"https://news.example\",\n    \"apiBase\": \"https://news.example/api/v1/news\"\n  },\n  \"providers\": {\n    \"openalex\": { \"enabled\": true }\n  }\n}\n```\n\n## Optional Community policy foundation\n\nCiteWire can expose a local, read-only foundation for source policy, rights\nevaluation, and shadow inclusion scoring:\n\n```json\n{\n  \"community\": {\n    \"enabled\": true,\n    \"classifierMode\": \"shadow\",\n    \"thresholds\": {\n      \"adjacent_min\": 0.5,\n      \"standard_min\": 0.6\n    }\n  }\n}\n```\n\nEvery bundled source remains disabled by default. This setting performs no\nnetwork calls, loads no credentials, and cannot publish. Credential-based\nrights checks accept opaque secret-manager references in memory but never\nreturn those references. The classifier is forced to shadow mode and always\nreports `publishable: false` until a separately reviewed editorial system and\nevaluation corpus exist.\n\nRead [Source registry and rights](docs/source-registry-and-rights.md) for the\nruntime validation, fail-closed policy, canonical MCP tools and resources, and\ncurrent limitations.\n\n## Design boundaries\n\n- **MIT and zero dependency.** The package uses Node built-ins and has no\n  runtime or development dependencies.\n- **Node ESM.** Community supports Node.js 18 or newer through ESM. It does not\n  provide CommonJS compatibility or a CommonJS build.\n- **Read only.** The included tools query platform and provider read surfaces.\n- **Stateless.** The Community server has no accounts, sessions, saved searches,\n  or retained history.\n- **Attribution first.** Results preserve source metadata and links supplied by\n  the upstream platform or provider.\n- **Config driven.** A deployer decides which tools are present. Nothing turns\n  itself on.\n- **Storage free.** The core does not retain provider responses or source\n  content.\n\nThese boundaries are maintained through the\n[project governance policy](docs/governance.md).\n\n## Ecosystem and product documentation\n\n- [Product tiers](docs/product-tiers.md) defines the permanent Community value\n  and the additive commercial boundary.\n- [Distribution](docs/distribution.md) contains the exact registry and catalog\n  checklist. Unperformed submissions are marked `PENDING`.\n- [Governance](docs/governance.md) explains decisions, provider stewardship,\n  compatibility, and licensing.\n- [Providers](docs/providers.md) documents each upstream provider.\n- [Platform contract](docs/platform-contract.md) defines the compatible news\n  read API.\n- [Contributing](CONTRIBUTING.md) covers setup, tests, provider additions, and\n  pull request expectations.\n- [Releasing](docs/releasing.md) defines package and registry release controls.\n- [Support](SUPPORT.md), [Security](SECURITY.md), and the\n  [Code of Conduct](CODE_OF_CONDUCT.md) define community operating channels.\n\n## Project origin\n\ncitewire was shaped through its first deployment for\n[Karaya Group Industry News](https://karaya.group/industry-news). The public\nplatform contract is generic and can wrap any compatible read API.\n\n## Contributing\n\nRun the test suite with `npm test`. No install step is required. See\n[CONTRIBUTING.md](CONTRIBUTING.md) before proposing a provider or a change to a\npublic contract.\n\n## License\n\nCommunity is MIT licensed. See [LICENSE](LICENSE).\n",
  "bytes": 9141,
  "sha": "a561b75ac05e135d8ce9232e3ce9ea960d414dd347bb6cdfa7e7e83bcf311209",
  "repo_slug": "openly-useful/citewire",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_openly_useful_citewire_0d11abcd/readme"
}