What MCP servers can actually do

5,860 tool names, each one reported by a server that answered our handshake. Registries tell you a server exists. This tells you what it exposes.

Ordered by how many separate hosts expose a tool, not how many listings. One operator running a thousand servers that all share a toolkit would otherwise fill this entire page, and did before we changed it.

Back to the server directory

5,860 matching.

tool	hosts	listings
`probe_ucp_readiness`	2	2
`procure`	2	2
`product_details`	2	2
`product_discovery`	2	2
`product_intel`	2	2
`product_reviews`	2	2
`products`	2	2
`products.get`	2	2
`products.search`	2	2
`project`	2	2
`project-create`	2	2
`project-list`	2	2
`projects_search`	2	2
`property_lookup`	2	2
`proposal.get`	2	2
`propose`	2	2
`protect_payment`	2	2
`protect_pdf`	2	2
`prove_safe_action`	2	2
`provider_incidents`	2	2
`provider_profile`	2	2
`provider_reliability`	2	2
`provider_terms_changed`	2	2
`provider_transparency`	2	2
`public_holidays`	2	2
`publish_essay`	2	2
`publish_html`	2	2
`publish_markdown_to_harness`	2	2
`publish_page`	2	2
`publish_resource_package`	2	2
`publish_run`	2	2
`publish_website`	2	2
`publisher`	2	2
`pull_ai_crawler_watch`	2	2
`pull_harness`	2	2
`pull_instructions`	2	2
`purchase`	2	2
`purchase_options`	2	2
`purchase_skill`	2	2
`qr_generate`	2	2
`query_database`	2	2
`query_events`	2	2
`query_fda`	2	2
`query_features`	2	2
`query_issuer_registry`	2	2
`query_jurisdiction_overlay`	2	2
`query_knowledge`	2	2
`query_knowledge_graph`	2	2
`query_outcomes`	2	2
`query_range`	2	2