ByteRay AI
Server Details
Hunt zero-days by talking to binaries. 40+ tools. Hosted, OAuth + SSO, invite: hi@byteray.ai
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 3.8/5 across 43 of 43 tools scored. Lowest: 3.1/5.
The tool set has clear distinct purposes for most tools, but there is notable overlap in some areas. For example, 'get_references_from' and 'get_references_to' are distinct, but 'get_call_tree', 'what_calls', and 'who_calls' all relate to call relationships and could cause confusion. Similarly, 'read_assembly', 'read_pseudocode', 'read_lifted_il', and 'read_ssa_form' all provide code views with subtle differences that might be hard for an agent to distinguish without deep domain knowledge.
Tool names follow a consistent verb_noun pattern with minor deviations. Most tools use clear verbs like 'get_', 'list_', 'read_', 'trace_', etc., but there are a few inconsistencies such as 'ask_ai' (verb_abbreviation), 'goto_address' (verb_noun but 'goto' is less common), and 'navigate_cfg' (verb_abbreviation). Overall, the naming is predictable and readable, with only slight variations.
With 43 tools, the count is excessive for a reverse engineering server, leading to potential overwhelm and redundancy. While the domain is complex, many tools could be consolidated (e.g., multiple code view tools or call analysis tools) without losing functionality. This high number may hinder agent usability and efficiency in selecting the right tool.
The tool set provides comprehensive coverage for binary analysis, including loading binaries (upload, fetch, open), navigation (goto, inspect), code examination (assembly, pseudocode, CFG), data flow (trace, SSA), vulnerability detection (attack surface, sanitization), and utility functions (hashes, strings). There are no obvious gaps; it supports full CRUD-like operations and advanced analysis workflows in the domain.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!