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.
Available components
Last scanned (17 hours ago)
Scores higher than 59% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Workflow Automation
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 22 Oct 26 +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.
- 20 Oct 26 +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.
- 19 Oct 26 0
- Tool “do” rewrote its description, which is the text the model reads security
- 18 Oct 26 +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.
- 16 Oct 26 +1
- Schema quality: 810 → 1027 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Server version: 0.3.1 → 0.3.2 functional
- New tool “inspect_workflow” functional
- 15 Oct 26 65
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 23 Oct 2026 · Probed https://mcp.usebridgecore.com/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usebridgecore.com | CN=WE1,O=Google Trust Services,C=US | 15 Oct 2026 | 13 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | f3b111dc154b86e413ff68c51c7ea8fb |
| SANs: usebridgecore.com, mcp.usebridgecore.com, *.mcp.usebridgecore.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.usebridgecore.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| usebridgecore.com. | 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 | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.usebridgecore.com/ | Verified | 200 | |
| http (plaintext) | http://mcp.usebridgecore.com/ | Inconclusive | 405 |
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 →
do Do it (find the capability, preview the exact call) ~276
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | What should happen, in plain words. One action to run it ('text +1… saying hi'); 'when …' for a flow. |
| Name | Type | Req | Description |
|---|---|---|---|
| charged | integer | – | successful calls billed |
| dry_run | boolean | – | true = nothing was sent |
| fee_usd | number | – | price per successful real call |
| need | string | yes | – |
| 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 |
No examples provided.
find_recipe Find a ready-made automation recipe ~146
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many recipes to return (1-10). |
| need | string | yes | What should happen, in plain words. Start with 'when …' for the trigger. |
| Name | Type | Req | Description |
|---|---|---|---|
| need | string | yes | – |
| 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 |
No examples provided.
inspect_workflow Check an existing n8n workflow before running it ~217
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The n8n workflow JSON (nodes + connections), as exported or as a template's JSON. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | one line: what would run without asking |
| verified | object | – | – |
No examples provided.
make_n8n_workflow Make an importable n8n workflow ~248
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| 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 |
No examples provided.
plan_automation Plan an automation (tool per step) ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| alternatives | integer | – | Runner-up tools to list per step (1-5). |
| need | string | yes | What should happen, in plain words: 'when <trigger> <action>, then <action>'. |
| Name | Type | Req | Description |
|---|---|---|---|
| need | string | yes | – |
| steps | array | – | trigger + actions, each with the best tool, alternatives, or a gap |
No examples provided.
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.
remote · mcp.usebridgecore.com
claude mcp add --transport http chinlee2200-dotcom-bridgecore 'https://mcp.usebridgecore.com/'
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.