← Registry

Developer Tools

metamesh-uga.dev

Provides a gateway for discovering and managing MCP tools from a large catalog.

x402 supported1 endpoint15 known toolsFirst detected July 14, 2026Last detected August 29, 2026

ENDPOINT 1

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

No auth detected

MCP server metadata

Name
metamesh-uga-gateway
Version
1.0.0
Capabilities
tools

Known tools 15

metamesh.context

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

Potential side effects
metamesh.search_tools

Search the catalog of 13k+ MCP tools by keyword.

Inferred read-only
metamesh.tool_info

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

Inferred read-only
metamesh.metrics

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

Inferred read-only
metamesh.discovery_status

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

Inferred read-only
metamesh.health

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

Potential side effects
stripe.stripe_implementation_planner

Stripe payment integration planner.

Potential side effects
stripe.send_stripe_mcp_feedback

Submit feedback from user or agent about Stripe's MCP server tools.

Inferred read-only
stripe.search_stripe_documentation

Search the Stripe documentation for the given question and language.

Inferred read-only
stripe.get_stripe_account_info

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

Inferred read-only
stripe.stripe_api_search

Search for Stripe API operations by providing an intent and a resource to operate on.

Inferred read-only
stripe.stripe_api_details

Get detailed parameter information for a specific Stripe API operation.

Inferred read-only
stripe.stripe_api_read

Read data from any Stripe API GET operation: 1.

Inferred read-only
stripe.stripe_api_write

Write data via any Stripe API POST/PATCH/PUT/DELETE operation: 1.

Potential side effects
stripe.stripe_analytics

This tool is for analyzing Stripe Sigma and Metrics data (e.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.metamesh-uga-gateway]
url = "https://api.metamesh-uga.dev/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "metamesh-uga-gateway": {
      "type": "http",
      "url": "https://api.metamesh-uga.dev/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: metamesh-uga-gateway
Remote MCP URL: https://api.metamesh-uga.dev/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "metamesh-uga-gateway": {
      "url": "https://api.metamesh-uga.dev/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "metamesh-uga-gateway": {
      "type": "http",
      "url": "https://api.metamesh-uga.dev/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "metamesh-uga-gateway",
  "transport": "streamable-http",
  "url": "https://api.metamesh-uga.dev/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for metamesh-uga.dev was fetched 2026-07-27T22:25:55.290Z and is being refreshed.

Trust status Neutral

metamesh-uga.dev is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.