CarryFeed

io.github.christian-beep383Published by GitHub account christian-beep383v0.1.1Updated Oct 24, 2026

Resolve public X/Twitter profiles, posts, and media through CarryFeed.

VerifiedSTDIODesktop onlyWeb Search & ScrapingMedia & Design

Overview

AI-generated overview

CarryFeed is a local MCP server that lets an assistant resolve public X/Twitter profiles, posts, articles and media through CarryFeed's hosted API.

What you can do
Check CarryFeed API health and resolve public X/Twitter links or IDs into profile, post and article data via a hosted resolver service. Fetch public profile metadata by handle, recent public statuses, and recent public media posts for a profile. List media candidates exposed by a public post and build CarryFeed download proxy URLs for returned media. The package is a wrapper around the hosted API and does not include the resolver implementation.
When to use it
Useful when an assistant needs to look up public X/Twitter profiles, posts or media from links or IDs without browser login flows or custom scraper code. Not suitable for private, protected, deleted, restricted or login-only content.
Requirements
Runs locally over stdio, typically via npx with the npm package @carryfeed/mcp, so Node.js and network access to the CarryFeed API are needed. The optional CARRYFEED_API_BASE_URL variable overrides the default API base URL. No authentication is declared.
Before you install
Requests go to CarryFeed's hosted API, so the links and handles you resolve are sent to that third party. It only covers public X/Twitter content and is not an official X/Twitter API. The download URL tool builds proxy URLs for returned media; check where those point before fetching.

Installation

In SourceWeft

  1. Open CarryFeed 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

@carryfeed/mcp

MCP server for CarryFeed's hosted public X/Twitter profile, post, article, and media API.

CarryFeed gives agents one source-preserving way to resolve public X/Twitter links without browser login flows or internal scraper code. This package is a wrapper around the hosted CarryFeed API; it does not include CarryFeed's internal resolver implementation.

Install

Run directly with npx:

bash
npx -y @carryfeed/mcp

Or install locally:

bash
npm install @carryfeed/mcp

MCP Config

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

Tools

  • carryfeed_health: check API health.
  • carryfeed_resolve: resolve a public X/Twitter profile, post, article-style link, or id.
  • carryfeed_media: list media candidates exposed by a public post.
  • carryfeed_profile: resolve public profile metadata by handle.
  • carryfeed_profile_statuses: fetch recent public statuses for a profile.
  • carryfeed_profile_media: fetch recent public media posts for a profile.
  • carryfeed_post: resolve a public post by id.
  • carryfeed_download_url: build a CarryFeed download proxy URL for returned media URLs.

Environment

  • CARRYFEED_API_BASE_URL: optional API base URL. Defaults to https://api.carryfeed.com.

Boundaries

CarryFeed works with public X and Twitter links only. It does not unlock private, protected, deleted, restricted, or login-only content, and it is not an official X/Twitter API.

Links:

Source: packages/mcp/README.md at commit fc07ae4

Tools

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

Version history

1
  1. v0.1.1LatestSep 16, 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