Email Reputation & Risk Score

omnial/x402-email-reputation-score

Given an email address, returns a 0-100 reputation/trust score plus a risk level, whether the address is syntactically valid with a resolvable domain, the domain and its provider type (e.g. major provider vs. disposable), and the individual factors (with each one's point impact) that produced the score.

activeper callv4

Price

Up to $0.0487 per call; you pay what the call used

You pay the price shown. If a call turns out to cost more than its quote, you pay the actual price, capped at twice the quote. No monthly minimum. Top-ups start at $5.00.

Data source

Public DNS records

Data from public DNS records.

Use it

Your AI assistant does the work: it finds this tool, shows you the price first, runs it, and you are charged when the run finishes. There is nothing to set up for this tool in particular.

Connect once and your AI can find and run this tool, and any other it needs.

Install it Create an account

For developers: the calls your assistant makes

agent

// 1. search: find the tool
omnial_search({ query: "what you need" })

// 2. inspect: price and input schema
omnial_inspect({ tool: "omnial/x402-email-reputation-score" })

// 3. learn: read the usage guide at runtime
omnial_learn({ tool: "omnial/x402-email-reputation-score" })

// 4. run: price the exact call first, then run it
omnial_execute({ tool: "omnial/x402-email-reputation-score", input: { /* see input_schema */ }, dry_run: true })
omnial_execute({ tool: "omnial/x402-email-reputation-score", input: { /* ... */ } })

// 5. settle: the call is charged when it finishes, nothing to do

Not connected yet? Point your MCP client at https://mcp.eden-engine.com/mcp, then copy a config for your client.

Pricing

Every charge this tool can incur.

Charge	Price
Per call	$0.0487

Updated: Nov 6, 2026

Input and output schemas

Input schema

input_schema.json

{
  "type": "object",
  "required": [
    "email"
  ],
  "properties": {
    "email": {
      "type": "string",
      "description": "Email address to score"
    }
  },
  "additionalProperties": false
}

Output schema

output_schema.json

{
  "type": "object",
  "properties": {
    "email": {
      "type": "string",
      "description": "The email address exactly as submitted, echoed back."
    },
    "domain": {
      "type": "string",
      "description": "The domain portion of the submitted email address."
    },
    "factors": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "detail": {
            "type": "string",
            "description": "Human-readable explanation of the signal."
          },
          "factor": {
            "type": "string",
            "description": "Short machine-readable signal name."
          },
          "impact": {
            "type": "number",
            "description": "Point contribution to reputation_score; observed both positive (10, 18) and negative (-40, -10)."
          }
        },
        "additionalProperties": true
      },
      "description": "The individual signals that produced reputation_score, e.g. reputable provider, valid MX records, disposable domain, suspicious local part."
    },
    "risk_level": {
      "type": "string",
      "description": "Observed values: 'low' and 'critical'. Likely also takes intermediate values (e.g. 'medium'/'high') not seen in testing -- treat as an open string, not a fixed two-value enum."
    },
    "email_valid": {
      "type": "boolean",
      "description": "Whether the address is syntactically valid and has a resolvable domain."
    },
    "provider_type": {
      "type": "string",
      "description": "Observed values: 'major_provider' (gmail.com) and 'disposable' (mailinator.com). Other categories are likely but not documented."
    },
    "reputation_score": {
      "type": "number",
      "description": "0-100 trust score. Observed 78 (low risk, gmail.com) and 10 (critical risk, a disposable domain) in testing."
    }
  },
  "description": "The email reputation result.",
  "additionalProperties": true
}