ByteRay AI
ai.byterayPublished by byteray.aiOfficial publisherv1.1.0Updated Oct 24, 2026
Hunt zero-days by talking to binaries. 40+ tools. Hosted, OAuth + SSO, invite: [email protected]
Overview
A hosted MCP server that lets an assistant hunt zero-days by talking to binaries, with over 40 tools.
- What you can do
- ByteRay AI is a remote MCP server reached over streamable HTTP. According to its description, it lets an assistant hunt zero-days by talking to binaries and exposes more than 40 tools. The manifest does not list the individual tools, so the exact operations are not documented here. Access is hosted and requires OAuth sign-in, with SSO mentioned.
- When to use it
- Consider it when you want an assistant to assist with binary analysis and vulnerability research, such as zero-day hunting, through a hosted service rather than local tooling. It is less relevant if you need documented tool names or offline operation.
- Requirements
- A remote MCP client that supports streamable HTTP, pointed at the provider's hosted endpoint. OAuth authentication is required, and the description mentions SSO. No environment variables, headers, or packages are declared. The description gives an email address for invitations, suggesting access may be gated.
Installation
In SourceWeft
- Open ByteRay AI in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/ai.byteray%2Fbyteray-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"byteray-ai": {
"type": "http",
"url": "https://mcp.byteray.ai/mcp"
}
}
}Tools
0Version history
1- v1.1.0LatestSep 16, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.