pingoru-public

endpoint

https://pingoru.io/api/mcp-public/

protocol

http-sse ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is pingoru-public live?

Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.

Is pingoru-public free to use?

Yes — the hub reached it with no key and no payment.

What tools does pingoru-public have?

6 tools: provider_components, provider_incidents, incident_detail, component_status, provider_status, search_providers.

Is pingoru-public safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• provider_components unknown never probed

  List a provider's components with current status. Use to drill into 'which AWS components are broken right now?' style questions. Set only_problematic=true to filter out the operational ones. Slug accepts shorthand / typos via fuzzy fallback (see provider_status docstring).

  mcp-tool

  123456789101112131415161718

  {
    "type": "object",
    "title": "provider_componentsArguments",
    "required": [
      "slug"
    ],
    "properties": {
      "slug": {
        "type": "string",
        "title": "Slug"
      },
      "only_problematic": {
        "type": "boolean",
        "title": "Only Problematic",
        "default": false
      }
    }
  }

  arguments 18 lines copy
• provider_incidents unknown never probed

  Recent incident history for a provider (days clamped to 1-30), plus a separate `maintenance` list: maintenance scheduled or held in the window, including upcoming windows. Each item has its current status (investigating / identified / monitoring / resolved, scheduled / in_progress / completed), start and resolve times, duration, impact, affected components, the vendor's link and the Pingoru page (pingoru_url). Pass component (substring match on component name) to scope to one component. Slug accepts shorthand / typos via fuzzy fallback.

  mcp-tool

  123456789101112131415161718192021222324252627282930

  {
    "type": "object",
    "title": "provider_incidentsArguments",
    "required": [
      "slug"
    ],
    "properties": {
      "days": {
        "type": "integer",
        "title": "Days",
        "default": 7
      },
      "slug": {
        "type": "string",
        "title": "Slug"
      },
      "component": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Component",
        "default": null
      }
    }
  }

  arguments 30 lines copy
• incident_detail unknown never probed

  Full record for one incident or maintenance: current status, impact, start / resolve times and duration, scheduled window (for maintenance), affected components, the vendor's link, the Pingoru page (pingoru_url) and every status update with its timestamp. Use to summarise 'what happened during the May 3 outage'. Covers the last 30 days plus anything still open. Slug accepts shorthand / typos via fuzzy fallback.

  mcp-tool

  123456789101112131415161718

  {
    "type": "object",
    "title": "incident_detailArguments",
    "required": [
      "slug",
      "incident_id"
    ],
    "properties": {
      "slug": {
        "type": "string",
        "title": "Slug"
      },
      "incident_id": {
        "type": "integer",
        "title": "Incident Id"
      }
    }
  }

  arguments 18 lines copy
• component_status unknown 1h ago

  Pinpoint the status of one component by name (case-insensitive substring match). Returns an error when the name matches multiple components — the agent should ask the user to disambiguate. Slug accepts shorthand / typos via fuzzy fallback.

  mcp-tool

  123456789101112131415161718

  {
    "type": "object",
    "title": "component_statusArguments",
    "required": [
      "slug",
      "component"
    ],
    "properties": {
      "slug": {
        "type": "string",
        "title": "Slug"
      },
      "component": {
        "type": "string",
        "title": "Component"
      }
    }
  }

  arguments 18 lines copy
• provider_status unknown 1h ago

  Get the current status and any active incidents for a status-page vendor. Use when the user asks 'is X down?' or 'is X having problems?'. slug: Provider slug or human name. Exact slug ('github', 'amazon-web-services', 'google-cloud') is matched first; on miss we fall back to a search lookup so common shorthands ('aws', 'gcp', 'github actions') and minor typos still resolve. The response includes `matched_via: 'fuzzy'` and the original query when fuzzy fallback was used so the agent can confirm with the user.

  mcp-tool

  12345678910111213

  {
    "type": "object",
    "title": "provider_statusArguments",
    "required": [
      "slug"
    ],
    "properties": {
      "slug": {
        "type": "string",
        "title": "Slug"
      }
    }
  }

  arguments 13 lines copy
• search_providers unknown 1h ago

  Find providers by name or slug. Use when the agent does not know the exact slug ('look up that DBaaS… planetscale?'). Uses Meilisearch under the hood so typos and shorthand still match — 'aws', 'gcp', 'githb', 'k8s' all resolve to the right vendor.

  mcp-tool

  123456789101112131415161718

  {
    "type": "object",
    "title": "search_providersArguments",
    "required": [
      "query"
    ],
    "properties": {
      "limit": {
        "type": "integer",
        "title": "Limit",
        "default": 10
      },
      "query": {
        "type": "string",
        "title": "Query"
      }
    }
  }

  arguments 18 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.