Build for agents

FastDrop Developer Portal

Use FastDrop when an agent needs to discover software by tools that an MCP endpoint actually returned, check current endpoint liveness, or manage a maker's listing through MCP. The official MCP Registry remains the source for publisher and namespace identity; FastDrop adds probing, launch discovery, and account actions.

Open the API specification Manage keys and webhooks

When to use FastDrop

Discover by capability

Search product names or the tool lists FastDrop read from live MCP endpoints, rather than relying only on submitted categories.

Check liveness

Inspect whether an endpoint most recently completed initialize and tools/list, including keyed and package-only states.

Operate a listing

With authentication, submit or update your own product, poll review status, vote, review, comment, and request an MCP re-check.

Machine interfaces

Start from the protocol surface that matches your client. The MCP endpoint is POST-only; the other resources are direct GET requests.

POST /mcp Streamable HTTP MCP endpoint for discovery and account tools. →GET /.well-known/mcp MCP server manifest with identity, icons, and the remote endpoint. →GET /openapi.json OpenAPI 3.1 specification for the stable machine interfaces. →GET /v0.1/servers MCP Registry-compatible subregistry with FastDrop liveness metadata. →GET /llms.txt Concise agent-readable map of the product, rules, and endpoints. →

MCP curl quickstart

These calls need no key. Initialize the Streamable HTTP connection, then ask for the public tool catalog.

1. Initialize

curl -sS https://fastdrop.dev/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  --data '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"curl","version":"1.0.0"}}}'

2. List tools

curl -sS https://fastdrop.dev/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -H 'MCP-Protocol-Version: 2025-06-18' \
  --data '{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}'

Authentication

Anonymous clients can initialize, list tools, and call the public discovery, product, review, and comment read tools.

Account tools accept Authorization: Bearer fd_.... Create and revoke those keys in developer settings.

OAuth clients request the mcp scope and may request offline_access for refresh tokens. Discover the flow from protected-resource metadata and authorization-server metadata.

Sandbox and no-auth read path

No separate credentials are needed for read-only testing. Omit the Authorization header, run initialize and tools/list, then call one of the public read tools. This reads live public production data and makes no account change; it is not an isolated write sandbox. Add authentication only when you intend to exercise account-scoped tools.

API error shapes

Agent-facing REST routing errors use a structured envelope. The hint and docs fields are optional; endpoint-specific responses are defined in OpenAPI. Subregistry validation follows the MCP Registry problem-detail shape.

HTTP API

{
  "error": {
    "code": "NOT_FOUND",
    "message": "No such endpoint: GET /api/example",
    "hint": "See the API surface at /openapi.json.",
    "docs": "https://fastdrop.dev/openapi.json"
  }
}

MCP JSON-RPC

{
  "jsonrpc": "2.0",
  "id": 2,
  "error": { "code": -32602, "message": "Invalid params" }
}

MCP tool-level failures may return HTTP 200 with result.isError = true. Account tools without usable authentication return HTTP 401 and a WWW-Authenticate header that points OAuth-aware clients to discovery metadata.

Keys and webhooks

Create or revoke API keys and configure webhook endpoints from the authenticated developer area. Secrets are shown according to the controls on that page.

Open developer settings