us.detritus/account
Detritus Site Services: Your Account
Is the Detritus Site Services MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-10-26.
Manage your Detritus account: sites, services, quotes, invoices, and notifications.
needs auth probed 2026-11-15 · unchanged since 2026-10-26 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error":"unauthorized","message":"Sign in to Detritus to use this connector."}- Endpoint
- https://mcp.detritus.us/manage/mcp (streamable-http)
- Host
- mcp.detritus.us
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://mcp.detritus.us/manage/mcp registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server auth.detritus.us, PKCE S256, grants authorization_code, refresh_token, urn:ietf:params:oauth:grant-type:jwt-bearer.
Scopes customer:read customer:request.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/Detritus-LLC/detritus-main
- Website
- https://detritus.us
- Registry
- active, updated 2026-10-25 · registry entry
Compare this server with others.
More servers
Other registry entries on mcp.detritus.us.
- Detritus Site Services: Get a Quote us.detritus/site-services · alive
Servers that mention account.
- AdAdvisor MCP Server ai.adadvisor/mcp-server · needs auth
- Inside Ads ad.inside/inside-ads · alive
- AIノアカリ☆ One-Minute Akari ai.ai-akari/one-minute-akari · paid (402)
- ai.augmentev/paseo · needs auth
- ai.aqta/seal · alive
- Google Ads ai.b77/google-ads · needs auth
- Bindry ai.bindry/bindry · needs auth
- Boolsai Scan ai.boolsai/scan · needs auth
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.