DataImpulse MCP Proxy
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DI_PASS | Yes | Your DataImpulse password. | |
| DI_USER | Yes | Your DataImpulse username. |
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 |
|---|---|
| fetch_pageC | Fetch a public HTTP(S) page through a DataImpulse residential proxy. |
| check_exit_ipB | Return the public IP assigned by the current DataImpulse proxy targeting. |
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 completely distinct purposes: one fetches a page through the proxy, the other reports the proxy's exit IP. There is no overlap or ambiguity between them.
Both tool names follow a consistent verb_noun pattern: 'fetch_page' and 'check_exit_ip'. This makes the API predictable and easy to learn.
With only 2 tools, the server feels slightly thin for a typical MCP server, but the scope is narrow and focused on basic proxy operations. The count is borderline but not excessive.
The server covers the essential proxy workflow: fetching a page and verifying the proxy IP. Minor gaps exist, such as no session management or request customization, but the core purpose is adequately served.