BigHugger

MCP servers with a whoami tool, you can run either way, over streamable-http

An MCP server is something you connect an agent to. The registry will tell you a server's name, its version and how to reach it — but not what it can do, which is the only thing you actually want to know. We read that off the repository.

31,279 servers, 76,670 tool names across 6,537 of them, last read 11 September 2026.

A server's tools are not in the registry. We read them from the repository README, which means a list here is what the README documented and an absence is usually silence rather than a server with nothing to offer: 20.9% of servers have a list, and filtering on tools narrows to those. Where a list exists, the page for the server says which part of the README it came from.

  1. mcpcom.shipstatic

    Deploy static websites from AI agents. Free at mcp.shipstatic.com — no install, no signup.

    bothstreamable-httpstdio15 toolsneeds a credential
  2. mcpio.github.affset

    Run affset from chat: stats, campaigns, zones, payouts, targeting, and team.

    bothstreamable-httpstdio29 toolsneeds a credential
  3. mcpio.artifacta

    Artifact store for AI agents. Hosted OAuth at mcp.artifacta.io/mcp; local stdio via npm/PyPI.

    bothstreamable-httpstdio13 toolsneeds a credential
  4. eodly-mcpio.github.layergen

    Read your team's end-of-day reports and roster from Eodly.

    bothstreamable-httpstdio4 toolsneeds a credential
  5. agentdocs-mcpio.github.hoornet

    AgentDocs (agentdocs.eu) MCP: read, search, write, comment, share & attach images to Markdown docs.

    bothstreamable-httpstdio19 toolsneeds a credential
  6. mcpio.routescore

    Read-only pre-sign evidence for onchain agents: route quality, MEV exposure, clear/caution verdict.

    bothstreamable-httpstdio8 toolsneeds a credential

Browse all 31,279 servers200 at a time, grouped by owner. The list above is the servers with the highest standing; this is every one of them.

Live servers only. The whole corpus is one call away through the search API — including tools=, which is how you ask for a server by what it does rather than by what it is called.