Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.boy-373/mcp-marketplace

REMOTE · MCP.PIANAM.CN · SCANNED AUG 25

Search 25000+ MCP servers via AI. MCP SSE and A2A supported.

Available components

18 Trust /100
Trust breakdown (6 categories)

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 →

Endpoint Security46
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 4 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.

Install

How do I install the io.github.boy-373/mcp-marketplace server?

io.github.boy-373/mcp-marketplace is a hosted endpoint at https://mcp.pianam.cn/search/sse, 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.pianam.cn

# add to Claude Code
claude mcp add --transport http boy-373-mcp-marketplace 'https://mcp.pianam.cn/search/sse'
// .cursor/mcp.json
{
  "mcpServers": {
    "boy-373-mcp-marketplace": {
      "url": "https://mcp.pianam.cn/search/sse"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "boy-373-mcp-marketplace": {
      "type": "http",
      "url": "https://mcp.pianam.cn/search/sse"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.boy-373-mcp-marketplace]
url = "https://mcp.pianam.cn/search/sse"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "boy-373-mcp-marketplace": {
      "type": "remote",
      "url": "https://mcp.pianam.cn/search/sse",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add boy-373-mcp-marketplace --url 'https://mcp.pianam.cn/search/sse' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  boy-373-mcp-marketplace:
    url: "https://mcp.pianam.cn/search/sse"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "boy-373-mcp-marketplace": {
      "Transport": "http",
      "Url": "https://mcp.pianam.cn/search/sse"
    }
  }
}
# add to Vellum
assistant mcp add boy-373-mcp-marketplace -t streamable-http -u 'https://mcp.pianam.cn/search/sse'
// mcp.json
{
  "mcpServers": {
    "boy-373-mcp-marketplace": {
      "type": "http",
      "url": "https://mcp.pianam.cn/search/sse"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 25 Aug 26 18

    First indexed and scored.

Diagnostics

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 25 Aug 2026 · Probed https://mcp.pianam.cn/search/sse

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.pianam.cn CN=YE1,O=Let's Encrypt,C=US 24 Aug 2026 22 Nov 2026 ECDSA 256 ECDSA-SHA384 67c0f4f55d8565ac1f9e1bc8ddddc3ea56e
SANs: mcp.pianam.cn
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd
DNSSEC insecure

Validation of mcp.pianam.cn. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
cn. present 33094 8 Verified
pianam.cn. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 404
Transports 2 probes
Transport URL Outcome Status Location
sse https://mcp.pianam.cn/search/sse HTTP error 404
http (plaintext) http://mcp.pianam.cn/search/sse Inconclusive 404
MCP tools

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.

No tool schema has been captured from this endpoint yet.

Common questions

What is the io.github.boy-373/mcp-marketplace server?

io.github.boy-373/mcp-marketplace is listed in the public MCP registry as io.github.boy-373/mcp-marketplace. Search 25000+ MCP servers via AI. MCP SSE and A2A supported. This page covers its hosted endpoint (https://mcp.pianam.cn/search/sse).

Is the io.github.boy-373/mcp-marketplace server safe to use?

io.github.boy-373/mcp-marketplace scores 18 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 io.github.boy-373/mcp-marketplace server require authentication?

No. We connected to io.github.boy-373/mcp-marketplace without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.boy-373/mcp-marketplace server still maintained?

io.github.boy-373/mcp-marketplace is still listed as active in the MCP registry. We last reached this channel on 25 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.