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
`get_proposal`	2	2
`get_protocol_info`	2	2
`get_protocol_stats`	2	2
`get_provider_info`	2	2
`get_provider_reviews`	2	2
`get_provider_status`	2	2
`get_public_forecast_vintage`	2	2
`get_public_share`	2	2
`get_qr_code`	2	2
`get_quote_completion_url`	2	2
`get_quote_requirements`	2	2
`get_race_results`	2	2
`get_rate_history`	2	2
`get_rba_table`	2	2
`get_reactions`	2	2
`get_real_estate`	2	2
`get_realtime`	2	2
`get_recalls`	2	2
`get_recent`	2	2
`get_recent_activity`	2	2
`get_recent_alerts`	2	2
`get_recent_filings`	2	2
`get_recent_news`	2	2
`get_recent_results`	2	2
`get_regime_context`	2	2
`get_region`	2	2
`get_register`	2	2
`get_registration`	2	2
`get_registry`	2	2
`get_related_articles`	2	2
`get_renewals`	2	2
`get_rental_details`	2	2
`get_report_by_slug`	2	2
`get_report_markdown`	2	2
`get_representatives`	2	2
`get_request_status`	2	2
`get_requests`	2	2
`get_research_claim`	2	2
`get_research_observation`	2	2
`get_research_papers`	2	2
`get-resources`	2	2
`get_responses`	2	2
`get_result_detail`	2	2
`get_retailers`	2	2
`get_revenue_attribution`	2	2
`get_revenue_segments`	2	2
`get_review`	2	2
`get_review_summary`	2	2
`get_rivals`	2	2
`get_robot`	2	2