The MCP tool directory.

List repository security advisories for a GitHub repository.

List secret scanning alerts in a GitHub repository.

Lists available component snippet categories.

Lists available snippets within a specified category.

List all available context souls.

List all available template starter kits with their features, use cases, and complexity levels. Each template includes architectural decision guidance that teaches you how to choose the right libraries and patterns for your needs, rather than prescribing specific solutions. Includes: Documentation Site, SaaS Marketing, Portfolio & Blog, Agency/Studio, Content Platform, Event/Conference, App Marketing, Podcast/Media, CMS-Integrated, Pitch Deck, Admin Dashboard, and E-commerce templates.

Lists available SvelteKit documentation topics.

Lists all tables in one or more schemas.

List all unique tags used in a soul, with counts.

List tags in a project. Tags are cross-cutting labels that can be assigned to any prompt. Use this tool to resolve tag names to IDs before filtering (tag_id filter/dimension, list_prompts), and to label tag IDs from report output with their human-readable names before presenting results. Returns columnar JSON: {columns, rows, rowCount}. Columns: id, name.

List all available tags/categories for filtering markets and events. Use tag IDs with search_markets or search_events.

Lists available Tailwind CSS documentation topics.

Browse the complete catalog of 32 technologies across 8 categories (frontend, backend, meta-framework, database, orm, auth, hosting, payments). Each technology has deterministic scores across 6 dimensions. Use this to discover valid technology IDs before using analyze_tech or compare_techs. Data version: 2.4.0

List topics in a project. Topics are folder-like groupings — each prompt belongs to exactly one topic. Use this tool to resolve topic names to IDs before filtering (topic_id filter/dimension, list_prompts), and to label topic IDs from report output with their human-readable names before presenting results. Returns columnar JSON: {columns, rows, rowCount}. Columns: id, name.

Get a list of trending WebSim projects. Perfect for 'Show me trending projects' or 'What are the popular projects?' questions. Supports pagination and filtering by time range.

Returns a paginated array of child block objects for the specified block.

Retrieve a paginated list of all available custom expense categories for the organization. Supports cursor-based pagination with limit, order, start_after, and end_before query parameters. - These categories are custom and different from the values for "mercuryCategory".

Access an extensive list of tracked commodities across various sectors, including energy, metals, and agricultural products. The FMP Commodities List API provides essential data on tradable commodities, giving investors the ability to explore market options in real-time.

Retrieve a list of all credit accounts for the organization.

Retrieve a paginated list of customers. Supports cursor-based pagination with limit, order, start_after, and end_before query parameters.

Retrieve a paginated list of invoices. Supports cursor-based pagination with limit, order, start_after, and end_before query parameters.

Retrieve a paginated list of all recipient tax form attachments across all recipients in the organization. Use cursor parameters (start_after, end_before) for pagination.

Retrieve a paginated list of send money approval requests for the authenticated organization. Supports filtering by account and status.

Retrieve a paginated list of all transactions across all accounts. Supports advanced filtering by date ranges, status, categories, and cursor-based pagination. CRITICAL TRUNCATION RULE - READ THIS FIRST: ================================================================================ IF YOU SEE "Result too long" IN THE RESPONSE: 1. IMMEDIATELY STOP - Do not analyze or use the truncated data 2. The data is INCOMPLETE and any analysis will be WRONG 3. Start over with a smaller limit (reduce by 50%) 4. Paginate through ALL pages until you have complete data 5. NEVER provide answers based on truncated results ================================================================================ MANDATORY PAGINATION FOR COMPLETE RESULTS: When a user asks ANY question requiring complete data (totals, balances, aggregates, "most/least", "all transactions", comparisons, or any calculation across transactions): CRITICAL: Incomplete pagination will produce WRONG ANSWERS for questions about totals, spending categories, balances, minimums, maximums, or "most/least". You must fetch everything before calculating or answering. 1. Start with a limit of 300 transactions. 2. You MUST automatically paginate through ALL pages WITHOUT asking the user 3. Continue calling listTransactions using the page.nextPage value from each response 4. Keep fetching until page.nextPage is not present 5. If pagination would take more than 3 tool calls, ask the user to narrow down to a smaller time period 6. It is a CRITICAL ERROR to answer before having fetched ALL pages FILTERING: - IMPORTANT: WHEN FILTERING BY DATE, ALWAYS CHECK THE CURRENT DATE FIRST and ensure you're using the current year for current year queries - Unless specified otherwise or queried for "all transactions", ONLY include transactions with "status: sent" - To get transactions for a specific account, use the accountId parameter to filter by accountId PAGINATION MECHANICS: - Use the limit parameter to control page size - If page.nextPage is returned, use it as the start_after parameter in your next call - Keep fetching until page.nextPage is null/undefined - The page.nextPage value is a transaction ID to start after (exclusive) COMPUTATIONAL REQUIREMENTS: - For any query requiring: - Sums, totals, averages, medians, modes, ranges, most/least, or other aggregations across accounts/transactions - Calculations involving currency amounts - Comparisons of financial metrics - You MUST: - Create an artifact that processes the data programmatically - Parse the JSON response and use JavaScript/Python to calculate - Display intermediate steps for verification - Never rely on mental arithmetic for financial calculations - Example: "What's my total balance?" - CORRECT: Create artifact that parses accounts, maps to balances, uses reduce() to sum - INCORRECT: Manually adding up balance values For queries about 'last two months' or 'this year', calculate dates based on the actual current date Use the getCurrentDate tool to get the current date. Use the getTransaction tool to get more details about a specific transaction.

Search law-ordinance links by ministry (연계 법령 소관부처별 목록 조회). This tool searches local ordinances linked to laws managed by a specific government ministry or department. Args: org: Ministry/department code (required, e.g., "1400000") display: Number of results per page (max 100, default 20). **Recommend 50-100 for law searches (법령 검색) to ensure exact matches are found.** page: Page number (1-based, default 1) oc: Optional OC override (defaults to env var) type: Response format - "JSON" (default), "XML", or "HTML" sort: Sort order ctx: MCP context (injected automatically) Returns: Search results with ministry's linked ordinances or error Examples: Search ordinances linked to ministry 1400000: >>> lnkDep_search(org="1400000", type="XML")

Search laws linked to local ordinances (법령-자치법규 연계 목록 조회). This tool searches Korean laws that have linkages to local ordinances. Useful for understanding how national laws relate to local regulations. Args: query: Search keyword (default "*") display: Number of results per page (max 100, default 20). **Recommend 50-100 for law searches (법령 검색) to ensure exact matches are found.** page: Page number (1-based, default 1) oc: Optional OC override (defaults to env var) type: Response format - "JSON" (default), "XML", or "HTML" sort: Sort order - "lasc"|"ldes"|"dasc"|"ddes"|"nasc"|"ndes" ctx: MCP context (injected automatically) Returns: Search results with linked laws list or error Examples: Search for "자동차관리법": >>> lnkLs_search(query="자동차관리법", type="XML")

Search ordinance articles linked to law articles (연계 법령별 조례 조문 목록 조회). This tool searches local ordinance articles that are linked to specific national law articles. Shows which local ordinances implement or relate to specific law provisions. Args: query: Search keyword (default "*") display: Number of results per page (max 100, default 20). **Recommend 50-100 for law searches (법령 검색) to ensure exact matches are found.** page: Page number (1-based, default 1) oc: Optional OC override (defaults to env var) type: Response format - "JSON" (default), "XML", or "HTML" knd: Law type code (to filter by specific law) jo: Article number (4 digits, zero-padded). Examples: "0002" (Article 2), "0020" (Article 20), "0100" (Article 100) jobr: Branch article suffix (2 digits, zero-padded). Examples: "00" (main article), "02" (Article X-2) sort: Sort order ctx: MCP context (injected automatically) Returns: Search results with linked ordinance articles or error Examples: Search ordinances linked to 건축법 시행령: >>> lnkLsOrdJo_search(knd="002118", type="XML") Search specific article (제20조): >>> lnkLsOrdJo_search(knd="002118", jo=20, type="XML")

Authenticate MCP session to a Signal Found client account. Run this at the start of each session before business tools. Most tools require authenticated context and will use this session client id unless you pass an explicit `client_id` argument.

Clear the active authenticated client context for this MCP server session.

Get data about players based on first, last, or full name.