Malicious URLs MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | API 密钥 |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_urlsC | Get list of all urls with page number |
| searchC | Search by url |
| get_randomB | responds with one random url |
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 3 tools
Each tool has a clearly distinct purpose: get_random retrieves a single random URL, list_urls fetches a paginated list of all URLs, and search allows querying by URL. There is no overlap in functionality, making it easy for an agent to select the right tool.
The tool names follow a consistent verb-based pattern (get_random, list_urls, search), with all using snake_case. However, 'search' deviates slightly by not including a noun, which is a minor inconsistency in an otherwise predictable naming scheme.
With only 3 tools, the server feels thin for handling malicious URLs, as it lacks operations like adding, updating, or deleting URLs, or more advanced analysis features. While the tools cover basic retrieval, the scope seems limited for a domain that might benefit from more comprehensive management.
The tool surface is significantly incomplete for a malicious URL server, as it only provides read operations (random, list, search) with no ability to create, update, delete, or analyze URLs. This leaves obvious gaps in CRUD coverage and limits agents to passive querying without active management capabilities.