Impreza Host
Server Details
No-KYC offshore hosting an AI agent self-onboards (no e-mail), funds in crypto, then deploys.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- imprezahost/impreza-mcp
- GitHub Stars
- 0
- Server Listing
- Impreza Host MCP Server
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 1 of 1 tools scored.
With only one tool, there is no ambiguity. The tool's purpose is clearly defined and distinct.
The tool name follows a consistent pattern (impreza_ + verb_noun in snake_case), and there are no other tools to conflict.
The single tool is insufficient for the apparent scope of the server, which includes funding, VPS ordering, and app deployment. The server feels thin.
The server only provides account creation. Critical operations like top-up, VPS management, and app deployment are missing, making the surface severely incomplete.
Available Tools
1 toolimpreza_bootstrap_accountAInspect
Create a brand-new ANONYMOUS Impreza account — no e-mail, no KYC — and get an operating credential in ONE call. Use this when you have no account or token yet. Returns: account_id, api_key + api_secret (REST), a fresh mcp_token (reconnect THIS MCP server with it as the Bearer to unlock the full toolset), and a one-time recovery_code (save it). After bootstrapping, reconnect with the mcp_token, then fund the account in crypto with impreza_topup (BTC/XMR) before ordering a VPS or deploying an app.
| Name | Required | Description | Default |
|---|---|---|---|
| label | No | Optional label for the account/credential (e.g. your agent name). | |
| idempotency_key | No | Optional unique string so a retried call does not create a duplicate account. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses that the account is anonymous (no email/KYC), returns specific credentials (account_id, api_key+secret, mcp_token, recovery_code), and that reconnecting with mcp_token unlocks the full toolset. It implies a one-time creation with idempotency support. Minor gap: does not mention if account creation is reversible or any rate limits.
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 well-structured with the core purpose front-loaded. The additional sentences about follow-up steps are relevant and justified. It could be slightly more concise, but all information serves a purpose.
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?
Given the lack of output schema, the description adequately explains return values and workflow. It covers the bootstrap flow and next steps. Lack of error handling or rate limit information is acceptable for a creation tool of this nature.
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?
Both parameters (label, idempotency_key) are optional and fully documented in the input schema with clear descriptions. The tool description does not add any additional meaning beyond the schema, so it meets the baseline for complete 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 clearly states the tool creates a brand-new anonymous Impreza account and returns credentials in one call. It specifies the verb 'create' and the resource 'anonymous Impreza account', and distinguishes itself as a bootstrap tool for when no account exists.
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 explicitly says 'Use this when you have no account or token yet' and provides a clear workflow: after bootstrapping, reconnect with mcp_token, fund with impreza_topup, then order VPS or app. This tells the agent exactly when to use this tool and what to do next.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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!
Your Connectors
Sign in to create a connector for this server.