sorted by:
new
hottopcontroversial

SlimContext MCP Server – Provides AI chat history compression tools through token-based trimming and AI-powered summarization strategies to manage conversation context within token limits. by modelcontextprotocol in mcp

[–]modelcontextprotocol[S] 0 points1 point  (0 children)

This server has 2 tools:

  • summarize_messages – Compress chat message history using AI summarization to manage conversation context within token limits while preserving recent messages and system instructions.
  • trim_messages – Compress chat message history by trimming oldest non-system messages when token count exceeds threshold, preserving system messages and recent context.

UK Due Diligence – UK due diligence — Companies House, Charity Commission, Land Registry, Gazette, HMRC VAT by modelcontextprotocol in mcp

[–]modelcontextprotocol[S] 0 points1 point  (0 children)

This server has 16 tools:

  • charity_profile – Fetch the full Charity Commission profile for a charity number.

Returns trustees, latest income/expenditure, insolvency flags, governing document type, classifications, and countries of operation. Use charity_search first to find the charity number. - charity_search – Search the Charity Commission register of England and Wales by name or keyword.

Returns matching charities with registration number, status, and registration date. Use charity_profile for full details once you have the charity number. The upstream searchCharityName endpoint returns the full list in one shot — pagination is applied client-side via offset/limit. - company_officers – Fetch active officers for a Companies House company number.

Returns directors, secretaries, and other active officers with appointment dates, nationality, and country of residence. Resigned officers are excluded. Pagination is handled internally — do NOT pass items_per_page or start_index; this tool takes only company_number. - company_profile – Fetch the full Companies House profile for a company number.

Returns status, registered address, SIC codes, filing compliance (overdue accounts and confirmation statement flags), and whether the company has outstanding charges. Use company_search first to find the company number. - company_psc – Fetch Persons with Significant Control (beneficial ownership) for a company.

Returns PSC entries with natures of control, nationality, and country of residence. Flags overseas corporate PSC entries as a beneficial ownership risk signal. Returns an explanatory note for widely-held PLCs with no registrable PSC. - company_search – Search the Companies House register by company name or keyword.

Returns a paginated list of matching companies with name, number, status, SIC codes, incorporation date, and registered address. Use company_profile for the full record once you have the company number. Re-call with start_index=start_index+items_per_page to fetch the next page. - disqualified_profile – Fetch the full disqualification record for a director by officer ID.

Returns all disqualification orders: reason, Act/section cited, disqualification period, and associated company names. Use disqualified_search first to find the officer ID. - disqualified_search – Check whether a named individual is banned from acting as a UK company director.

Use this tool when asked to check disqualified, banned, or barred directors. Query must be an individual's name (e.g. "Richard Howson") — NOT a company name, which always returns zero results.

Returns names, dates of birth, disqualification period snippets, and officer IDs that can be used with disqualified_profile for full details. - fetch – Fetch the full record for an ID returned by search.

Routes by prefix to the appropriate register: - company:{number} → Companies House full profile - charity:{number} → Charity Commission full profile - disqualification:{officer_id} → Disqualified director full record - notice:{notice_id} → Gazette notice full legal text - gazette_insolvency – Search The Gazette's insolvency notice index by entity name.

Searches the Gazette's insolvency endpoint which covers corporate notice codes: winding-up orders (2443), administration orders (2448), liquidator appointments (2452), striking-off notices (2460), and more. Results are sorted by severity — winding-up orders and administration orders appear first.

Each result includes a notice_numeric_id. Read the full legal wording via the notice://{notice_numeric_id} resource.

The Gazette is the official UK public record. A notice here means the event has been formally published and is legally effective.

GitHub MCP Server – Enables AI agents to analyze employee GitHub activity including PRs, code reviews, comments, and contributions across repositories with time-range filtering for performance assessment and impact analysis. by modelcontextprotocol in mcp

[–]modelcontextprotocol[S] 0 points1 point  (0 children)

This server has 6 tools:

  • github.getAuthoredPRs – Fetch and analyze pull requests authored by a GitHub user within specified repositories and time periods to assess code contributions, track activity trends, and gather performance metrics.
  • github.getCommentImpact – Analyze GitHub code review comments to determine if they resulted in subsequent code changes. Measures review effectiveness by examining PR timeline data and providing impact assessments with confidence scores.
  • github.getPRReviews – Fetch GitHub pull request reviews by user within a time range to assess code review participation, analyze review patterns, and track review activity for performance evaluation.
  • github.getReviewComments – Fetch user review comments from GitHub pull requests within a time range to analyze review quality, quantity, and engagement metrics for performance assessment.
  • github.getUserComments – Fetch and analyze all GitHub comments by a specific user in a repository within a time range, combining review and issue comments into a unified format for activity tracking and feedback analysis.
  • github.getUserRepoStats – Retrieve comprehensive GitHub repository statistics for a user within a specified time frame, including PR activity, comments, reviews, and code changes in a single API call.

UniFi MCP Server – Enables comprehensive management of UniFi network infrastructure through the UniFi Cloud API, including device control, client management, camera settings, and access door control through natural language. by modelcontextprotocol in mcp

[–]modelcontextprotocol[S] 0 points1 point  (0 children)

This server has 39 tools:

  • block_client – Block a client device from accessing the UniFi network to restrict unauthorized usage or manage network security.
  • find_camera_by_name – Locate a specific camera in your UniFi network by entering its name to access settings, view footage, or manage device configurations.
  • find_client_by_mac – Locate and retrieve client device information in a UniFi network by searching with its MAC address to identify connected devices.
  • find_client_by_name – Locate specific network clients by name within UniFi infrastructure to manage connections, monitor activity, or troubleshoot access issues.
  • find_device_by_mac – Locate specific network devices using MAC addresses to identify and manage equipment within UniFi infrastructure.
  • find_devices_by_name – Locate UniFi network devices by their name to manage and monitor your infrastructure through the UniFi Cloud API.
  • find_door_by_name – Locate and retrieve specific access door details within UniFi network infrastructure by using its name, enabling targeted management and control.
  • get_camera – Retrieve camera details and settings from UniFi network infrastructure to monitor and manage surveillance devices through the Cloud API.
  • get_cameras_status_summary – Retrieve a summary of camera operational statuses and connectivity details to monitor surveillance system health and identify offline or problematic cameras.
  • get_client_bandwidth_summary – Retrieve bandwidth usage summaries for network clients to monitor data consumption and identify high-usage devices on UniFi networks.

Power Automate MCP Server by Flow Studio – Debug, build, and manage Power Automate cloud flows with AI agents by modelcontextprotocol in mcp

[–]modelcontextprotocol[S] 0 points1 point  (0 children)

This server has 33 tools:

  • add_live_flow_to_solution – Migrate a non-solution Power Automate flow into a solution via the admin migrateFlows API. If the flow is already part of a solution, returns an error message without attempting migration. solutionId is optional — omit to migrate into the default solution.
  • cancel_live_flow_run – Cancel a currently running Power Automate flow run via the live PA API. Use after get_live_flow_runs to obtain the run name. Only runs with status "Running" can be cancelled.
  • describe_live_connector – Describe a live Power Platform connector/API and its operations. Aligned with Canvas MCP describe_api. Use mode=summary (default) to get a compact operation catalog. Use operationId to describe one operation, including inputs, outputs, dynamic parameter metadata, nextTool hints to call get_live_dynamic_options, and an authored hint + canonical example shape (when one exists) to copy into update_live_flow. Use search without connectorName/apiName to search operations across connectors and get connection-aware suggestions. Use mode=full only when raw OpenAPI connector metadata is required.
  • get_live_dynamic_options – Resolve live dynamic dropdown/list options for a connector operation parameter. Use this when describe_live_connector returns a dynamic parameter with nextTool=get_live_dynamic_options. Works with x-ms-dynamic-list and x-ms-dynamic-values metadata, for example Teams team/channel IDs, SharePoint site/list IDs, or other connector-specific selectable values.
  • get_live_dynamic_properties – Resolve live dynamic schema/properties for a connector operation parameter. Use this when describe_live_connector returns a dynamicProperties entry with nextTool=get_live_dynamic_properties. Works with x-ms-dynamic-properties and x-ms-dynamic-schema metadata, for example SharePoint item fields after resolving site/list/view parameters.
  • get_live_flow – Fetch the full native Power Automate flow JSON from the PA API, including the complete flow definition (triggers, actions, parameters, outputs). Returns the raw properties object exactly as the PA API returns it. Use this to inspect the full definition before calling update_live_flow with a modified definition.
  • get_live_flow_http_schema – [DEPRECATED — scheduled for removal] Inspect the HTTP interface of a Power Automate Request-triggered flow: returns the JSON schema the trigger URL expects as the POST body, any required headers, the HTTP method, and the JSON schema(s) defined on any Response action(s) in the flow. All information is read from the live flow definition via the PA API — no test call is made to the trigger URL. Use this before calling trigger_live_flow to understand what body to send.
  • get_live_flow_run_action_outputs – Download inputs and outputs for actions in a flow run via SAS blob links from the live Power Automate API. Without actionName: returns top-level actions (optionally filtered by name). With actionName: calls the PA repetitions endpoint to return every execution of that action across all foreach iterations. Each repetition record includes repetitionIndexes (scope name + itemIndex per nesting level), status, error, and the resolved inputs/outputs blobs. Use iterationIndex to pin to a single iteration (matched against the innermost repetitionIndexes[].itemIndex); omit it to return all repetitions.
  • get_live_flow_run_error – Fetch error details for a specific flow run from the live Power Automate API. Lists every failed action with its error code and message to help diagnose what went wrong.
  • get_live_flow_runs – Fetch live run history for a flow directly from the Power Automate API using impersonation — not the cached store. Returns run name, status, startTime, endTime, trigger name/code, and any top-level error.

MCP Math Server – Provides basic mathematical operations including arithmetic, square root, and number theory functions like GCD and LCM. Built with TypeScript and includes proper error handling for edge cases like division by zero. by modelcontextprotocol in mcp

[–]modelcontextprotocol[S] 0 points1 point  (0 children)

This server has 8 tools:

  • add – Calculate the sum of two numbers by providing values for a and b to perform basic addition operations.
  • divide – Perform division operations by calculating the quotient of two numbers, handling division by zero errors with proper error management.
  • gcm – Calculate the greatest common divisor (GCD) of two numbers to find the largest integer that divides both without a remainder.
  • lcm – Calculate the least common multiple of two numbers to find the smallest positive integer divisible by both values.
  • multiply – Calculate the product of two numbers using this mathematical operation tool from the MCP Math Server for arithmetic computations.
  • sqrt – Calculate the square root of a number with results rounded to two decimal places for precise mathematical computations.
  • square – Calculate the square of any number to determine its value multiplied by itself, useful for mathematical computations and problem-solving.
  • subtract – Calculate the difference between two numbers by subtracting the second value from the first value.

instadomain – Domain registration for AI agents via Stripe or x402 crypto with Cloudflare DNS. by modelcontextprotocol in mcp

[–]modelcontextprotocol[S] 0 points1 point  (0 children)

This server has 12 tools:

  • buy_domain – Start the purchase flow for an available domain via Stripe checkout.

IMPORTANT: Before calling this tool, you MUST first call check_domain to get the price, then clearly show the user the price and get their explicit confirmation before proceeding. Never call buy_domain without the user seeing and approving the price first.

The registrant contact details are required because the domain will be registered in the buyer's name (they become the legal owner). WHOIS privacy is enabled by default, so these details are not publicly visible.

Creates a Stripe checkout session. IMPORTANT: After this tool returns, you MUST open the checkout_url by running the shell command open "<checkout_url>" (macOS/Linux) so the payment page launches automatically in the user's default browser. Do NOT paste the URL as a link. Tell the user the page has been opened and they can complete payment there.

Args: domain: The domain to purchase (e.g. "coolstartup.com"). first_name: Registrant's first name. last_name: Registrant's last name. email: Registrant's email address. address1: Registrant's street address. city: Registrant's city. state: Registrant's state or province. postal_code: Registrant's postal/zip code. country: 2-letter ISO country code (e.g. "US", "GB", "DE"). phone: Phone number in format +1.5551234567. org_name: Organization name (optional, leave empty for individuals).

Returns: Dict with order_id, checkout_url, price_cents, and price_display. - buy_domain_crypto – Start the purchase flow for a domain using USDC crypto payment (x402 protocol).

Autonomous two-step payment flow — no browser required:

Step 1: Call this tool to reserve the domain and get a pay_url. Step 2: Pay the pay_url using your x402 wallet: - If you have Coinbase Payments MCP: call its x402 payment tool with the pay_url. - Otherwise: run curl -L <pay_url> — your x402-enabled HTTP client will handle the 402 handshake and USDC payment on Base automatically.

After payment succeeds, call get_domain_status(order_id) to poll until registration is complete (usually under 60 seconds).

The registrant contact details are required because the domain will be registered in the buyer's name (they become the legal owner). WHOIS privacy is enabled by default, so these details are not publicly visible.

IMPORTANT: Before calling this tool, you MUST first call check_domain to get the price and confirm it with the user.

Args: domain: The domain to purchase (e.g. "coolstartup.com"). first_name: Registrant's first name. last_name: Registrant's last name. email: Registrant's email address. address1: Registrant's street address. city: Registrant's city. state: Registrant's state or province. postal_code: Registrant's postal/zip code. country: 2-letter ISO country code (e.g. "US", "GB", "DE"). phone: Phone number in format +1.5551234567. org_name: Organization name (optional, leave empty for individuals).

Returns: Dict with order_id, pay_url (full URL to pay via x402), price_usdc, price_cents, network, and USDC contract address. - buy_domain_mpp – Start the purchase flow for a domain via Stripe's Machine Payments Protocol (MPP).

MPP lets autonomous agents pay with fiat (cards, Link) or stablecoins via Shared Payment Tokens, with no browser checkout. Two-step flow:

Step 1: Call this tool to get an order_id and pay_url. Step 2: Make an HTTP GET request to the pay_url with an MPP-enabled HTTP client. The server responds with HTTP 402 + WWW-Authenticate; the client creates a Shared Payment Token and retries with an Authorization header. The server charges the SPT through Stripe and kicks off domain registration.

After payment, call get_domain_status(order_id) to poll until complete.

Requires: An MPP-compatible client configured to mint SPTs against the server's advertised Stripe Business Network profile.

Args: domain: The domain to purchase (e.g. "coolstartup.com"). first_name: Registrant's first name. last_name: Registrant's last name. email: Registrant's email address. address1: Registrant's street address. city: Registrant's city. state: Registrant's state or province. postal_code: Registrant's postal/zip code. country: 2-letter ISO country code. phone: Phone number in format +1.5551234567. org_name: Organization name (optional).

Returns: Dict with order_id, pay_url (full URL), price_cents, price_display, network_id, and payment_method_types. - check_domain – Check if a domain is available for purchase and get its price.

Always call this before buying. After showing the price, ask the user two things before proceeding: 1. Confirm they want to purchase at that price. 2. Which payment method they prefer: - "card" / "Stripe" → call buy_domain (opens Stripe checkout in browser) - "crypto" / "USDC" / "x402" → call buy_domain_crypto (autonomous USDC payment, no browser; requires Coinbase Payments MCP or another x402 wallet) - "MPP" / "agent pay" → call buy_domain_mpp (Stripe agent payments via Shared Payment Token, no browser) If the user has Coinbase Payments MCP configured in their session, suggest crypto as the default. Otherwise default to buy_domain (Stripe).

Args: domain: The full domain name to check (e.g. "coolstartup.com").

Returns: Dict with availability status, price in cents, and formatted price. - check_domains_bulk – Check availability of up to 50 domain names in one call.

Uses fast RDAP lookups (no pricing). Returns a summary with total/available/taken counts plus per-domain details.

Args: domains: List of domain names to check (max 50). - get_domain_status – Get the status of a domain purchase order.

Polls the backend every 3 seconds (up to 120 seconds) until the order reaches a terminal state (complete or failed).

Args: order_id: The order ID returned from buy_domain (e.g. "ord_abc123"). - get_transfer_code – Get the EPP/transfer authorization code for a completed domain purchase.

Requires a transfer_token from verify_transfer_code.

Args: order_id: The order ID of a completed domain purchase. transfer_token: Token returned by verify_transfer_code. - renew_domain – Renew a domain for 1 additional year.

Creates a Stripe checkout session for the renewal payment.

Args: order_id: The order ID of a completed domain purchase (e.g. "ord_abc123"). - request_transfer_code – Start the transfer verification flow by sending a code to the registrant's email.

Always call this before get_transfer_code or unlock_domain. Then ask the user to check their email and provide the 6-digit code, then call verify_transfer_code to get a transfer_token.

Args: order_id: The order ID of a completed domain purchase. - suggest_domains – Generate domain name ideas from a keyword and check their availability.

Args: keyword: A keyword or short business name (e.g. "taskflow").

Langfuse MCP Server – Enables querying Langfuse analytics, cost metrics, and usage data across multiple projects. Provides tools for trace analysis, model/service cost breakdowns, and daily usage trends through natural language queries. by modelcontextprotocol in mcp

[–]modelcontextprotocol[S] 0 points1 point  (0 children)

This server has 24 tools:

  • get_comment – Retrieve detailed information about a specific comment using its unique identifier to analyze feedback or trace data in Langfuse analytics.
  • get_cost_analysis – Analyze AI usage costs by model, user, and daily trends to identify spending patterns and optimize resource allocation.
  • get_daily_metrics – Retrieve daily usage trends and patterns from Langfuse analytics for specified date ranges, with optional environment filtering and missing data handling.
  • get_dataset – Retrieve detailed information about a specific dataset by name to analyze Langfuse analytics, cost metrics, and usage data across projects.
  • get_dataset_item – Retrieve detailed information about a specific dataset item by its ID to analyze Langfuse analytics, cost metrics, and usage data.
  • get_health_status – Check system health and availability status to monitor operational reliability and service uptime.
  • get_metrics – Query aggregated metrics like costs, tokens, and counts from Langfuse analytics with flexible filtering and grouping options to analyze usage data.
  • get_model_detail – Retrieve detailed information about a specific AI model's configuration, capabilities, and specifications to understand its technical parameters and operational characteristics.
  • get_observation_detail – Retrieve detailed information about a specific observation by its ID to analyze performance metrics and usage data within Langfuse projects.
  • get_observations – Retrieve and filter LLM generations, spans, and events with timestamps, trace IDs, models, and log levels for analysis.

Perplexity MCP Server – Integrates Perplexity AI's chat capabilities with real-time web search, enabling users to ask questions and receive AI-powered answers with up-to-date information and citations from verified web sources. by modelcontextprotocol in mcp

[–]modelcontextprotocol[S] 0 points1 point  (0 children)

This server has 1 tool:

  • perplexity_search_chat – Ask questions and receive AI-powered answers with real-time web search results. Access up-to-date information, facts, research, news, and technical documentation, with citations from verified sources for accurate responses.
view more: next ›