Server Everything vs Realestateapi

A side-by-side look at the Server Everything and Realestateapi 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 protocol55GoodAuth: no auth requiredRealestateapi logoRealestateapiReal Estate · Local subprocess (stdio)RealEstateAPI MCP — property search, detail, and skip-trace (realestateapi.com)59GoodAuth: not declared

Verdict: choose Server Everything for other tools and integrations work as a local process; choose Realestateapi for real estate 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.
Explore Server Everything

Realestateapi logoChoose Realestateapi when

  • You need dedicated capabilities in the Real Estate domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like realestateapi_property_search, realestateapi_property_detail, realestateapi_skip_trace.
Explore Realestateapi

Feature & specification comparison

Rows where the two servers differ are marked.

SpecServer Everything logoServer EverythingRealestateapi logoRealestateapi
CategoryOther Tools and IntegrationsReal Estate
Quality signal55/100 · Good59/100 · Good
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,4050
Directory activity 9 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
ToolsNot listed3

Tools & capabilities

Server Everything tools

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

Realestateapi tools 3

  • realestateapi_property_searchSearch properties by city/state/filters (off-market, absentee-owner, value range) — returns matching properties with address, owner, beds/baths, and estimated value. Example: realestateapi_property_search({ city: "Austin", state: "TX", absentee_owner: true, value_max: 400000, size: 25, _apiKey: "your-key" })
  • realestateapi_property_detailGet full property detail by id or address — returns owner, estimated value, last sale, characteristics (beds/baths/sqft/year/lot), and mortgage. Example: realestateapi_property_detail({ address: "123 Main St, Austin, TX 78701", _apiKey: "your-key" })
  • realestateapi_skip_traceSkip-trace owner contact info for an address — returns the owner name plus phone numbers and emails. Regulated PII: pure passthrough, nothing is stored. Example: realestateapi_skip_trace({ address: "123 Main St, Austin, TX 78701", _apiKey: "your-key" })

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"
      ]
    }
  }
}

Realestateapi

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "realestateapi": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-realestateapi"
      ]
    }
  }
}

Frequently asked questions

Server Everything is categorized under Other Tools and Integrations and uses a local stdio subprocess. Realestateapi belongs to Real Estate and uses a local stdio subprocess. Pick Server Everything for other tools and integrations work and Realestateapi for real estate.

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. Realestateapi 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 realestateapi 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 55/100 (Good) with 9 views, 0 installs and 91,405 GitHub stars. Realestateapi has 59/100 (Good) with 1 views, 0 installs and 0 GitHub stars.