yultrace-audit
Server Details
EVM audit (Slither + source + security.txt + MCP-probe + wallet-exposure). 6 tools + /trace.
- 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 4.3/5 across 6 of 6 tools scored. Lowest: 3.3/5.
Each tool has a clearly distinct purpose with no overlap: contract auditing, wallet exposure checking, source code fetching, security contact listing, endpoint probing, and chain support listing. The descriptions reinforce unique domains (security auditing, wallet analysis, source retrieval, contact discovery, server testing, and configuration).
Tools follow a consistent verb_noun pattern (e.g., audit_contract, check_my_wallet_exposure, fetch_contract_source) with one minor deviation: 'supported_chains' uses an adjective_noun form instead of a verb. This small inconsistency doesn't hinder readability but prevents a perfect score.
Six tools is well-scoped for a security auditing server, covering core areas like contract analysis, wallet safety, source access, contact information, endpoint validation, and configuration. Each tool earns its place without bloat or thin coverage.
The toolset provides strong coverage for security auditing workflows, including analysis, exposure checks, and disclosure contacts. A minor gap exists in lacking tools for updating or managing findings (e.g., a tool to track audit results over time), but agents can work around this with existing tools.
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!