MCP.Market

Bridgecore MCP server

online · 100% uptime
by chinlee2200-dotcom·io.github.chinlee2200-dotcom/bridgecore·v0.3.2
No reviews yet

Say what should happen; get the right app tool per step, an n8n workflow, or the call itself.

C63/100grade C
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
C63/100

not scanned yet

Adoption
New

Little public usage data yet

Reviews

Write one

Nobody has reviewed Bridgecore yet.

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

Bridgecore 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 Bridgecore compares

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

Safety score
63/100
higher than 18% of 48,273 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
919 ms
faster than 14% of 30,037 servers

Release history: 3 versions in the registry since 2026-10-14, latest 2026-10-15, typically one every 1 day.

Install Bridgecore in Claude Code, Cursor or VS Code

claude mcp add --transport http bridgecore https://mcp.usebridgecore.com/
Add to Cursor

Bridgecore: common questions

Is Bridgecore MCP server safe?
With care: it is graded C, so read the findings first (63/100). Read the Bridgecore safety report
How do I install Bridgecore?
It runs remotely at mcp.usebridgecore.com. 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 Bridgecore need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Bridgecore maintained?
The latest release is v0.3.2.
Is Bridgecore up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Bridgecore compare with other MCP servers?
safety score 63/100 (higher than 18% of 48,273 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 919 ms (faster than 14% of 30,037 servers). Full comparison.