Pay-per-call safety checks for AI agents: screen a crypto address or URL before you transact.
Check whether a crypto address is safe to transact with. Screens OFAC sanctions + community scam lists and flags contract-vs-wallet. Returns verdict (safe/caution/avoid), 0-100 risk score, reasons, and sources.
| Name | Required | Description | Default |
|---|---|---|---|
| chain | No | base | ethereum (default: base) | |
| address | Yes | EVM 0x… address to check |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, and the description adds meaningful behavioral context: it screens specific list types, flags contract-vs-wallet, and returns a structured verdict with risk score, reasons, and sources. This goes beyond the annotations to clarify what the tool does and what output the agent can expect.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is three sentences, front-loaded with the main purpose, and every sentence adds value: what it does, what it screens, and what it returns. No redundant or filler content.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has only 2 parameters and no output schema, so the description's inclusion of the return format (verdict, risk score, reasons, sources) is helpful. Minor gap: the description says 'crypto address' while the schema specifies 'EVM 0x…', which could cause slight ambiguity for non-EVM addresses, but overall the description is sufficient for a read-only check tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so both parameters (chain and address) are already documented in the schema. The description does not add extra detail about the parameters themselves; it focuses on high-level behavior. Baseline 3 is appropriate given full schema coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description has a specific verb ('Check'), clear resource ('crypto address'), and a clear goal ('safe to transact with'). It distinguishes from sibling check_url by focusing on crypto addresses rather than URLs.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context for when to use the tool: checking crypto address safety. It mentions the screening criteria (OFAC sanctions, scam lists, contract-vs-wallet) but does not explicitly state when NOT to use it or how it compares to check_url.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Check whether a URL or domain is a scam/phishing site. Screens the MetaMask crypto-phishing blocklist, domain age (RDAP), and lexical red flags. Returns verdict (safe/caution/avoid), 0-100 risk score, reasons, and sources.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | URL or domain to check |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint and openWorldHint, so the agent knows it's a safe read operation. The description adds value by revealing the screening sources (MetaMask blocklist, RDAP domain age, lexical flags) and return fields (verdict, risk score, reasons, sources), providing useful behavioral context beyond the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loaded with purpose, and includes all key details without redundant wording. It efficiently conveys the tool's function, method, and output.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description fully covers what the tool does and what it returns (verdict, risk score, reasons, sources). Given the simple single-parameter schema and no output schema, this is complete and sufficient for an agent to invoke correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with the parameter 'url' described as 'URL or domain to check'. The description adds nothing new about the parameter beyond what the schema already states, so baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool checks if a URL or domain is a scam/phishing site, specifying the verb 'Check' and the resource 'URL or domain'. It also distinguishes itself from the sibling 'check_address' by focusing on URLs/domains rather than addresses.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for URL/domain safety checks but does not explicitly mention alternatives or when not to use it. With a sibling tool 'check_address', the lack of explicit differentiation or usage guidance is a minor gap, though context is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user or an account that owns the GitHub organization, then choose Claim with GitHub.
HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
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
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
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.
No comments yet. Be the first to start the discussion!
Pay-per-call cybersecurity for AI agents: vuln scans, threat intel, compliance, code security.
DeFi safety layer for AI agents: wallet safety, token risk, tx decode/simulate. 20 tools.
Pay-per-call safety guards for AI agents: injection, tool-call, signing, secret, x402-trust.
Deterministic runtime safety for AI agents: scan PII, gate tool actions, verify LLM output.
Add one secure layer between your agents and this server.
Each tool targets a distinct input type: crypto address vs. URL/domain. There is no overlap in purpose, so an agent can easily select the correct tool based on what it needs to check.
Both tools follow the same check_<object> pattern, making the naming predictable and consistent. There are no deviations or mixed conventions.
With only 2 tools, the server feels thin, though the scope is narrow and both tools are directly relevant. The count is borderline but not unreasonable for a specialized security checking utility.
The server covers the two core security checks expected from its purpose (address and URL). There are no obvious dead ends, though a fuller security suite might add checks for transactions or other asset types.
