Everyrow MCP Server

io.github.futuresearchPublished by GitHub account futuresearchv0.5.1Updated Oct 24, 2026

Give your AI a research team. Forecast, score, classify, or research every row of a dataset.

VerifiedSTDIODesktop onlyData & AnalyticsAI & ML

Overview

AI-generated overview

A local MCP server that lets an assistant run bulk research, forecasting, scoring and classification across every row of a dataset through the Everyrow service.

What you can do
Send a dataset to Everyrow for row-by-row processing, such as forecasting, scoring, classifying or researching each row. Use it to enrich or label tabular data in bulk rather than one item at a time. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Useful when you have a table of items and want an assistant to research, forecast, score or classify each row at scale, instead of handling rows one by one in conversation.
Requirements
Runs locally as a Python package launched with uvx, so a Python/uv runtime is needed. Requires an Everyrow API key supplied through the EVERYROW_API_KEY environment variable. Network access to the Everyrow service is implied. Desktop only.
Before you install
The server needs an Everyrow API key, which is a secret; keep it out of shared logs and configuration. Dataset rows are sent to the third-party Everyrow service for processing, so avoid submitting sensitive or regulated data without checking its terms. Bulk runs may consume paid service quota.

Installation

In SourceWeft

  1. Open Everyrow MCP Server 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

This repository has no README.

Tools

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

Version history

1
  1. v0.5.1LatestSep 16, 2026

Score

35% 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

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

  • License10 pts