# io.github.chinlee2200-dotcom/bridgecore (remote · mcp.usebridgecore.com)

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

- Trust score: 69/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `mcp.usebridgecore.com`: 69/100 (this document), [markdown](https://verifymcp.io/servers/chinlee2200-dotcom-bridgecore/mcp.md), [page](https://verifymcp.io/servers/chinlee2200-dotcom-bridgecore/mcp)

## Channel facts

- Endpoint: `https://mcp.usebridgecore.com/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.2`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-23.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 76/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1027 tokens (~205/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the io.github.chinlee2200-dotcom/bridgecore MCP server?

io.github.chinlee2200-dotcom/bridgecore is a hosted endpoint at https://mcp.usebridgecore.com/, 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.

### Claude

```bash
claude mcp add --transport http chinlee2200-dotcom-bridgecore 'https://mcp.usebridgecore.com/'
```

### Cursor

```json
{
  "mcpServers": {
    "chinlee2200-dotcom-bridgecore": {
      "url": "https://mcp.usebridgecore.com/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "chinlee2200-dotcom-bridgecore": {
      "type": "http",
      "url": "https://mcp.usebridgecore.com/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.chinlee2200-dotcom-bridgecore]
url = "https://mcp.usebridgecore.com/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "chinlee2200-dotcom-bridgecore": {
      "type": "remote",
      "url": "https://mcp.usebridgecore.com/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add chinlee2200-dotcom-bridgecore --url 'https://mcp.usebridgecore.com/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  chinlee2200-dotcom-bridgecore:
    url: "https://mcp.usebridgecore.com/"
```

### Netclaw

```json
{
  "McpServers": {
    "chinlee2200-dotcom-bridgecore": {
      "Transport": "http",
      "Url": "https://mcp.usebridgecore.com/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add chinlee2200-dotcom-bridgecore -t streamable-http -u 'https://mcp.usebridgecore.com/'
```

### Other

```json
{
  "mcpServers": {
    "chinlee2200-dotcom-bridgecore": {
      "type": "http",
      "url": "https://mcp.usebridgecore.com/"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-22 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-20 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-19 (score 67, 0)

- [security] Tool “do” rewrote its description, which is the text the model reads

### 2026-10-18 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-16 (score 66, +1)

- [functional regression] Schema quality: 810 → 1027
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 0.3.1 → 0.3.2
- [functional] New tool “inspect_workflow”

### 2026-10-15 (score 65)

First indexed and scored.

## MCP tools (5)

### `do` (~276 tokens)

Do it (find the capability, preview the exact call)

One tool for 3,604 app capabilities (n8n catalog + OpenAPI + MCP): say what should happen; get the exact call. Plain words in ('send an sms to +1 213 555 0100 saying hello', 'add a row to google sheets'); the matching capability is found, its required inputs are checked (values you said out loud — emails, #channels, +phones — are filled for you), and the exact HTTP/MCP request that would be sent is returned, with `missing` naming any input still needed. Preview only: this server never sends the request and never accepts credentials. A 'when …' need or several steps returns one preview per step; n8n-only steps come back as an importable n8n workflow. Running the request for real is offered separately by the Bridgecore Apify Actor (apify.com/bridgecore/bridgecore-automation-planner).

Input parameters:

- `dry_run` (boolean): Kept for compatibility; this server always previews and never sends.
- `inputs` (object): Values for the capability's inputs by name (see `missing` in a dry run). Optional.
- `need` (string, required): What should happen, in plain words. One action to run it ('text +1… saying hi'); 'when …' for a flow.

Output parameters:

- `charged` (integer): successful calls billed
- `dry_run` (boolean): true = nothing was sent
- `fee_usd` (number): price per successful real call
- `need` (string)
- `note` (string)
- `ran` (integer): real calls made
- `steps` (array): per step: capability, request (headers masked), missing inputs, status/data/error
- `workflow` (object): n8n workflow when a step can only run inside n8n

### `find_recipe` (~146 tokens)

Find a ready-made automation recipe

Find a ready-made automation recipe for a plain-words need, e.g. 'when a typeform is submitted add a row to google sheets and send a slack message'. Returns the best matching recipes (apps chained with →, what it does, the n8n workflow JSON, the blanks to fill and accounts to connect) plus matching public n8n templates (title + official link). Covers connecting apps, automating a workflow, syncing tools, and getting notified when something happens.

Input parameters:

- `limit` (integer): How many recipes to return (1-10).
- `need` (string, required): What should happen, in plain words. Start with 'when …' for the trigger.

Output parameters:

- `need` (string)
- `planned_steps` (array)
- `public_templates` (array): public n8n templates: title + official link
- `recipes` (array): matching tested recipes, each with its n8n workflow, blanks and accounts

### `plan_automation` (~112 tokens)

Plan an automation (tool per step)

Turn a plain-words need into steps (one trigger + actions) and pick the concrete tool for each step from 3,000+ app capabilities (n8n nodes, OpenAPI, MCP). Reports a gap when the named app cannot do a step instead of substituting another app.

Input parameters:

- `alternatives` (integer): Runner-up tools to list per step (1-5).
- `need` (string, required): What should happen, in plain words: 'when <trigger> <action>, then <action>'.

Output parameters:

- `need` (string)
- `steps` (array): trigger + actions, each with the best tool, alternatives, or a gap

### `make_n8n_workflow` (~248 tokens)

Make an importable n8n workflow

Generate an importable n8n workflow JSON from a plain-words need, with every node wired in order, values said out loud already filled (emails, #channels, trigger events), plus the list of blanks only the person can fill and the credentials to connect. Shape-checked; the person tests it in n8n before turning it on. Say 'and ask me first' (or approval='always') and a one-tap approval gate — a Slack/Telegram/Gmail message with Approve / Decline buttons — goes in front of the step, so nothing is sent, posted, deleted or paid until the person taps Approve.

Input parameters:

- `approval` (string): auto = gate the steps the need asks to approve ('ask me first'); always = gate every irreversible step (send, post, delete, pay); never = no gates.
- `name` (string): Workflow name shown in n8n (optional; made from the need when left out).
- `need` (string, required): What should happen, in plain words. Start with 'when …' for the trigger; add 'and ask me first' before a step the person wants to approve.

Output parameters:

- `accounts` (array): credentials to connect
- `approval` (object): which steps got an Approve/Decline gate, through which app, and how to add one
- `how_to_import` (string)
- `links` (object)
- `need` (string)
- `problems` (array): shape-check findings (empty = clean)
- `steps` (array): one per step: tool, reversibility (read-only / reversible / irreversible), approval_gate
- `to_fill` (array): blanks only the person can fill
- `workflow` (object): importable n8n workflow JSON

### `inspect_workflow` (~217 tokens)

Check an existing n8n workflow before running it

Read an existing n8n workflow JSON (a template from n8n.io, an export, anything) and say what it would do before it runs: every node's label (read-only / reversible / irreversible, computed from the node's own resource + operation), which irreversible steps (send, post, delete, pay) would run with nobody asked, which steps already have an approval in front of them, and which nodes have no account connected. With add_gates=true it returns a copy of the workflow with a one-tap Approve / Decline step (Slack, Telegram, Gmail…) wired in front of every such step. Nothing is run; the original is not modified.

Input parameters:

- `add_gates` (boolean): Also return `gated_workflow`: a copy that asks before every irreversible step.
- `ask_via` (string): Where the Approve / Decline message goes.
- `workflow` (object, required): The n8n workflow JSON (nodes + connections), as exported or as a template's JSON.

Output parameters:

- `accounts_missing` (array)
- `counts` (object): nodes per label
- `gated` (array)
- `gated_workflow` (object): only with add_gates: the workflow with Approve/Decline gates added
- `name` (string|null)
- `nodes` (array): every node: app, label, why, gated, has_account
- `risky` (array): irreversible nodes with no approval in front
- `to_fill` (array)
- `verdict` (string): one line: what would run without asking
- `verified` (object)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/chinlee2200-dotcom-bridgecore/mcp#diagnostics

## Score history

- 2026-10-23: 69
- 2026-10-22: 69
- 2026-10-21: 68
- 2026-10-20: 68
- 2026-10-19: 67
- 2026-10-18: 67
- 2026-10-17: 66
- 2026-10-16: 66
- 2026-10-15: 65

## Common questions

### What is the io.github.chinlee2200-dotcom/bridgecore MCP server?

io.github.chinlee2200-dotcom/bridgecore is an MCP server listed in the public MCP registry as io.github.chinlee2200-dotcom/bridgecore. Say what should happen; get the right app tool per step, an n8n workflow, or the call itself. This page covers its hosted endpoint (https://mcp.usebridgecore.com/).

### Is the io.github.chinlee2200-dotcom/bridgecore MCP server safe to use?

io.github.chinlee2200-dotcom/bridgecore scores 69 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.

### What tools does the io.github.chinlee2200-dotcom/bridgecore MCP server expose?

io.github.chinlee2200-dotcom/bridgecore exposes 5 tools: do, find_recipe, plan_automation, make_n8n_workflow, inspect_workflow. Their descriptions and schemas cost roughly 999 tokens of context every time the server is loaded.

### Does the io.github.chinlee2200-dotcom/bridgecore MCP server require authentication?

No. We connected to io.github.chinlee2200-dotcom/bridgecore without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the io.github.chinlee2200-dotcom/bridgecore MCP server still maintained?

io.github.chinlee2200-dotcom/bridgecore is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.usebridgecore.com/
- Repository: https://github.com/chinlee2200-dotcom/Laboratory-
- Website: https://usebridgecore.com/
- Changelog RSS feed: https://verifymcp.io/servers/chinlee2200-dotcom-bridgecore/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/chinlee2200-dotcom-bridgecore/mcp.json
- HTML version of this page: https://verifymcp.io/servers/chinlee2200-dotcom-bridgecore/mcp