MCP.Market

Pinbridge MCP server

online · 100% uptime
by pinbridge.io·io.pinbridge/pinbridge·v1.4.2

Publish and schedule Pinterest pins from any MCP client. Token refresh and retries handled.

B77/100grade B
What users say
No reviews yet
Be the first
Safety scan
B77/100

not scanned yet

Adoption
New

Little public usage data yet

Reviews

Write one

Nobody has reviewed Pinbridge yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Pinbridge tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Pinbridge compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
77/100
higher than 50% of 48,243 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
574 ms
faster than 28% of 30,027 servers

Release history: 2 versions in the registry since 2026-09-19, latest 2026-10-10, typically one every 21 days.

Install Pinbridge in Claude Code, Cursor or VS Code

claude mcp add --transport http pinbridge https://mcp.pinbridge.io
Add to Cursor

Grade history

  • 2026-10-03restoreC → Bscore 77: No source repository listed

Pinbridge: common questions

Is Pinbridge MCP server safe?
Mostly: it is graded B (77/100). Read the Pinbridge safety report
How do I install Pinbridge?
It runs remotely at mcp.pinbridge.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Pinbridge need an API key?
Yes. The registry entry asks for Authorization.
Is Pinbridge maintained?
The latest release is v1.4.2.
Is Pinbridge up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Pinbridge compare with other MCP servers?
safety score 77/100 (higher than 50% of 48,243 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 574 ms (faster than 28% of 30,027 servers). Full comparison.