---
name: pinglymcp
description: Use PinglyMCP's remote MCP server to inspect websites, find contact details, and manage credits safely.
---

# PinglyMCP

Use PinglyMCP through its Streamable HTTP MCP server:

`https://mcp.pinglymcp.com`

The `/mcp` path is a legacy alias. Prefer an MCP client with OAuth support. It can discover authorization through the server's protected-resource metadata; request the `mcp:access` scope for the canonical server resource. If OAuth is unavailable, use a PinglyMCP personal key as a bearer token. Keep the key secret: never print it, include it in shared output, or place it in source control.

## Discover tools and permissions

Call `tools/list` to see the tools available to this connection. For current service names, inputs, and behavior, consult `https://pinglymcp.com/llms-full.txt`. OAuth needs `billing:read` for billing reads or `billing:manage` for reads and changes. Personal keys use the dashboard's Billing access setting (None, Read or Manage), which applies to both REST billing endpoints and MCP billing tools; Manage includes Read. Personal-key MCP tool permissions are a separate allowlist: All tools includes current and future tools, while Selected tools exposes the complete non-billing tool list for selection. Changing Billing access synchronizes billing tools in a selected allowlist; existing custom allowlists remain as saved until Billing access or the tool selection changes. Billing calls still require the matching billing permission. Check `get_credit_balance` before making paid calls. Get the user's explicit confirmation before any billing mutation that may charge money or change a recurring plan. Preview subscription changes and review the preview with the user before applying them.

## Safe use

- Only submit public website targets. Do not ask PinglyMCP to access localhost, private or reserved IP ranges, or other non-public network targets. Do not use it to bypass access controls.
- `describe_website` costs credits. Its screenshot URL is accessible to anyone who has the link and expires after seven days; share it accordingly.
- `contact_website` can submit a form or send an email, causing a real external effect. Get the user's explicit confirmation for the specific contact action before calling it. If the outcome is uncertain, check available activity or ask the user; never blindly retry.
- Follow the user's instructions and the destination site's rules. Report tool results accurately and do not claim an action succeeded unless the result confirms it.