Agentry

QuickAgent Builder

MCP servers that run here

What the MCP server survey saw of every npm package, PyPI package and remote MCP address it reached. Look a server up before you add it to a QuickAgent. The Drafter reads the same list.

Run here
31,234+
works
31,663
signs in
5,618
needs a key
1,289
failed
17,953

59,187 servers in the list, 1 to 50 shown.

How the list was made

Each package was installed with the Agentry runner's builder, started behind its MCP gateway and asked for its tools, with a placeholder for every key and no call made. Each remote address was asked to start a session with no credential, and its sign-in details were read; nobody signed in. A record says what was seen on its date, not that a server suits a task.

Tested 2026-10-09 to 2026-10-26, from the MCP Registry, Smithery and GLAMA: 59,187 packages and addresses. Docker images, MCPB bundles and servers built from source are not in it, because a QuickAgent declares a server from npm, PyPI or an https:// address. A failed server may only need a setting or a host its catalogue entry did not name.

works:
A package installed with the runner's builder, started behind the gateway and listed its tools; a remote address listed its tools with no credential.
signs in:
A remote address that publishes OAuth sign-in details the CLI accepts. Nobody signed in, so its tools were not listed.
needs a key:
A remote address that refused an anonymous request and publishes no OAuth details: it wants a key, sent some other way.
failed:
Did not install, did not start or list a tool, listed none, or as a remote address was unreachable or refused the probe.
cannot be declared:
An address a QuickAgent's manifest cannot declare: a placeholder, a port, a query or a key in it.

The list as JSON: /build/mcp-servers/lookup?q=… (with kind, status, limit and offset).

Agentry uses only strictly necessary cookies — they sign you in and keep the site secure. Nothing here tracks you, and there are no advertising or analytics cookies. Privacy policy