GitHub Meta (BYOK) — connector documentation
- MCP endpoint:
https://byok-github-meta.connectorbay.com/mcp - REST API:
POST https://byok-github-meta.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec athttps://byok-github-meta.connectorbay.com/openapi.json - Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
- Authentication: your own GitHub Meta GitHub personal access token (no scopes needed), sent in the
X-Upstream-Keyheader of every request (never stored, logged or cached) - Health:
https://byok-github-meta.connectorbay.com/health· Tool schemas:https://byok-github-meta.connectorbay.com/tools.json - Publisher: Unify Dynamics LLC · connectorbay.com/byok-github-meta · agent@connectorbay.com
What GitHub Meta (BYOK) is for
GitHub Meta (BYOK) lets an AI assistant read your own GitHub Meta data through the GitHub Meta API with a key you supply (GitHub personal access token (no scopes needed)). Read-only: 6 tools (get_rate_limit_status, get_github_meta, list_licenses, get_license, get_repository_license, list_codes_of_conduct). 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 Meta. GitHub Meta and its logos are trademarks of their owners and are used only to say which service the connector works with.
Ask your assistant things like:
- "How many search and core GitHub API calls do I have left right now?"
- "What IP ranges does GitHub send webhooks from?"
- "Which open source licenses does GitHub offer when creating a repository?"
- "What does the Apache 2.0 license permit and require?"
- "Which license does octocat/Hello-World use?"
- "Which codes of conduct can I add to a GitHub repository?"
What it does
get_rate_limit_status: Show the remaining API calls and reset time of the key for every GitHub rate limit bucket (core, search, code search, GraphQL and others). Reading this does not use up calls.get_github_meta: Get GitHub's published SSH key fingerprints and the IP address ranges (CIDR blocks) used by webhooks, the web, the API, git, pages, importer and package services.list_licenses: List the commonly used open source licenses GitHub knows with key, name and SPDX ID; optionally only the featured ones.get_license: Get one license by its key (for example mit or apache-2.0): description, what it permits, requires and limits, and whether it is featured; the full license text is left out.get_repository_license: Get the license detected for a repository: license key, name, SPDX ID and the license file's path and size.list_codes_of_conduct: List the codes of conduct GitHub offers as templates with key, name and URL; the full text is left out.
BYOK key
You bring your own GitHub Meta GitHub personal access token (no scopes needed) (https://github.com/settings/tokens). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.github.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.
Data sources
- https://docs.github.com/en/rest/meta/meta (the API this connector calls, with a BYOK key)
Live from the GitHub Meta API (api.github.com) with a BYOK key; documentation: https://docs.github.com/en/rest/meta/meta. Endpoints checked against that documentation on 2026-10-16.
What it is not
Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by GitHub Meta. GitHub Meta and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your GitHub Meta account.
Built for: Worldwide. Languages: English.