Realurls
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| verify_urlA | Check whether a URL or domain is the verified official website of a software product, AI tool, or company. Returns official | not_official (with the real official domains) | insufficient_evidence | unknown. Judges ownership only, never safety. |
| get_official_urlA | Look up the verified official website for a software product, AI tool, or company by name. Returns verified URLs with the evidence behind them, or says the site could not be confirmed. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct inputs and purposes: verify_url checks a given URL/domain against the official record, while get_official_url retrieves the official URL from a product or company name. No ambiguity exists between them.
Both tool names follow the same verb_noun pattern with snake_case: verify_url and get_official_url. The verbs ('verify', 'get') match the respective actions, creating a predictable and consistent naming convention.
With only two tools, the server feels slightly thin even though both tools cover the core domain of official URL verification and lookup. Each tool earns its place, but the small count leaves little room for broader utility or edge-case coverage.
The two tools cover the entire primary workflow: given a name, look up the official URL; given a candidate URL, verify its official status. There are no obvious gaps for a read-only service focused on official website verification.