Profullstack

NicheDB: IP and Domain Reputation

nichedb_reputation_lookup

Read-onlyIdempotent

[NicheDB] Is an IP address or a domain on a blocklist? Give indicator (an IPv4/IPv6 address or a domain; a URL is reduced to its host). Answers listed, a rough 0-100 score with the reasons behind it, the nichedb /traffic record (addresses our own servers banned and a person approved), the abuse.ch indicators (ThreatFox, URLhaus, Feodo Tracker; a domain is checked with its parent domains), the SURBL standing of a watched domain, and live DNS blocklists in dnsbl (an address: Spamhaus ZEN with SBL/CSS/XBL/PBL decoded, SpamCop, PSBL, Mailspike; a domain and its parents: Spamhaus DBL, URIBL, SURBL). A domain is also resolved and each A/AAAA address is checked the same way, in addresses (each with ip, listed, traffic, indicators, dnsbl). A list whose own test entry failed is named in unknown, not treated as a miss. Not listed is not the same as clean.

Served by NicheDB (https://nichedb.dev/docs/mcp).

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": {
      "indicator": "<indicator>"
    },
    "name": "nichedb_reputation_lookup"
  }
}

Input Schema

Name	Required	Description	Default
`indicator`	Yes	An IP address or a domain, e.g. 203.0.113.9 or evil.example

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the annotations, the description explains returned fields, checks against nichedb traffic records, abuse.ch sources, SURBL, and live DNSBLs, including special handling for domains and their parent domains. It also discloses important caveats such as failed test entries appearing in `unknown` and 'not listed' not meaning 'clean'.

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?

The description is front-loaded with the core question and has no filler sentences, but it is dense and packs many source and output details into one paragraph. The density is defensible because there is no output schema, though it could be easier to scan with structure.

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?

For a one-parameter lookup tool with no output schema, the description covers input handling, returned fields, DNSBL sources, domain resolution behavior, failure handling, and an important interpretation caveat. It gives an agent enough context to invoke and interpret the tool correctly.

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?

The schema already documents the single `indicator` parameter, but the description adds meaningful semantics: it accepts IPv4/IPv6 or a domain, and URLs are reduced to their host. That goes beyond the schema examples and helps the agent format inputs correctly.

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 opens with a specific verb and resource: checking whether an IP address or domain is on a blocklist. It clearly frames the tool as a reputation/blocklist lookup rather than a generic domain or IP lookup, so an agent can identify its role immediately.

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?

Usage is implied by the blocklist-reputation framing, but the description does not explicitly say when to use this instead of siblings such as nichedb_check_domain or profullstack_bulk_domain_check. There are no stated exclusions or alternative-selection rules.

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

All Profullstack tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?