bridgecore MCP server
io.github.chinlee2200-dotcom/bridgecorechinlee2200-dotcomstreamable-httpv0.3.2Scanned
Say what should happen; get the right app tool per step, an n8n workflow, or the call itself.
5 tools: 1 do something that can't be undone, 3 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- 4 findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the bridgecore MCP server can do
The bridgecore MCP server is published by the GitHub account chinlee2200-dotcom. It has 5 tools. It can do things that cannot be undone, such as sending, paying or publishing (inspect_workflow) and create or change data (3 tools: do, plan_automation and make_n8n_workflow), but cannot delete data. 1 tool only reads.
1 tool brings in text other people can write (inspect_workflow).
The fixed checks matched 4 findings (credentials-mention and annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 16, 2026, version 0.3.2.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Can't be undone 1Claude Code: ask
inspect_workflowRead 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,…Reads text others write1 finding
Why it is in this group
- The name "inspect_workflow" says "inspect": a word for reading.
- The description says "irreversible".
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe description's first sentence says "read" and "post": it reads posts, which other people can write.
Findings
- Warn
The server marks "inspect_workflow" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "inspect_workflow" says "inspect": a word for reading.
Description, as the server wrote 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.
Annotations the server declares
- title: Inspect workflow
- readOnlyHint: true
- openWorldHint: false
Changes things 3Claude Code: ask
doOne tool for 3,638 app capabilities (n8n catalog + OpenAPI + MCP): say what should happen; get the exact call.1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...ver sends the request and never accepts credentials. A 'when …' need or several steps retur..."
Description, as the server wrote it One tool for 3,638 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).
Annotations the server declares
- title: Do it (preview)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
make_n8n_workflowGenerate 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 …2 findings
Why it is in this group
- The description's first verb is "generate": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...blanks only the person can fill and the credentials to connect. Shape-checked; the person t..."
- Warn
The server marks "make_n8n_workflow" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The description's first verb is "generate": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- title: Make n8n workflow
- readOnlyHint: true
- openWorldHint: false
plan_automationTurn 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).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Plan automation
- readOnlyHint: true
- openWorldHint: false
Only reads 1Show 1 read-only tool
find_recipeFind a ready-made automation recipe for a plain-words need, e.g.No findings
Why it is in this group
- The name "find_recipe" says "find": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Find recipe
- readOnlyHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:03 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 4
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (1 irreversible, 3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.usebridgecore.com/: tools/list returned 5 tools to an anonymous client, including inspect_workflow (irreversible), do (write), plan_automation (write), make_n8n_workflow (write)
Findings
Matches of fixed checks, with the text they matched.
The server marks "make_n8n_workflow" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The description's first verb is "generate": a word for a change.
- Warninspect_workflow
The server marks "inspect_workflow" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "inspect_workflow" says "inspect": a word for reading.
- Infodo
The description mentions "credentials".
What this check looks forMatched text
description: "...ver sends the request and never accepts credentials. A 'when …' need or several steps retur..."
The description mentions "credentials".
What this check looks forMatched text
description: "...blanks only the person can fill and the credentials to connect. Shape-checked; the person t..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Install
Pinned to version 0.3.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http bridgecore https://mcp.usebridgecore.com/claude mcp add --transport http bridgecore https://mcp.usebridgecore.com/Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__bridgecore__find_recipe"
],
"ask": [
"mcp__bridgecore__do",
"mcp__bridgecore__plan_automation",
"mcp__bridgecore__make_n8n_workflow",
"mcp__bridgecore__inspect_workflow"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as bridgecore. Review it before you use it.
Capability tags behind 1 rule
- mcp__bridgecore__inspect_workflow untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.chinlee2200-dotcom/bridgecore/verify?hash=236c1493860fd66fbb8f29ccc3e2fbb8716ae4489de63e19770e4194ba8ee1b3" | jq -e '.changed == false'Pinned hash 236c1493860f, from Nov 16, 2026, 13:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.chinlee2200-dotcom/bridgecore/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.chinlee2200-dotcom/bridgecore)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:27 UTC.
bridgecore MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the bridgecore MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 4 of which can change, send or delete something, and 4 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the bridgecore MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the bridgecore MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: inspect_workflow.
What tools does the bridgecore MCP server have?
- 5 tools: 1 irreversible, 3 write, 1 read. inspect_workflow, do, plan_automation, make_n8n_workflow and find_recipe.
Does the bridgecore MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the bridgecore MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the bridgecore MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 16, 2026. Every change is on this page and in its Atom feed.