Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Citesearch

by CloudCorpRecordsversion 0.1.0i★ –iRuns on your computer
Registry nameio.github.CloudCorpRecords/citesearch

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Search & AI memory

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • The registry lists no key to fill in.

You need

  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

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

Run this in your terminal

claude mcp add citesearch -- npx -y @reneturcios/citesearch mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "citesearch": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/citesearch",
        "mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account CloudCorpRecords, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Search & AI memoryi

  • More stars than 0% of the other 7229 servers in this category
  • Published to the registry more recently than 89% of the other 7229 servers in this category
  • Basic checks equal to or better than 100% of the other 7229 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Citesearch safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 4 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Docker on your computer.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated 3 days ago
Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 20 days ago
Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated 44 days ago
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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

npx @reneturcios/citesearch search koala

Or run the container image:

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

citesearch search Mount Fuji

citesearch fetch ep9kcz7eym citesearch fetch ep9kcz7eym --no-citations citesearch related ep9kcz7eym citesearch connect epStart epTarget citesearch 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:

npx -y @reneturcios/citesearch mcp

MCP client configuration:

{

"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

npm install

npm 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.)

Ask PopNx