Research Mcp

io.github.varvararattaPublished by GitHub account varvararattav1.0.0Updated Nov 2, 2026

MCP server for Research

VerifiedStreamable HTTPWeb executable

Overview

AI-generated overview

A hosted, zero-auth MCP endpoint labeled "Research", part of a farm of public MCP servers; its actual tools are not documented.

What you can do
  • The manifest lists no tools, and the description only says it is an MCP server for research.
  • The README describes a hosted farm of public MCP servers with a free health check and discovery tools, plus paid tools.
  • Paid tools are said to require an x402-capable MCP client, with payment in USDC on Base.
  • No research-specific capabilities, inputs or outputs are described anywhere in the supplied material.
When to use it
Only worth trying if you specifically want to probe a hosted endpoint named "Research" and are prepared to discover its tools by connecting. Because nothing documents what it does, it is a poor fit for a production or data-sensitive workflow.
Requirements
A remote streamable HTTP endpoint; no package, environment variables or headers are declared. The README says paid tools need an x402-capable MCP client, and that health check and discovery tools are free. Network access to the hosted endpoint is required.
Before you install
The README states that some tools are paid via x402 in USDC on Base, so connecting could involve spending cryptocurrency; treat any payment prompt with care. The server's real tools are undocumented, so what it reads, writes or sends to third parties is unknown. No authentication is declared, so do not send sensitive data to it.

Installation

In SourceWeft

  1. Open Research Mcp in the dashboard and add it to a workspace.
  2. 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.github.varvararatta%2Fresearch_mcp/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.

{
  "mcpServers": {
    "research": {
      "type": "http",
      "url": "https://research-mcp.mcpize.run/mcp"
    }
  }
}

README

BotFactory MCP Farm

Hosted MCP servers on MCPize — zero-auth public APIs, freemium x402 (USDC on Base).

Catalog

See CATALOG.md for the full list with gateway URLs.

Connect

https://<slug>.mcpize.run/mcp

Requires an x402-capable MCP client for paid tools. health_check and discovery tools are free.

Awesome list entries

See AWESOME_ENTRIES.md.

Source: README.md at commit 14e36b4

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

75% 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 listedRequired15 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

    Declare a license in the repository or the registry entry.