Skip to main content
Glama
IPGeolocation MCP Server

IPGeolocation MCP Server

Bulk Security Check

bulk_security_check
Read-only

Check security details for up to 250 IPv4 or IPv6 addresses in one request, returning per-IP threat, VPN, proxy, Tor, bot, hosting, and spam data for batch risk review.

Instructions

Read-only bulk security lookup via POST /v3/security-bulk. Paid only. Cost: 2 credits per valid IP. This MCP server accepts up to 250 IPs; private, bogon, and malformed IPs are not billed. Larger batches are rejected before any API call. Complete results within upstream and cache byte limits are returned directly or as cached pages. Cached pages use get_cached_result without another API call or additional credits. An upstream body above its byte limit, or a required pagination snapshot too large to retain, returns a non-retryable resource_limit error with no cursor; the API may already have used credits.

This endpoint is dedicated to security-only batches; bulk_lookup_ip with include=security provides security data together with geolocation or other IP domains. Returns one { ip, security } result per valid IP. fields/excludes accept security.* dot paths per item. force_refresh bypasses cached data, makes a new upstream request, and can consume credits.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ips": "<ips>"
    },
    "name": "bulk_security_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipsYesArray of IPv4 and/or IPv6 addresses to check. Minimum 1, maximum 250 in this MCP server.
fieldsNoComma-separated dot-path fields to return per IP (e.g. security.threat_score,security.is_vpn). Reduces response size.
excludesNoComma-separated dot-path fields to exclude per IP (e.g. security.is_tor,security.is_cloud_provider).
force_refreshNoDefault false. When true, bypasses cached bulk security data; a successful refresh makes a new upstream request and can consume credits.

Output Schema

NameRequiredDescriptionDefault
pageNo
errorNoPresent when the whole tool call fails, with isError: true.
itemsNoPresent on success: complete API results in input order, including any per-item error messages.
errorsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.3
    • removedOutput schema / properties / items / items / additionalProperties / anyOf
      Removed value: -[
      -  {
      -    "type": "null"
      -  },
      -  {
      -    "type": "boolean"
      -  },
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "array"
      -  },
      -  {
      -    "type": "object"
      -  }
      -]
    • addedOutput schema / properties / items / items / additionalProperties / type
      Added value: +[
      +  "null",
      +  "boolean",
      +  "number",
      +  "string",
      +  "array",
      +  "object"
      +]
  2. Addedv2.0.1
  3. Removedv2.0.0
  4. Changed1 schema field changedv1.0.15
    • changedInput schema / properties / force_refresh / description
      Previous value: -"Default false. Leave unset unless the user asks to refresh or rerun."New value: +"Default false. Set true only when the user asks to refresh cached bulk security data; a successful refresh makes a new upstream request and can consume credits."
  5. First observedv1.0.10

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only cover readOnlyHint and openWorldHint; the description adds the substantive behavior an agent actually needs: 2 credits per valid IP, private/bogon/malformed IPs unbilled, pre-flight rejection of oversized batches, cache-page continuation via get_cached_result, and a non-retryable resource_limit error with no cursor where credits may already have been spent. That cost-and-failure disclosure goes well beyond the annotation bar.

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

Conciseness4/5

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

Front-loaded with the endpoint, billing rate, and batch cap, then error and pagination behavior, then sibling routing. Dense and largely waste-free, but the billing and limit facts are split across two sentences and the cache/error passage is packed tightly enough to reward a second read.

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

Completeness5/5

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

An output schema exists, so return values need not be explained, and the description still names the per-IP result shape. Combined with cost, batch limits, cache continuation, and error semantics, nothing an agent needs to invoke this correctly or budget for it is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description still adds the constraint that fields/excludes take security.* dot paths per item, which the schema only illustrates by example. It also reinforces that force_refresh triggers a billable upstream request, though that is largely restated from the schema.

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?

States a specific verb and resource ("read-only bulk security lookup via POST /v3/security-bulk") plus the per-item return shape ({ ip, security }). It explicitly distinguishes itself from the two nearest siblings, bulk_lookup_ip and (implicitly) check_security, so an agent can pick it without opening any schema.

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

Usage Guidelines5/5

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

Gives an explicit routing rule: use this for security-only batches, use bulk_lookup_ip with include=security when geolocation or other IP domains are also needed, and use get_cached_result to page cached results without another API call. It also states a hard when-not (batches above 250 IPs are rejected before any API call).

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