LinkList

io.linklistPublished by linklist.ioOfficial publisherv1.0.0Updated Oct 24, 2026

Search source collections your team vetted. Every passage cites its URL and fetch date.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingKnowledge & Memory

Overview

AI-generated overview

Lets an assistant search source collections vetted by your team, with every passage citing its URL and fetch date.

What you can do
LinkList provides search over source collections that a team has vetted. Results return passages, and each passage carries the URL it came from and the date it was fetched, so answers can be traced back to a specific source. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Useful when an assistant needs to draw on curated, team-approved sources rather than the open web, and when citations with URLs and fetch dates matter for verification.
Requirements
A remote MCP endpoint at linklist.io reached over streamable HTTP. Authentication is OAuth and is required; no environment variables or headers are declared.
Before you install
Access is tied to an OAuth sign-in, so the assistant acts with your account's permissions on your team's collections. The manifest does not describe what data is sent to the service or whether searches are logged.

Installation

In SourceWeft

  1. Open LinkList in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.linklist%2Flinklist/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "linklist": {
      "type": "http",
      "url": "https://linklist.io/mcp"
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

56% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.