# io.github.chinlee2200-dotcom/bridgecore

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

- name: io.github.chinlee2200-dotcom/bridgecore
- version: 0.3.2
- connection class: R0 (autonomous)
- trust: 96/100
- quality: 85/100 (new)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/io.github.chinlee2200-dotcom%2Fbridgecore
- tools: https://api.protogrid.dev/v1/servers/io.github.chinlee2200-dotcom%2Fbridgecore/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

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


## Trust

- hygiene: 100
- liveness: 96
- freshness: 100
- provenance: 90
- drivers: +repository +namespace-matches-repo +website +reachable +uptime-89% +updated-5d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 85/100 (new)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-06-18; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 93 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 5 of 5 tools declare readOnlyHint or destructiveHint
- warn `tools.directory_hints`: 1 of 5 tools declare all four hints; missing: find_recipe (destructiveHint, idempotentHint); plan_automation (destructiveHint, idempotentHint); make_n8n_workflow (destructiveHint, idempotentHint); …
- pass `tools.token_cost`: about 1,320 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: n/a (weight 15)

- n/a `stability.changes`, `stability.rug_pull`: tool history recorded for 6 of the 7 days needed

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 5, about 1,320 tokens to load them all
- tool set hash: dd5451e5a8336deca0a981b83dbb785d
- tools last changed: 2026-10-18T16:34:36.197Z
- badge: [![protogrid quality](https://protogrid.dev/badge/io.github.chinlee2200-dotcom/bridgecore.svg)](https://protogrid.dev/servers/io.github.chinlee2200-dotcom/bridgecore)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-18 `do` changed (description)
  - before: One tool for 3,597 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).
  - after: 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).
- 2026-10-16 `inspect_workflow` added
  - 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.
- 2026-10-15 `make_n8n_workflow` changed (description, inputSchema, outputSchema)
  - before: 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.
  - after: 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.
- 2026-10-15 `plan_automation` changed (outputSchema)
- 2026-10-15 `find_recipe` changed (outputSchema)
- 2026-10-15 `do` changed (outputSchema)
- 2026-10-15 `plan_automation` changed (description)
  - before: 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. Use before building any integration or workflow.
  - after: 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.
- 2026-10-15 `find_recipe` changed (description)
  - before: 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). Use when a person wants to connect apps, automate a workflow, sync tools, or get notified when something happens.
  - after: 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.
- 2026-10-15 `do` changed (title, description, inputSchema, annotations)
  - before: One tool for 3,597 app capabilities (n8n catalog + OpenAPI + MCP): say what should happen; get the exact call or the result. 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 then: dry_run=true (default, safe, free) returns the exact HTTP/MCP request that would be sent, with `missing` naming any input still needed; dry_run=false makes the call and returns the service's reply (`charged` counts successful calls at fee_usd each; failures and missing inputs cost nothing). A 'when …' need or several steps returns the plan: HTTP/MCP steps are called one by one (no data flows between them), n8n-only steps come back as an importable n8n workflow — they run inside n8n, not here. No credentials pass through this server: a capability that needs an API key is called from an Apify Actor run (per-run `auth`), here it only shows the request. Use plan_automation to see alternatives, find_recipe for ready-made flows.
  - after: One tool for 3,597 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).
- 2026-10-14 `make_n8n_workflow` changed (title, inputSchema, outputSchema, annotations)

Full history: https://api.protogrid.dev/v1/servers/io.github.chinlee2200-dotcom%2Fbridgecore/changes

## Remotes

- https://mcp.usebridgecore.com/ (streamable-http, auth none, reachable true, uptime30d 0.8888889)

## Packages

_none_

## Tools (5)

- `do`: 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).
- `find_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.
- `inspect_workflow`: 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.
- `make_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.
- `plan_automation`: 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.
