dev.metamesh-uga/metamesh-uga

Est-ce que dev.metamesh-uga/metamesh-uga est sûr ?

Au dernier audit MCP Hub, le serveur MCP « dev.metamesh-uga/metamesh-uga » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 15 outils

• metamesh.context≈ 61 tokens

  Compact snapshot of the MetaMesh gateway: active tool count, top categories, payment/billing status, last discovery. Best first call for context.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "metamesh.context", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• metamesh.discovery_status≈ 53 tokens

  Control/observability: status of the registry discovery engine (active tools, last run, pages fetched).

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "metamesh.discovery_status", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• metamesh.health≈ 44 tokens

  Gateway health: database connectivity, payment configuration and feature flags.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "metamesh.health", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• metamesh.metrics≈ 46 tokens

  Usage analytics: total tools, calls, success rate and recent error counts. Read-only.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "metamesh.metrics", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• metamesh.search_tools≈ 110 tokens

  Search the catalog of 13k+ MCP tools by keyword. Returns concise matches (name, category, description). Use this instead of listing all tools.

  Paramètres, retour & exemple (2)

  Paramètres

  • q · string · requis
    Search query, e.g. "github", "database", "email"
  • limit · number · optionnel
    Max results (default 10, max 50)

  Exemple d'appel

  {"name": "metamesh.search_tools", "arguments": {"q": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• metamesh.tool_info≈ 72 tokens

  Detailed info for a specific catalog tool: description, category, trust/security score, state, source.

  Paramètres, retour & exemple (1)

  Paramètres

  • name · string · requis
    Exact tool name

  Exemple d'appel

  {"name": "metamesh.tool_info", "arguments": {"name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• stripe.get_stripe_account_info≈ 45 tokens

  This will get the account info for the logged in Stripe account.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "stripe.get_stripe_account_info", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• stripe.search_stripe_documentation≈ 264 tokens

  Search the Stripe documentation for the given question and language. It takes two arguments: - question (str): The user question to search an answer for in the Stripe documentati…

  Paramètres, retour & exemple (3)

  Paramètres

  • language · string · optionnel · dotnet | go | java | node | php | ruby | python | curl
    The programming language to search for in the documentation.
  • question · string · requis
    The user question about integrating with Stripe will be used to search the documentation.
  • search_only_api_ref · boolean · optionnel
    When set to true, search only in the Stripe API reference documentation instead of the full documentation set. Use true when users need specific API implementation details, code examples, or parameter references. Use false (default) for conceptual explanations, best practices, integration guides, or troubleshooting help.

  Exemple d'appel

  {"name": "stripe.search_stripe_documentation", "arguments": {"question": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• stripe.send_stripe_feedback≈ 332 tokens

  Share feedback about Stripe's products. Submit when the user gives product feedback or you observe something concrete that worked or failed. Do not report model behavior, the use…

  Paramètres, retour & exemple (5)

  Paramètres

  • actor · string · optionnel · human | agent
    Who decided to submit: human or agent. Defaults to agent.
  • context · string · requis
    What the user was trying to accomplish. Do not include sensitive business information.
  • message · string · requis
    What broke or worked, concrete and specific. At least 5 words.
  • sentiment · string · requis · positive | negative | neutral
    positive, negative, or neutral
  • feature_area · string · optionnel · payments | connect | subscriptions | billing | payouts | reporting | invoicing | invoices
    Product area this feedback is about.

  Exemple d'appel

  {"name": "stripe.send_stripe_feedback", "arguments": {"context": "texte", "message": "texte", "sentiment": "positive"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• stripe.stripe_analytics≈ 607 tokens

  This tool is for analyzing Stripe Sigma and Metrics data (e.g. about revenue, charges, products, invoices, subscriptions, disputes, transactions, tax tables, payments etc) and run…

  Paramètres, retour & exemple (2)

  Paramètres

  • intent · string · requis · execute_query_run | retrieve_query_run | search_query_tables | retrieve_query_table | execute_query_template | retrieve_query_template
    The intent of the tool call.
  • params · object · optionnel
    The parameters for the tool call. Required parameters depend on the intent.

  Exemple d'appel

  {"name": "stripe.stripe_analytics", "arguments": {"intent": "execute_query_run"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• stripe.stripe_api_details≈ 118 tokens

  Get detailed parameter information for a specific Stripe API operation. Provide the stripe_api_operation_id from stripe_api_search results to see all path, query, and body paramet…

  Paramètres, retour & exemple (1)

  Paramètres

  • stripe_api_operation_id · string · requis
    The operation ID to get details for (e.g. 'PostCustomers', 'GetPaymentIntents')

  Exemple d'appel

  {"name": "stripe.stripe_api_details", "arguments": {"stripe_api_operation_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• stripe.stripe_api_read≈ 194 tokens

  Read data from any Stripe API GET operation: 1. Use stripe_api_search to find the operation ID. 2. Use stripe_api_details to see its parameters, unless the search result already l…

  Paramètres, retour & exemple (2)

  Paramètres

  • parameters · object · optionnel
    All path, query, and request-body values for the API call. Include path parameters here, named as in the path's curly braces (e.g. 'id' for /v1/customers/{id}). Array fields (e.g. line_items) must be passed as a JSON array value, not as a plain string.
  • stripe_api_operation_id · string · requis
    The operation ID to execute

  Exemple d'appel

  {"name": "stripe.stripe_api_read", "arguments": {"stripe_api_operation_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• stripe.stripe_api_search≈ 188 tokens

  Search for Stripe API operations by providing an intent and a resource to operate on. For the resource, use a specific, descriptive phrase (e.g. "issuing card transactions", "pay…

  Paramètres, retour & exemple (3)

  Paramètres

  • limit · integer · optionnel
    Maximum number of results to return
  • intent · string · requis
    The intent of the operation
  • resource · string · requis
    Target resource the operation is looking to manipulate

  Exemple d'appel

  {"name": "stripe.stripe_api_search", "arguments": {"intent": "texte", "resource": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• stripe.stripe_api_write≈ 454 tokens

  Write data via any Stripe API POST/PATCH/PUT/DELETE operation: 1. Use stripe_api_search to find the operation ID. 2. Use stripe_api_details to see its parameters, unless the searc…

  Paramètres, retour & exemple (3)

  Paramètres

  • parameters · object · optionnel
    All path, query, and request-body values for the API call. Include path parameters here, named as in the path's curly braces (e.g. 'id' for /v1/customers/{id}). Array fields (e.g. line_items) must be passed as a JSON array value, not as a plain string.
  • human_confirmation · object · optionnel
    This tool might require human confirmation. To run it, first invoke it with the desired parameters, ignoring the `approval_token` parameter. If it requires human confirmation, the response will include an approval request ID and a URL to an approval page for the human to approve the tool call. You, as the LLM agent, should: 1. Present this URL to the human as a clickable markdown link. Tell them that they have to approve this tool call at that URL, and that they should tell you when they have approved the operation. 2. The human will approve that call. 3. After the human tells you they have approved the operation, you must call the tool again with the `approval_token` parameter and the exact same parameters. The operation will then go through.
  • stripe_api_operation_id · string · requis
    The operation ID to execute

  Exemple d'appel

  {"name": "stripe.stripe_api_write", "arguments": {"stripe_api_operation_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• stripe.stripe_implementation_planner≈ 281 tokens

  Stripe integration planner. Use this tool to help users accept payments, sell products online, set up billing, set up a marketplace or platform, or build any Stripe integration. C…

  Paramètres, retour & exemple (4)

  Paramètres

  • accept · boolean · optionnel
    Set to true when returning the completed decision trees with your chosen options. Include selected_leaf_nodes with the IDs of all terminal leaves reached.
  • message · string · optionnel
    For new guides: describe the use case or business requirements.
  • guide_id · string · optionnel
    ONLY pass a guide_id that was returned by a previous call to this tool in this conversation. Never fabricate, guess, or reuse guide_ids from other sessions. If you do not have a guide_id from a prior response, omit this field entirely. Invalid guide_ids will be rejected.
  • selected_leaf_nodes · array · optionnel
    The IDs of all terminal leaves reached while traversing the guide's decision tree.

  Exemple d'appel

  {"name": "stripe.stripe_implementation_planner", "arguments": {"accept": true, "message": "texte", "guide_id": "texte", "selected_leaf_nodes": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://api.metamesh-uga.dev/mcp