Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
GitHub Secret Scanning (BYOK) icon

GitHub Secret Scanning (BYOK)

Read GitHub secret scanning alerts across an organization, alert locations, scan history and custom patterns with your own personal access token; secret values are never returned

Unify Dynamics LLC

Tools7read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderGitHub Secret Scanningunofficial, not affiliated
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

Which open secret scanning alerts does octo-org have?
Tools called
list_org_secret_scanning_alerts
Describe secret scanning alert 9 of octocat/Hello-World
Tools called
get_secret_scanning_alert
In which files and commits was secret scanning alert 9 of octocat/Hello-World found?
Tools called
list_alert_locations
When did secret scanning last run on octocat/Hello-World?
Tools called
get_scan_history
Which custom secret patterns does octocat/Hello-World define?
Tools called
list_repo_custom_patterns
Which custom secret patterns does octo-org define?
Tools called
list_org_custom_patterns

About

GitHub Secret Scanning (BYOK) lets an AI assistant read your own GitHub Secret Scanning data through the GitHub Secret Scanning API with a key you supply (GitHub personal access token (security_events scope, or repo scope)). Read-only: 7 tools (list_org_secret_scanning_alerts, get_secret_scanning_alert, list_alert_locations, get_scan_history, list_repo_custom_patterns, list_org_custom_patterns, list_org_pattern_configurations). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.github.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by GitHub Secret Scanning. GitHub Secret Scanning and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the GitHub Secret Scanning API (api.github.com) with a BYOK key; documentation: https://docs.github.com/en/rest/secret-scanning/secret-scanning. Endpoints checked against that documentation on 2026-10-16.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.

What it can do

7 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Read your data7 tools
  • List org secret scanning alertsList secret scanning alerts across an organization with secret type, provider, state, validity and repository; the secret value is never returned.
  • Get secret scanning alertGet one repository secret scanning alert: type, provider, state, resolution, validity, leak flags and push protection bypass; the secret value is…
  • List alert locationsList where a secret scanning alert was found: file path, line and column range, and the commit and blob SHA.
  • Get scan historyGet a repository's secret scanning scan history: incremental, pattern update, backfill and custom pattern scans with status and times.
  • List repo custom patternsList a repository's custom secret scanning patterns with name, state, push protection flag and version; the pattern expressions are left out.
  • List org custom patternsList an organization's custom secret scanning patterns with name, state, push protection flag and version; the pattern expressions are left out.
  • List org pattern configurationsGet an organization's secret scanning pattern configuration: per-provider alert totals, false positive and bypass rates and the push protection…

Information

PublisherUnify Dynamics LLC
CategoryDeveloper tools
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-github-secret-scanning.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide
FunctionOther
LayerDeep connectors

More like this

More in Other

Cloudflare Workers Platform (BYOK)

Read your Cloudflare Workers platform resources: KV namespaces, D1 databases, Queues, Hyperdrive configs, Vectorize indexes, Workflows, custom domains and cron triggers with your own API token

Live · MCP + REST11 tools

Cloudflare Pages (BYOK)

Read your Cloudflare Pages projects, deployments, build logs and custom domains with your own API token

Live · MCP + REST6 tools

Cloudflare Zero Trust (BYOK)

Read your Cloudflare Zero Trust Access applications, policies, groups, identity providers, service tokens, Gateway rules and tunnels with your own API token

Live · MCP + REST9 tools

Twilio Video (BYOK)

Read your Twilio Programmable Video rooms, participants, track recordings, compositions and recording settings with your own credentials (read-only)

Live · MCP + REST9 tools

Twilio Content (BYOK)

Read your Twilio Content Templates (rich messages for WhatsApp, SMS and more) and their approval status with your own credentials (read-only)

Live · MCP + REST5 tools

Twilio Verify (BYOK)

Read your Twilio Verify services, rate limits, webhooks, templates, messaging configuration and verification attempt statistics with your own credentials (read-only; never starts a verification)

Live · MCP + REST9 tools

Get GitHub Secret Scanning (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own GitHub Secret Scanning GitHub personal access token (security_events scope, or repo scope). Create one at https://github.com/settings/tokens, with the fewest permissions it needs (read-only if the provider offers it). Your assistant sends it in the X-Upstream-Key header with every request. It is used for that one call only: never stored, logged or cached, and only ever sent to GitHub Secret Scanning. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with GitHub Secret Scanning.