Rubiscout Email Analysis MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RUBISCOUT_API_KEY | Yes | Your Rubiscout API key (get one at https://rubiscout.com/dashboard) |
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 |
|---|---|
| analyze_emailA | Analyze an email for phishing, spoofing, and authentication failures. Accepts raw email headers or a full RFC 2822 email (headers + body). Returns a full forensic verdict with SPF/DKIM/DMARC results, IP reputation, routing path, risk score, and recommendations. |
| get_analysisA | Retrieve a previously stored Rubiscout analysis by its UUID. Returns the full analysis result including verdict, risk score, authentication results, IP reputation, and recommendations. |
| list_analysesA | List recent Rubiscout analyses, ordered by most recent first. Optionally filter by risk score. |
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 targets a distinct operation: analyzing a new email, retrieving a specific analysis by UUID, and listing recent analyses. There is no functional overlap.
All tool names follow a consistent verb_noun pattern with lowercase and underscores (analyze_email, get_analysis, list_analyses), making them predictable.
With 3 tools, the server is scoped tightly to email analysis. While minimal, it covers the primary use cases without unnecessary bloat.
The server provides core CRUD-like operations (create, read, list) for email analyses. Missing update and delete are minor gaps, but the essential workflow for analysis is complete.