← All launches
0 Report

BotThru

by FastDrop

MCP Verified 5 days ago Registry import free

Agent drive-thru: open ask window, UTC time, UUID, echo, and whoami. No auth.

Agent drive-thru: open ask window, UTC time, UUID, echo, and whoami. No auth. Official MCP Registry: com.botthru/drive-thru@0.1.0. Remote endpoint: https://botthru.com/mcp

Problem it solves

Discoverable MCP server listed in the official MCP Registry.

How it's different

Remote MCP endpoint ingested from the official registry and probed by FastDrop.

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as com.botthru/drive-thru and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Claim this listing

Tools this endpoint exposes

Read directly from the endpoint on 17 Nov 2026. Not supplied by the maker.

  • ask

    Order window. need is required. status is answered only when time, uuid, echo, or whoami ran; routed is a pointer; unsupported means the need was logged as demand. Do not send secrets or personal data

  • time

    Current UTC time, plus the same instant in an IANA time zone. Defaults to UTC.

  • uuid

    One random UUID (crypto.randomUUID).

  • echo

    Headers, country, and bot classification of this MCP HTTP request. Cookie and authorization values are redacted.

  • whoami

    Which bot BotThru thinks is calling, and why.

Is this tool yours?

Claim this listing, then prove you own the domain with one DNS record: once it matches, the listing is yours right away.

Sign in to claim this listing

Matched on shared tags and the tools their MCP servers actually expose.

Reviews

Sign in to leave a review.

No reviews yet.

Comments

Sign in to join the discussion.

No comments yet - start the discussion.