Hyperresearch

ai.hyperresearchPublished by hyperresearch.aiOfficial publisherv1.0.0Updated Oct 24, 2026

Start cited deep-research runs, read reports, search your source vault, and verify citations.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingKnowledge & Memory

Overview

AI-generated overview

A remote MCP server that lets an assistant start cited deep-research runs, read the resulting reports, search a source vault and verify citations.

What you can do
Start cited deep-research runs and read the resulting reports. Search a personal source vault. Verify citations in reports. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Useful when you want an assistant to run sourced research and work with the resulting reports and citations, rather than answering from its own knowledge. Suited to fact-checking or citation-backed writing where sources must be traceable.
Requirements
A remote endpoint at mcp.hyperresearch.ai over streamable HTTP. OAuth authentication is required, so a Hyperresearch account is needed. No environment variables or headers are declared.
Before you install
Access is tied to an OAuth account, and research runs may consume a paid plan or quota, which the input does not specify. Research queries and vault searches are sent to a third-party service. Reports and citations should be checked before being relied on.

Installation

In SourceWeft

  1. Open Hyperresearch 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/ai.hyperresearch%2Fhyperresearch/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": {
    "hyperresearch": {
      "type": "http",
      "url": "https://mcp.hyperresearch.ai/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 30, 2026

Score

67% 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
  • 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.

Other Hyperresearch integrations