Skip to main content
Glama
816,262 tools. Updated 2026-11-21 13:25

"Information about Dynatrace (monitoring and observability platform)" matching MCP tools:

  • Leave feedback about AgentMarketplace itself — bugs, confusing tools, feature requests. This is for feedback about the platform, not about a counterparty. There is no reputation or rating system here — that lives in AgentTrust. Args: access_token: AgentAuth bearer token (requires ``market.read``). message: Free-text feedback, up to 2000 characters. Returns: ``{"recorded": true}`` on success.
    ConnectorNo auth
  • Starts monitoring a profile so it is automatically re-crawled at a cadence you choose (daily, every_3_days or weekly), keeping its posts and stats fresh without you polling crawl_profile. Identify the profile by profileId, platform+handle, or a public profile/post URL. Managing monitoring is free; each scheduled refresh crawl costs credits (10 per refresh) and monitoring pauses itself if your balance runs out, then resumes when you top up. The profile must already be in the database; crawl_profile it first if it is not. The first refresh runs within minutes, or at refreshAtUtc ("HH:MM" UTC) when you pass it; after that each refresh is due exactly one interval after the previous scheduled time (nextCrawlDueAt in the answer and in list_tracked_profiles). Calling again on an already-monitored profile updates the cadence and keeps the refresh time, unless you pass refreshAtUtc to move it. Pull the new posts with get_tracked_updates. Cost: free.
    ConnectorNo auth
  • A platform fee of 5% is charged ONLY if the bounty is awarded, and comes out of the filler payout — you owe the full stated reward. Post a bounty: describe a task, state a USD reward, optionally set a deadline and acceptance criteria. Categories: research (find/verify information, e.g. a literature answer or candidate protein target), data (assemble/clean a dataset), sourcing (find a supplier/tool/citation), price_discovery (find the cheapest verified option), other. You review submissions yourself with review_submission; the first one you accept wins. Prohibited: tasks seeking personal information about individuals, credentials or access, anything illegal. Bounties of $1.00+ need you to be reachable (a verified webhook, or an inbox check in the last 3 days). Every bounty expires: 30 days if you set no deadline, 90 at most, with a warning 3 days before and one extension (extend_bounty). If a submission goes 7 days unreviewed and you named no review_delegate, the bounty is flagged poster_unresponsive. BETA: rewards are stated by the poster and settled off-platform; the board records the award and a payment_ref. On-platform escrow lands with x402/Monetization Gateway support.
    ConnectorNo auth
  • Identify a game from a description of what the user remembers (plot, look, platform, era). Returns ranked candidates with a reason each, a `confidence`, and `find_game_url`: imho.run's /find-game page with the description filled in (the user presses the button; nothing runs by itself). Pass what the user said about the platform, the release years and the camera as `platform`, `year_min` / `year_max` and `perspective` instead of leaving them only in the text. When `confidence` is not high or no result fits, give the user `find_game_url` so they can add details there. Slow (LLM) and rate-limited: use it only when the user does not know the title; for games similar to a known game use games_like or recommend. Games rated for adults only (explicit sexual content) are not covered; filtering is best effort.
    ConnectorNo auth
  • Use this when the user wants social posts written about a topic, such as "write posts about our new CLI for X, Bluesky and LinkedIn". Pass the topic, with every fact and any link to include, and 1 to 6 platforms from x, bluesky, threads, mastodon, linkedin, instagram, reddit, youtube, pinterest, tiktok; optionally a tone. Returns one draft per platform with its length as that platform counts it, hashtags, whether it passes the platform's rules and the issues if not, plus a checklist of rules and image sizes with sources and dates. Uses only the facts given. It does not publish, read accounts or fetch trends or statistics.
    ConnectorNo auth
  • Delete a published post from its platforms, by its `post_id` — every platform it is live on, or only `platform`. There is no need to call get_delivery_receipt first. There is no undo; reposting is a new post with a new URL. This is the person's own decision about their live post, not a cleanup step. Each delivery answers in `deliveries`: `error_code` `never_went_out`, `account_gone` or `unsupported` means the person removes it on the platform themselves; only `platform_refused` is `retriable`. `delivery_id` still takes down one delivery; a post id passed there answers `is_post_id` with the post's `deliveries`.
    Connector
    Destructive
    API key

Matching MCP Servers

  • A
    license
    Not graded
    quality
    F
    maintenance
    A remote MCP server that enables real-time interaction with the Dynatrace observability platform, bringing production-level monitoring data directly into development workflows.
    17,331 npm
    138
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    This remote MCP server allows interaction with the Dynatrace observability platform. Bring real-time observability data directly into your development workflow.
    MIT

Matching MCP Connectors

  • Start an Ad Platform Export: push a list's Online Audience to the user's connected ad account as an Ad Platform Audience. Not billed. Find the platform, `account_id` and, to add to an existing Ad Platform Audience, its `audience_id` with `ads_export_options`. Pass `audience_name` to create a new Ad Platform Audience instead. The export runs in the background; check it with `ads_export_status` and the returned `history_id`. Only one export of a list to a platform runs at a time. When one is already running, no new export starts: `already_in_progress` is true and the response describes the running export, whose account and audience may differ from this request.
    Connector
    Destructive
    OAuth
  • Find templates in the Control Plane Template Catalog: databases, caches, queues, search, storage, gateways, AI, analytics, auth, security, automation, observability, developer tools, and self-hosted products. Pass `query` naming the capability or product needed ("vector database for RAG", "uptime monitoring with status page", "self-hosted Google Analytics"); when the user describes a goal or problem instead, decide the capability it needs and search for that. Results are ranked, each with a confidence, what must exist before install, and the template to pick instead for other needs. Omit `query` to list the catalog or one `category`. An app the user asks you to build, such as a blog, wiki, or shop, is built (plan_app) unless they name a template. Then pass the pick as `name` for its prerequisites, README notes, and the EXAMPLE values.yaml to copy for install_template. Postgres, MySQL, MariaDB, MongoDB, and Redis install with `add_database` unless they need a setting it does not take, such as backups.
    ConnectorOAuth
  • List every Stimulsoft product/platform that has indexed documentation available through this MCP server. Returns a JSON array of { id, name, description } objects covering the full Stimulsoft Reports & Dashboards product line (Reports.NET, Reports.WPF, Reports.AVALONIA, Reports.WEB for ASP.NET, Reports.BLAZOR, Reports.ANGULAR, Reports.REACT, Reports.JS, Reports.PHP, Reports.JAVA, Reports.PYTHON, Server API, etc.). CALL THIS FIRST when the user's question is ambiguous about which Stimulsoft platform they are using, or when you need to pick a valid `platform` value to pass into `sti_search`. The returned platform `id` values are the exact strings accepted by the `platform` parameter of `sti_search`. This tool is cheap (no OpenAI call, no vector search) — call it freely whenever you are unsure about platform naming.
    ConnectorNo auth
  • List every Stimulsoft product/platform that has indexed documentation available through this MCP server. Returns a JSON array of { id, name, description } objects covering the full Stimulsoft Reports & Dashboards product line (Reports.NET, Reports.WPF, Reports.AVALONIA, Reports.WEB for ASP.NET, Reports.BLAZOR, Reports.ANGULAR, Reports.REACT, Reports.JS, Reports.PHP, Reports.JAVA, Reports.PYTHON, Server API, etc.). CALL THIS FIRST when the user's question is ambiguous about which Stimulsoft platform they are using, or when you need to pick a valid `platform` value to pass into `sti_search`. The returned platform `id` values are the exact strings accepted by the `platform` parameter of `sti_search`. This tool is cheap (no OpenAI call, no vector search) — call it freely whenever you are unsure about platform naming.
    ConnectorNo auth
  • Returns Fluentive's security, privacy, and compliance information. Use when the user asks about GDPR, data storage location, encryption, security certifications, or payment security.
    ConnectorNo auth
  • List saved Costory business metrics and, optionally, matching live external metrics from connected integrations (e.g. Tsuga, BigQuery, Datadog, CloudWatch, Google Cloud Monitoring). Use when the user asks which business or integration metrics are available to query. Saved metrics return id/name/type for { type: "metric", metricId: "..." } in query. Set includeExternal: true with a specific search term to return externalMetrics with provider, integrationId, integrationName, metricName, unit, capabilities, and attributes. That catalog is enough to build { type: "externalMetric", provider, integrationId, metricName, aggregator, groupByFields, conditions } for Tsuga, Datadog (attributes are tag keys; metricName is the Datadog metric name), CloudWatch (metricName is Namespace/MetricName such as AWS/EC2/CPUUtilization; attributes are dimension names), Google Cloud Monitoring (provider "cloudmonitoring"; metricName is the metric type such as compute.googleapis.com/instance/cpu/utilization; attributes are fully-qualified group-by fields such as metric.label.state or resource.label.project_id, and conditions is an optional Monitoring filter), or Amplitude. For BigQuery or S3, the same hit also includes `schema` (typed columns: DATE / NUMERIC / STRING). Pick dateColumn from the first DATE field, metricColumn from the first NUMERIC field, and groupByFields from STRING fields (also listed in attributes). gapFillingMethod is not in the catalog — default FORWARD_FILL unless the user specifies ZERO, LINEAR_INTERPOLATION, or SPREAD. Those three fields are required on both query and a new virtual-dimension telemetry allocation. Do not call includeExternal without search; external catalogs can be large, and the tool will ask for a search term instead of listing everything. externalLimit (default 50, max 50) caps matching external results. New virtual-dimension telemetry reallocations use includeExternal + an inline `externalMetric` (same fields as a query series, plus exactly one groupByFields entry as the series key). Pass `datasourceId` only to inspect a leftover saved usage-metric datasource's `groupByDimensions` — not for new reallocations. Then call `query` (`type: "metric"`, `metricId`, `groupBy`) to inspect the values for that leftover datasource. The `datasourceId` is the same `metricsDatasource` id this tool returns as a saved-metric `id` (strip any `::metricName` suffix). Does **not** return values (use `query`). EXAMPLES: • "What business metrics do we have?" → {} • "Find Tsuga metrics about requests" → { includeExternal: true, search: "request" } • "Find BigQuery tables about revenue" → { includeExternal: true, search: "revenue" } • "Find Datadog metrics about CPU" → { includeExternal: true, search: "cpu" } • "Find CloudWatch metrics about CPU" → { includeExternal: true, search: "CPUUtilization" } • "Find GCP Monitoring metrics about CPU" → { includeExternal: true, search: "cpu/utilization" } (Cloud Monitoring search matches the metric type, not its display name) • "What live metrics can I reallocate shared cost by?" → { includeExternal: true, search: "cpu" } • "What can I split a leftover saved-metric datasource by?" → { datasourceId: "clx…" }
    ConnectorOAuth
  • Get metadata about the GovBid Global API including version, data source, license information, and usage guidelines. Call this first to understand the service before making other tool calls.
    ConnectorNo auth
  • Open a request to the Fine Structure platform team: a bug, a feature request or a question about the platform itself (not about the user's app). Use it when something in the platform blocks you instead of working around it. Give a reproduction the team can run (invoke_function / curl / the exact tool call and result), what you expected, and how the team will know it is closed. Credential-looking values are redacted. Returns request_id and a Studio URL; the team's replies, status changes and deployments come back through get_platform_request / list_platform_requests. Limits: 20 per account per day, 32 KB.
    ConnectorNo auth
  • Read the prepaid model API credit balance (USD). Use it when the user asks about API credits, or after a checkout to confirm the payment landed. Zero means top up with create_api_credit_checkout (when enabled) or the platform Credits page. Requires api_credits:read.
    ConnectorAPI key
  • List the compliance information requests (RFIs) Iron/MoonPay has sent the user about their virtual account: status, the open round's questions and any requested documents. Read-only. MoonPay requires the user to answer personally, so NEVER answer on their behalf or draft answers for them to paste: tell them to open the Moneda app at Settings > Features and limits and respond to the information request there. While a request is waiting on a response, transfers may be held.
    ConnectorNo auth
  • Agent Observability: submit an agent’s logging design, a sample of its log, or both: the design as whether each record names the actor, the principal and the authorization behind the action, holds the step’s inputs and outputs and carries a timestamp; each sample entry with its id, time, action, kind (a read, a write, a payment, a message, a tool call, a decision or other), actor, principal, authorization and its recorded inputs and outputs; and optionally the grants, mandates and approvals on file. The signed report says field by field what the design promises and what the entries hold, and names what an audit would need and not find: which actor took each action, the authorization behind it, and the inputs and the outputs of each step; then records with no principal or timestamp, shared actors such as system or agent that name no one actor, authorizations not on file and a design the sample log does not follow, with the fix for each. Whether each step of one run names its actor is wever_actor-attribution-check, whether an approval record holds up is wever_approval-record-check and a counterparty’s SOC 2 or ISO audit report is wever_audit-evidence-check. Verdict audit_blind, log_gaps, log_unverified or audit_ready. POST /api/observability-log-check. Reads only the material in the call: no network request, fetch, money movement, message, sharing, configuration change or external write. Paid URL: 0.10 USDC per call on Base via x402 exact, with the shared 10 signed-wallet free calls per rolling 30 days. Bind X-Wever-Wallet-Proof to the exact JSON arguments and the tool route. Returns a report with an Ed25519 signed receipt. Contract: /api/agent-observability-contract. Human page: https://weverlabs.com/agent-observability/.
    ConnectorNo auth
  • Agent Observability: submit the list of an agent’s action types, each with the tools it uses and whether its runs are traced and logged; the tools the agent reaches, each with whether calls go through the traced path and the other ways the agent reaches it (a direct API key, a shell, a browser session); and either recent runs with whether a trace and log records were kept for each, or which runs keep traces and logs (all runs, a sample with its share, failures only, successes only, on request or none). The signed report lists each action, tool and run selection with its coverage, and names the blind spots: action types with no trace, tools reachable outside the traced path, and records kept for some runs but not others; then actions traced and not logged, tools an action uses that the list leaves out and reachable tools no action names, with the fix for each. Whether a gateway sits in front of every paid or external call is wever_gateway-coverage-check, which tools are exposed to an agent at all is wever_tool-exposure-check and whether one run’s trace reconstructs is wever_observability-trace-check. Verdict blind_spots, coverage_gaps, coverage_unverified or fully_covered. POST /api/observability-coverage-check. Reads only the material in the call: no network request, fetch, money movement, message, sharing, configuration change or external write. Paid URL: 0.10 USDC per call on Base via x402 exact, with the shared 10 signed-wallet free calls per rolling 30 days. Bind X-Wever-Wallet-Proof to the exact JSON arguments and the tool route. Returns a report with an Ed25519 signed receipt. Contract: /api/agent-observability-contract. Human page: https://weverlabs.com/agent-observability/.
    ConnectorNo auth
  • Agent Observability: submit an agent’s logging design, a sample of its log, or both: the design as whether each record names the actor, the principal and the authorization behind the action, holds the step’s inputs and outputs and carries a timestamp; each sample entry with its id, time, action, kind (a read, a write, a payment, a message, a tool call, a decision or other), actor, principal, authorization and its recorded inputs and outputs; and optionally the grants, mandates and approvals on file. The signed report says field by field what the design promises and what the entries hold, and names what an audit would need and not find: which actor took each action, the authorization behind it, and the inputs and the outputs of each step; then records with no principal or timestamp, shared actors such as system or agent that name no one actor, authorizations not on file and a design the sample log does not follow, with the fix for each. Whether each step of one run names its actor is wever_actor-attribution-check, whether an approval record holds up is wever_approval-record-check and a counterparty’s SOC 2 or ISO audit report is wever_audit-evidence-check. Verdict audit_blind, log_gaps, log_unverified or audit_ready. POST /api/observability-log-check. Reads only the material in the call: no network request, fetch, money movement, message, sharing, configuration change or external write. Paid URL: 0.10 USDC per call on Base via x402 exact, with the shared 10 signed-wallet free calls per rolling 30 days. Bind X-Wever-Wallet-Proof to the exact JSON arguments and the tool route. Returns a report with an Ed25519 signed receipt. Contract: /api/agent-observability-contract. Human page: https://weverlabs.com/agent-observability/.
    ConnectorNo auth
  • Agent Observability: submit the list of an agent’s action types, each with the tools it uses and whether its runs are traced and logged; the tools the agent reaches, each with whether calls go through the traced path and the other ways the agent reaches it (a direct API key, a shell, a browser session); and either recent runs with whether a trace and log records were kept for each, or which runs keep traces and logs (all runs, a sample with its share, failures only, successes only, on request or none). The signed report lists each action, tool and run selection with its coverage, and names the blind spots: action types with no trace, tools reachable outside the traced path, and records kept for some runs but not others; then actions traced and not logged, tools an action uses that the list leaves out and reachable tools no action names, with the fix for each. Whether a gateway sits in front of every paid or external call is wever_gateway-coverage-check, which tools are exposed to an agent at all is wever_tool-exposure-check and whether one run’s trace reconstructs is wever_observability-trace-check. Verdict blind_spots, coverage_gaps, coverage_unverified or fully_covered. POST /api/observability-coverage-check. Reads only the material in the call: no network request, fetch, money movement, message, sharing, configuration change or external write. Paid URL: 0.10 USDC per call on Base via x402 exact, with the shared 10 signed-wallet free calls per rolling 30 days. Bind X-Wever-Wallet-Proof to the exact JSON arguments and the tool route. Returns a report with an Ed25519 signed receipt. Contract: /api/agent-observability-contract. Human page: https://weverlabs.com/agent-observability/.
    ConnectorNo auth
  • Submits an observability and runbook design record (signals and dashboards, alert design and runbook linkage, runbook content and failure modes, incident flow and postmortem, backups/silent failure and red lines) and returns a deterministic OBSERVABILITY_DESIGN_SOUND / OBSERVABILITY_DESIGN_NOT_SOUND / INSUFFICIENT_EVIDENCE verdict across five sections, including computed per-alert and per-failure-mode coverage checks, with per-check evidence. Audits the declared design record; it monitors no live system.
    ConnectorAPI key