The MCP tool directory.
Each row is one tool from one provider. Tools sharing a name across providers (e.g. search) are listed separately because they aren't interchangeable.
[ 3116 tools indexed ]
[ all tools ]
30 / 3116
faf_validate
[ remote ]Validate .faf YAML content via the Mk4 Zig-WASM engine. Returns true if mission-ready (>= 100).
feature_flags.disable.update
[ remote ]Disables a feature flag in the current environment.
feature_flags.enable.update
[ remote ]Enables a feature flag in the current environment.
feature_flags.get
[ remote ]Get the details of an existing feature flag by its slug.
feature_flags.list
[ remote ]Get a list of all of your existing feature flags matching the criteria specified.
feature_flags.targets.create
[ remote ]Enables a feature flag for a specific target in the current environment. Currently, supported targets include users and organizations.
feature_flags.targets.delete
[ remote ]Removes a target from the feature flag's target list in the current environment. Currently, supported targets include users and organizations.
felo-search
[ remote ]Advanced AI-powered web search for technical intelligence. Retrieves up-to-date information including software releases, security advisories, migration guides, benchmarks, developer documentation, and community insights. Supports both standard and streaming responses.
fetch
[ remote ]Retrieves details about a Notion entity by its URL or ID. You can fetch the following types of entities: - Page, i.e. from a <page> block or a <mention-page> mention - Database, i.e. from a <database> block or a <mention-database> mention Use the "fetch" tool when you need to see the details of a Notion entity you already know exists and have its URL or ID. Provide the Notion entity's URL or ID in the `id` parameter. You must make multiple calls to the "fetch" tool if you want to fetch multiple entities. Content for pages that are returned use the enhanced Markdown format, which is a superset of the standard Markdown syntax. See the full spec in the description of the "create-pages" tool. Databases can have multiple data sources, which are collections of pages with the same schema. When fetching a database, the tool will return information about all its data sources. Examples of fetching entities: 1. Fetch a page by URL: { "id": "https://www.notion.so/workspace/Product-Requirements-1234567890abcdef" } 2. Fetch a page by ID (UUIDv4 with dashes): { "id": "12345678-90ab-cdef-1234-567890abcdef" } 3. Fetch a page by ID (UUIDv4 without dashes): { "id": "1234567890abcdef1234567890abcdef" } 4. Fetch a database: { "id": "https://www.notion.so/workspace/Projects-Database-abcdef1234567890" } Common use cases: - "What are the product requirements still need to be implemented from this ticket https://notion.so/page-url?" - "Show me the details of the project database at this URL" - "Get the content of page 12345678-90ab-cdef-1234-567890abcdef"
fetch
[ remote ]Fetch full document content for a search result.
fetch_page_content
[ remote ]Fetch and extract content from a web page. Returns the page content in markdown format.
fetchLinuxDoArticle
[ remote ]Fetch full article content from a linux.do post URL
files.list.list
[ remote ]Retrieves a list of files associated with the authenticated project. Results can be filtered by toolkit and tool slugs.
files.upload.request.create
[ remote ]Generates a presigned URL for uploading a file to S3. This endpoint handles deduplication by checking if a file with the same MD5 hash already exists.
find-columns
[ remote ]Find geological stratigraphic columns, rock layers, and geological history for any location worldwide. Use for geology, bedrock, formations, age dating, and stratigraphic analysis.
find-hooks
[ remote ]Find social media hooks by network and/or category
find-units
[ remote ]Find geological rock units, formations, bedrock geology, and mineral information for any location worldwide. Use for geology questions, rock types, age dating, lithology, and geological analysis.
find_agent_ready_products
[ remote ]Find products with the highest agent readiness scores — products that are easiest for AI agents to integrate with. Sorted by compositeScore desc; supports skip/limit pagination. All readiness scores are 0-100, higher better. Calibration: <30 = not agent-ready (default minimumScore filter), 30-49 = early/limited, 50-69 = decent, 70-89 = strong, 90+ = exceptional. Response: array of { slug, name, tagline, websiteUrl, tier (free|verified|featured), unverified (true on free only), verifiedAt (ISO; nullable), agentReadiness: { compositeScore, apiScore, protocolScore, sdkScore, integrationScore, dxScore } (each 0-100), mcp?: { hasMcpSupport, totalToolCount, serverCount } }. Note: ordering is by agent-readiness, not by tier — this is the one MCP tool where tier doesn't reorder results, since the buyer intent is technical fit, not paid placement.
find_awesome_section
[ remote ]Discovers sections/categories across awesome lists matching a search query and returns matching sections from awesome lists. You MUST call this function before 'get_awesome_items' to discover available sections UNLESS the user explicitly provides a githubRepo or listId. Selection Process: 1. Analyze the query to understand what type of resources the user is looking for 2. Return the most relevant matches based on: - Name similarity to the query and the awesome lists section - Category/section relevance of the awesome lists - Number of items in the section - Confidence score Response Format: - Returns matching sections of the awesome lists with metadata - Includes repository information, item counts, and confidence score - Use the githubRepo or listId with relevant sections from results for get_awesome_items For ambiguous queries, multiple relevant sections will be returned for the user to choose from.
find_breakpoints
[ remote ]Detect responsive layout breakpoints for a URL. Scans viewport widths from 320px to 1920px and identifies where significant layout changes occur (large height jumps, content reflows). Returns a list of detected breakpoint widths.
find_buses_to_destination
[ remote ]Find bus routes that go to a specified destination. Args: destination: The destination to search for (e.g., "Central", "Mong Kok", "Airport")
find_duplicates
[ remote ]Find potential duplicate contacts.
find_login_page
[ remote ]Discover login/sign-in pages for a website. Checks the site's sitemap.xml and probes common login URL paths. Returns a list of candidate login URLs found. Use this before attempting to log in to a site.
find_n_plus_one
[ remote ]Detect N+1 query patterns from recent query history. Fingerprints queries and flags repeated patterns. [ARCHITECT tier]
find_nearby
[ remote ]Find public facilities near GPS coordinates in Seoul, sorted by distance. Args: lat: Latitude of the search center point (Seoul range: ~37.4 to ~37.7). lng: Longitude of the search center point (Seoul range: ~126.7 to ~127.2). radius_m: Search radius in meters (100-5000, default 500). type: Optional filter by facility type — "toilet", "pharmacy", "wifi", "aed", or "tourist_info". limit: Maximum number of results to return (1-20, default 5). Returns: A list of nearby places sorted by distance, with distance_m field indicating meters from the search point.
find_places
[ remote ]Search for public facilities in Seoul (restrooms, pharmacies, WiFi hotspots, AED locations, tourist info centers). Args: type: Type of facility — "toilet", "pharmacy", "wifi", "aed", or "tourist_info". district: Seoul district name in English or Korean (e.g., "gangnam", "jongno", "강남구", "종로구"). filters: Service-specific filters as key-value pairs. Examples: {"english": true} for pharmacies with English support, {"is_24h": true} for 24-hour restrooms, {"indoor": true} for indoor WiFi. limit: Maximum number of results to return (1-50, default 10). Returns: A list of matching places with location, services, and hours information.
find_products_with_capability
[ remote ]Find B2B SaaS products that support a specific capability — an integration with a named service ('salesforce-integration'), a data format ('xrechnung-support'), an industry standard ('eclass-support'), or a compliance certification ('soc2'). Accepts either a canonical capability slug or natural language; resolves to a structured capability when possible. Returns products ranked by tier (Featured > Verified > Free). Response: { capability, matchType (none|exactSlug|canonicalSlug|nlpFallback — exactSlug & canonicalSlug are deterministic; nlpFallback is heuristic), resolvedFeatures[], products[] }. Each product: { slug, name, tagline, websiteUrl, tier, unverified (true on free only), verifiedAt, evidence[] (per-claim: featureSlug, evidenceUrl, notes, source, confidence) }. Empty: { capability, matchType, message, suggestedSlugs[] } when no capability matched, or products: [] when capability matched but no products claim it yet.
find_stop_by_name
[ remote ]Find bus stops matching a name or partial name. Args: stop_name: Full or partial name of the bus stop to search for
find_tool_for_task
[ remote ]Find the best MCP tools for a given task. Describe what you want to accomplish (e.g. 'manage github issues', 'send slack messages', 'query a database') and get ranked results with the products that provide each tool and their input schemas. By default only shows tools available via remote (network-hosted) servers. Audience: agent builders looking for installable MCP tools — for B2B SaaS recommendations, prefer search_products or find_products_with_capability. Response: { task, matchType (none|exactSlug|canonicalSlug|nlpFallback), resolvedCapabilities[], capabilityProducts[] (B2B SaaS products that claim the same capability — empty when matchType=none), results[] (MCP-tool-level matches) }. Each result: { normalizedName, displayName, description, inputSchema, relevance (integer; +1 per term hit, +3 for full-phrase hit), productCount, products[] (each: slug, name, serverQualifiedName, isRemoteCapable, tier, unverified, verifiedAt) }. Empty case: { task, matchType, message, suggestedQueries[], suggestedCapabilities[] }.
find_weather_stations
[ remote ]Find weather observation stations near a location in the United States. Useful for getting station-specific data, finding data sources, or understanding which stations provide weather data for an area. Includes ASOS, AWOS, and other automated weather stations.