Citesearch

io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 3, 2026

Search, read and trace links across the Edgepedia encyclopedia corpus.

VerifiedSTDIODesktop only

Overview

Citesearch's local MCP server; no sign-in required; STDIO.

No AI overview yet: these facts come from the registry entry and the server itself.

Installation

In SourceWeft

  1. Open Citesearch in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

citesearch

citesearch is a small client for Edgepedia, a standalone encyclopedia corpus of (per its own release notes) some 486,000 articles, each with its own id and credit line. It can search the corpus by subject, read an article or topic in full, list the articles related to one you already have, trace the chain of in-text links between two articles, and pin down which article an ambiguous name refers to when you give it a little surrounding context. One binary serves a command-line interface and a stdio MCP server.

There is no account and no API key. Under the hood, both faces forward each request to the hosted Edgepedia endpoint at https://www.edgechat.ai/mcp and print the text it returns. Articles carry a credit line; where the upstream text includes it, it is shown as returned — please keep it attached wherever you reuse the article text.

Install

bash
npx @reneturcios/citesearch search koala

Or run the container image:

bash
docker run -i ghcr.io/cloudcorprecords/citesearch

The container defaults to the MCP server (see below). Pass CLI arguments to use it as a CLI instead.

CLI

bash
citesearch search Mount Fujicitesearch fetch ep9kcz7eymcitesearch fetch ep9kcz7eym --no-citationscitesearch related ep9kcz7eymcitesearch connect epStart epTargetcitesearch resolve Jaguar --context "British car maker"
citesearch --version

Results print as plain text — a search returns matching articles with their ids, titles, links and summaries; a fetch returns one article as Markdown with its link, date, topic, license and credit line; a resolve answer names the article meant, its confidence and the alternatives. Exit codes: 0 on success, 1 when the upstream request fails, 2 for usage errors. Arguments are validated before any request is made.

Notes on fetch: with citations on (the default) an article's sources appear as inline links; --no-citations asks for [n] markers instead, which reads about a quarter shorter. The upstream documentation also mentions fetching several ids at once, a single section, a token budget, or only matching passages — but it does not publish parameter names for those controls, so this client does not invent any: fetch takes exactly one id and the citations switch.

MCP server

One bin serves both faces. The mcp subcommand starts a stdio MCP server:

bash
npx -y @reneturcios/citesearch mcp

MCP client configuration:

json
{  "mcpServers": {    "citesearch": {      "command": "npx",      "args": ["-y", "@reneturcios/citesearch", "mcp"]    }  }}

Tools

All five tools are read-only and key-free.

ToolInputWhat it returns
searchquery (string) — a subject's name, not a questionMatching articles: id, title, link and summary (or the article opening when there is no summary). Other names and misspellings work, and topic phrases return the topic.
fetchid (string); citations (boolean, optional)One article as Markdown, with its link, date, topic, license and credit line. A topic's id lists its articles. citations: false swaps inline source links for [n] markers.
relatedid (string)Articles related to it: its topic-mates, a few from each neighbouring topic, and its geography neighbours.
connectfrom (string), to (string)The shortest chain of in-text links from one article to the other (at most 6 hops), with the sentence that makes each hop.
resolvename (string); context (string, optional)Which article the name means, with a confidence and the alternatives. For example, "Jaguar" beside "British car maker" is the car company; beside "big cat" it is the animal.

Development

bash
npm installnpm run build   # tsc -> dist/npm test        # node test runner over test/*.test.ts, no network (fake fetch only)npm run dev     # run the CLI from source via tsx

License

MIT — see LICENSE. (This license covers this client; Edgepedia article text is under its own license and carries its own credit line.)

Source: README.md at commit 11bba53

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestNov 3, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts