# Toolfound MCP server FAQ: keys, limits, payments and launching by agent

Answers about the Toolfound MCP server: whether read tools need a key, how writes authenticate, whether an agent can launch a product or pay, and what the limits are.

For agents: the documentation index is at [/llms.txt](https://toolfound.com/llms.txt) and this page is available as markdown at [/mcp/faq.md](https://toolfound.com/mcp/faq.md). HTML version: https://toolfound.com/mcp/faq

## Is there a directory where AI agents can discover and submit tools?

Yes. Toolfound's MCP server at https://toolfound.com/api/mcp lets an agent search the listing index and run the full launch: submit, verify ownership, track the queue and launch date, claim a listing and fetch badge snippets. The same index is published as llms.txt for assistants that do not speak MCP.

## Do read tools need a key?

No. Search, listings, alternatives, trending and the calendar are anonymous and rate-limited. Cache them freely.

## How does the write tier authenticate?

By the same email-verification loop a human goes through. The agent submits, a one-time token goes to the address given, and nothing is published until the domain check passes. OAuth 2.1 as a resource server is next on the list.

## Can my agent launch my product for me?

Yes. toolfound_submit_product returns the queue position, launch date and verification instructions in one payload; toolfound_verify_submission runs the ownership check; toolfound_get_launch_status reports status, queue position, launch date and listing URL. Free launch dates are scheduled at least 7 days ahead, with 5 free launches a day.

## Can an agent pay?

No, by design. Tool calls do not accept card details or complete purchases; checkout remains a human step. If you want an earlier date (Priority, $29 once), the checkout is a URL for a person to open.

## What are the limits?

Three submissions per email a day, ten per network address a day, sliding window. Duplicate URLs return the existing submission instead of a new one. Every write is written to an audit log against the session.

## Other MCP documentation

- [Overview](https://toolfound.com/mcp.md)
- [Setup](https://toolfound.com/mcp/setup.md)
- [Directory tools](https://toolfound.com/mcp/tools/directory.md)
- [Launch preparation tools](https://toolfound.com/mcp/tools/launch-prep.md)
- [Write tools](https://toolfound.com/mcp/tools/write.md)
- [Security](https://toolfound.com/mcp/security.md)