Getting started

Start with free discovery

Paste this into your AI agent:

Read https://toolcargo.com/agents.txt, then find the MCP servers I need and help me connect them. Ask me what I want to do first.

If your client supports remote MCP servers, add this Streamable HTTP URL without authentication:

https://toolcargo.com/mcp

claude mcp add --transport http --scope user toolcargo https://toolcargo.com/mcp

No account or key is needed. Your agent can search ToolCargo's hosted catalogue and thousands of entries in our dated snapshot of the official MCP Registry. You can also browse the directory.

Discovery finds servers and their setup instructions. To run their tools, connect the chosen server separately. External servers have their own hosting, permissions and costs.

Tool arguments, pagination and JSON fallback: public MCP discovery and server search API reference.

Choosing a local package or a hosted URL? Compare local vs remote MCP servers before connecting.

Building your own integration? Compare MCP vs direct API access with a registry search example through both interfaces.

1. Create an account for hosted tools

Sign up with an email and password. New accounts automatically activate Site Audit Free: 50 tool calls a month shared across included hosted connectors. No card is needed. For an older account without a plan, choose “Activate Free plan” for Site Audit in your dashboard.

Choose a tool from the hosted connector catalogue. Its page lists the exact server URL, tools, permissions and setup requirements.

Public-source bundles such as Science & Academic Research (papers, chemicals, proteins, clinical trials, species, books), Economy & Public Data (indicators, exchange rates, holidays, weather, tides), Developer Toolkit (packages, vulnerabilities, AI models) and Marketing Toolkit need no external provider key. Connect them with your ToolCargo account and shared Free allowance. Tools for your business accounts may require a separate provider connection; provider fees and limits are listed on the connector page.

Use the MCP server evaluation checklist before connecting a candidate.

2. Connect your client

Every hosted connector has its own server URL. For Site Audit it is:

https://toolcargo.com/mcp/site-audit

There are two ways to authenticate, depending on the client:

• OAuth sign-in — for Claude (claude.ai and Desktop) and ChatGPT. Paste the URL; the client opens a ToolCargo page where you approve access. Nothing to copy.
• API key — for Claude Code, Cursor and VS Code. Create a key in the dashboard, select the connector you want to use, and send it as an Authorization: Bearer header. A key scoped only to Site Audit cannot call another connector.

With Claude Code, one command does it:

claude mcp add --transport http --scope user toolcargo-site-audit https://toolcargo.com/mcp/site-audit \
  --header "Authorization: Bearer YOUR_API_KEY"

Other clients and tested setup status: client setup. These examples use Site Audit; replace its URL with the chosen connector's URL when connecting another tool.

3. Ask for an audit

Open a conversation and ask in plain language, for example:

Audit https://example.com and tell me anything that would stop it from being indexed or shared properly.

Your assistant chooses the tools it needs (usually audit_page first) and reports back. Each call appears under Usage in your dashboard, with its result and duration.

What next

• Tool reference — exactly what each tool checks.
• Pre-launch SEO check — a workflow worth saving as a habit.
• Troubleshooting — if the tools don't show up.