Skip to main content
Glama
alberthild

ShieldAPI MCP

shieldapi.check_email

Read-onlyIdempotent

Check if an email address has been exposed in known data breaches via Have I Been Pwned (HIBP) to identify security risks.

Instructions

Check if an email address has been exposed in known data breaches via HIBP.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailYesEmail address to check

Implementation Reference

  • src/index.ts:179-187 (registration)
    The shieldapi.check_email tool is registered dynamically within a loop that iterates over the TOOLS configuration object. The tool handler uses the `callShieldApi` function to fetch data from the ShieldAPI.
    for (const [name, def] of Object.entries(TOOLS)) {
      server.tool(
        name,
        def.description,
        { [def.param]: z.string().describe(def.paramDesc) },
        { ...readOnlyAnnotations, title: TOOL_TITLES[name] || name },
        async (params) => formatResult(await callShieldApi(def.endpoint, params as Record<string, string>))
      );
    }
  • The handler function `callShieldApi` performs the actual API request to the ShieldAPI backend. It handles parameter serialization, demo mode injection, and payment-enabled fetching.
    async function callShieldApi(endpoint: string, params: Record<string, string>): Promise<unknown> {
      const url = new URL(`${SHIELDAPI_URL}/api/${endpoint}`);
      for (const [key, value] of Object.entries(params)) {
        url.searchParams.set(key, value);
      }
      if (demoMode) {
        url.searchParams.set('demo', 'true');
      }
    
      const response = await paymentFetch(url.toString());
      if (!response.ok) {
        const body = await response.text();
        throw new Error(`ShieldAPI ${endpoint} failed (${response.status}): ${body.substring(0, 200)}`);
      }
      return response.json();
    }
  • The schema and configuration for the `shieldapi.check_email` tool, defining the endpoint path and parameter requirements.
      'shieldapi.check_email': {
        description: 'Check if an email address has been exposed in known data breaches via HIBP.',
        param: 'email',
        paramDesc: 'Email address to check',
        endpoint: 'check-email',
      },
    };
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare safety profile (readOnly, non-destructive, idempotent) and external dependency (openWorldHint). The description adds valuable context by specifying 'via HIBP' (Have I Been Pwned), clarifying which external service is queried. It does not contradict annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single 11-word sentence with zero redundancy. Front-loaded with action verb, immediately communicates resource and data source. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple single-parameter input, comprehensive schema coverage, and rich annotations covering safety traits, the description is complete. The mention of HIBP adequately explains the external dependency implied by openWorldHint.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema description coverage ('Email address to check'), the baseline is 3. The description mentions 'email address' but does not add format constraints, validation rules, or semantic details beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses specific verb 'Check' with explicit resource 'email address' and scope 'known data breaches'. It clearly distinguishes from siblings like check_domain, check_ip, and check_password by specifying the exact entity being validated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The specificity of 'email address' implies when to use this tool (when targeting emails vs domains/IPs), but there is no explicit guidance on choosing between this and full_scan or scan_skill for comprehensive checks, nor when-not-to-use advice.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/alberthild/shield-api-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server