PineLabs Plural PG — Payment Gateway MCP Server
REMOTE · MCP.PINELABS.COM · 3 COMPONENTS · SCANNED SEP 20
Create payment orders, checkout, subscriptions & UPI via PineLabs Plural PG gateway
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
How do I install the PineLabs Plural PG — Payment Gateway MCP Server server?
PineLabs Plural PG — Payment Gateway MCP Server is a hosted endpoint at https://mcp.pinelabs.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.pinelabs.com
claude mcp add --transport http plural-pinelabs-pinelabs-online-mcp 'https://mcp.pinelabs.com/mcp'
{
"mcpServers": {
"plural-pinelabs-pinelabs-online-mcp": {
"url": "https://mcp.pinelabs.com/mcp"
}
}
} {
"servers": {
"plural-pinelabs-pinelabs-online-mcp": {
"type": "http",
"url": "https://mcp.pinelabs.com/mcp"
}
}
} [mcp_servers.plural-pinelabs-pinelabs-online-mcp] url = "https://mcp.pinelabs.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"plural-pinelabs-pinelabs-online-mcp": {
"type": "remote",
"url": "https://mcp.pinelabs.com/mcp",
"enabled": true
}
}
} openclaw mcp add plural-pinelabs-pinelabs-online-mcp --url 'https://mcp.pinelabs.com/mcp' --transport streamable-http
mcp_servers:
plural-pinelabs-pinelabs-online-mcp:
url: "https://mcp.pinelabs.com/mcp" {
"McpServers": {
"plural-pinelabs-pinelabs-online-mcp": {
"Transport": "http",
"Url": "https://mcp.pinelabs.com/mcp"
}
}
} assistant mcp add plural-pinelabs-pinelabs-online-mcp -t streamable-http -u 'https://mcp.pinelabs.com/mcp'
{
"mcpServers": {
"plural-pinelabs-pinelabs-online-mcp": {
"type": "http",
"url": "https://mcp.pinelabs.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Sept 26 0
- HSTS header: unverified → fail ▼ security
- Transport: fail → unverified ▼ security
- Authorization: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- Tool safety: Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools. security
- Tool coverage: Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools. functional
- Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it. functional
- Capabilities: Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. functional
- 3 Sept 26 0
- Transport: unverified → fail ▼ security
- Authorization: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Tool safety: Tool safety not yet verified: we couldn't read the endpoint's tools. security
- Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities. functional
- Schema quality: Schema not yet verified: we couldn't read the endpoint's schema. functional
- Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools. functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 22 Aug 26 36
- Authorization: fail → pass ▲ security
- First check of Authorization: partial security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://mcp.pinelabs.com/mcp
TLS valid
Negotiated TLS 1.2 with TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.pinelabs.com | CN=Go Daddy Secure Certificate Authority - G2,OU=http://certs.godaddy.com/repository/,O=GoDaddy.com\, Inc.,L=Scottsdale,ST=Arizona,C=US | 13 Feb 2026 | 3 Mar 2027 | RSA 2048 | SHA256-RSA | befdf5ac4a90aca5 |
| SANs: *.pinelabs.com, pinelabs.com | ||||||
| CN=Go Daddy Secure Certificate Authority - G2,OU=http://certs.godaddy.com/repository/,O=GoDaddy.com\, Inc.,L=Scottsdale,ST=Arizona,C=US (CA) | CN=Go Daddy Root Certificate Authority - G2,O=GoDaddy.com\, Inc.,L=Scottsdale,ST=Arizona,C=US | 3 May 2011 | 3 May 2031 | RSA 2048 | SHA256-RSA | 7 |
| CN=Go Daddy Root Certificate Authority - G2,OU=https://certs.godaddy.com/repository/,O=GoDaddy.com\, Inc.,L=Scottsdale,ST=Arizona,C=US (CA) | OU=Go Daddy Class 2 Certification Authority,O=The Go Daddy Group\, Inc.,C=US | 3 May 2011 | 3 May 2031 | RSA 2048 | SHA256-RSA | 2003 |
| OU=Go Daddy Class 2 Certification Authority,O=The Go Daddy Group\, Inc.,C=US (CA) | OU=Go Daddy Class 2 Certification Authority,O=The Go Daddy Group\, Inc.,C=US | 29 Jun 2004 | 29 Jun 2034 | RSA 2048 | SHA1-RSA | 0 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.pinelabs.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| pinelabs.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer realm="pinelabs-mcp", resource_metadata="https://mcp.pinelabs.com/.well-known/oauth-protected-resource", error="invalid_request", error_description="Authentication required. Provide an OAuth Bearer token or X-Client-Id/X-Client-Secret headers."
Bearer realm="pinelabs-mcp", resource_metadata="https://mcp.pinelabs.com/.well-known/oauth-protected-resource", error="invalid_request", error_description="Authentication required. Provide an OAuth Bearer token or X-Client-Id/X-Client-Secret headers."| Header | Value |
|---|---|
| www-authenticate | Bearer realm="pinelabs-mcp", resource_metadata="https://mcp.pinelabs.com/.well-known/oauth-protected-resource", error="invalid_request", error_description="Authentication required. Provide an OAuth Bearer token or X-Client-Id/X-Client-Secret headers." |
Protected resource metadata
| Document | https://mcp.pinelabs.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.pinelabs.com/mcp |
| Authorisation server | https://mcp.pinelabs.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.pinelabs.com/mcp | Auth required | 401 | |
| http (plaintext) | http://mcp.pinelabs.com/mcp | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
No tool schema has been captured from this endpoint yet.
What is the PineLabs Plural PG — Payment Gateway MCP Server server?
PineLabs Plural PG — Payment Gateway MCP Server is listed in the public MCP registry as io.github.plural-pinelabs/pinelabs-online-mcp. Create payment orders, checkout, subscriptions & UPI via PineLabs Plural PG gateway. This page covers its hosted endpoint (https://mcp.pinelabs.com/mcp).
Is the PineLabs Plural PG — Payment Gateway MCP Server server safe to use?
PineLabs Plural PG — Payment Gateway MCP Server scores 36 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
Does the PineLabs Plural PG — Payment Gateway MCP Server server require authentication?
Yes. PineLabs Plural PG — Payment Gateway MCP Server asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the PineLabs Plural PG — Payment Gateway MCP Server server still maintained?
PineLabs Plural PG — Payment Gateway MCP Server is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.