Server Everything vs Sourceright

A side-by-side look at the Server Everything and Sourceright MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Server Everything logoServer EverythingOther Tools and Integrations · Local subprocess (stdio)MCP server that exercises all the features of the MCP protocol73GreatAuth: no auth requiredSourceright logoSourcerightResearch · Local subprocess (stdio)Reference verification MCP server for CSL bibliographies, evidence, and audited writes.45FairAuth: not declared

Verdict: choose Server Everything for other tools and integrations work as a local process; choose Sourceright for research as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Server Everything logoChoose Server Everything when

  • You need dedicated capabilities in the Other Tools and Integrations domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like echo, get-annotated-message, get-env.
Explore Server Everything

Sourceright logoChoose Sourceright when

  • You need dedicated capabilities in the Research domain.
  • You prefer a local stdio subprocess transport.
Explore Sourceright

Feature & specification comparison

Rows where the two servers differ are marked.

SpecServer Everything logoServer EverythingSourceright logoSourceright
CategoryOther Tools and IntegrationsResearch
Quality signal73/100 · Great45/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars91,5501
Directory activity 10 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
Tools16Not listed

Tools & capabilities

Server Everything tools 16

  • echoEchoes back the input string
  • get-annotated-messageDemonstrates how annotations can be used to provide metadata about content.
  • get-envReturns all environment variables, helpful for debugging MCP server configuration
  • get-header-paramsReturns its region argument and the Mcp-Param-Region HTTP header it arrived in. Demonstrates x-mcp-header (a 2026-07-28 Streamable HTTP client mirrors the argument into the header) and JSON Schema 2020-12 input and output schemas.
  • get-resource-linksReturns up to ten resource links that reference different types of resources
  • get-resource-referenceReturns a resource reference that can be used by MCP clients
  • get-structured-contentReturns structured content along with an output schema for client data validation
  • get-sumReturns the sum of two numbers
  • get-tiny-imageReturns a tiny MCP logo image.
  • gzip-file-as-resourceCompresses a single file using gzip compression. Depending upon the selected output type, returns either the compressed data as a gzipped resource or a resource link, allowing it to be downloaded in a subsequent request: during the current session for a 2025-era client, or for ten minutes at a minted URI on protocol version 2026-07-28.
  • trigger-list-changedSends a notifications/<list>/list_changed for the tool, prompt or resource list. On protocol version 2026-07-28 it is delivered on each subscriptions/listen stream that asked for that list; a 2025-era client receives it unsolicited.
  • trigger-log-messagesSends one log message at each logging level during the call. On protocol version 2026-07-28 only the messages at or above the level the request names in _meta (io.modelcontextprotocol/logLevel) are sent, and none if it names no level; a 2025-era client gets those at or above the level it set with logging/setLevel. Deprecated: logging is deprecated as of protocol version 2026-07-28.
  • +4 more on the listing page

Sourceright tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Server Everything

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "modelcontextprotocol-server-everything": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-everything"
      ]
    }
  }
}

Sourceright

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "sourceright": {
      "command": "npx",
      "args": [
        "--yes",
        "markdownlint-cli2@0.18.1"
      ]
    }
  }
}

Frequently asked questions

Server Everything is categorized under Other Tools and Integrations and uses a local stdio subprocess. Sourceright belongs to Research and uses a local stdio subprocess. Pick Server Everything for other tools and integrations work and Sourceright for research.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Server Everything is listed as free. Auth: no auth required. Sourceright has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add modelcontextprotocol-server-everything and sourceright as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Server Everything has a quality signal of 73/100 (Great) with 10 views, 0 installs and 91,550 GitHub stars. Sourceright has 45/100 (Fair) with 2 views, 0 installs and 1 GitHub stars.