Hosted MCP server/Other

Quiet Menders MCP server

Hosted at quiet-menders-mcp.brianbooms.workers.dev·Streamable HTTP

Quiet Menders exposes 34 MCP tools. Ten clinic and waystation tools are free, including prompt-injection scrubbing, machine-file validation, endpoint probes, and clinic diagnosis. Twenty-two data-lane tools cost $0.01 to $0.10 per call and two commerce tools expose a 24-SKU catalog from $0.05 to $299.00. Paid calls are two-phase: call without a payment argument to receive a live 402 challenge, sign it in your own x402 client, then re-call with the base64 payment payload. The server never signs, pays, or holds funds.

quiet-menders-mcp.brianbooms.workers.dev Streamable HTTP Free clinic/waystation tools need no key; data-lane and commerce tools require caller-signed x402 USDC on Base Server not checked yet Reviewed 2026-11-16
About

Where it fits

Developers who want free privacy and validation utilities in an agent and are willing to use x402 for data-lane extras.

  • Scrub a prompt or document for injection attempts.
  • Validate a site's llms.txt, agent.json, and robots.txt.
  • Read a data-lane 402 challenge before paying in USDC.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Setup

Install it in your client

Choose a client, run the command or use the one-click install, then verify the connection. The endpoint uses Streamable HTTP.

All client guides
  1. 01

    Run this command in your terminal

    This adds Quiet Menders as a remote Streamable HTTP server in Claude Code.

    Claude Code
    claude mcp add --transport http quiet-menders https://quiet-menders-mcp.brianbooms.workers.dev/mcp --scope project
  2. 02

    Verify the connection

    Run claude mcp list, or open /mcp in a Claude Code session.

    Learn more about MCP in Claude Code

More clients, including project and global config files, are in the sidebar.

Connection

Endpoint and configuration

Endpoint
https://quiet-menders-mcp.brianbooms.workers.dev/mcp
Host
quiet-menders-mcp.brianbooms.workers.dev · /mcp
Transport
Streamable HTTP
Authentication
Free clinic/waystation tools need no key; data-lane and commerce tools require caller-signed x402 USDC on Base
Server name
quiet-menders
Listing type
Community or directory listing

The installer uses the server name quiet-menders. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that quiet-menders appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Scrub a prompt or document for injection attempts. Check the result before you give the server more access.

  3. 3
    Check permissions.

    Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.

Server not checked yet

We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. A provider page is linked but was not included in the automated check. Open it before setup.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • Authentication fails or no tools appear. The listing does not verify the provider's credential flow; check its documentation before retrying.
  • The endpoint responds but rejects tool calls. Confirm the current address and any account, key, or payment requirement with the provider.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider source

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

Quiet Menders repositoryhttps://github.com/brianbooms/quiet-menders