HubVibe: Pay-per-Call Agent Tools: Web Search, Email Verify, KYC Screening, Stocks, Crypto, News

IP address lookup: location, network owner, reverse DNS

hubvibe_ip_lookup

Read-onlyIdempotent

IP geolocation / IP address lookup: city, region, country and coordinates, the network's ASN and organisation, reverse DNS, and whether the address is public, private or reserved. IPv4 and IPv6. Location data from DB-IP Lite (CC BY 4.0, credited), updated monthly; location is the network's registered place, never a street address. Input: ip. $0.10 per call. Returns: ip, version, scope, reverse_dns[], location{city, region, country, country_code, continent, latitude, longitude}, network{asn, organization}, database_month, attribution{text, url, license}, notes[], checked_at.

Input Schema

Name	Required	Description	Default
`ip`	Yes	One IPv4 or IPv6 address, such as 8.8.8.8.
`language`	No	Optional BCP-47 language tag (en, ja, ko, pt-BR): the human-readable strings of the result (notes, details, reasons) are translated into this language; data, codes, numbers and URLs are untouched. Default: as produced.

Output Schema

Name	Required	Description	Default
`result`	Yes
`status`	Yes
`worker`	Yes
`price_usd`	Yes
`provenance`	Yes
`receipt_id`	Yes
`attribution`	No
`receipt_url`	Yes
`billing_warning`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed23 schema fields changedOct 1, 2026

removedOutput schema / description

Removed value: -"The 200 body of every paid /work call. `result` is the worker's own output (its schema is per route); everything else is the same on every /work route. A receipt for the job is at `receipt_url`."

removedOutput schema / properties / attribution / description

Removed value: -"Present only when the result's text was machine-translated: the credit to show with it."

removedOutput schema / properties / attribution / items / description
```
Removed value: -"A credit."
```

removedOutput schema / properties / attribution / items / properties

Removed value: -{
-  "text": {
-    "description": "Credit.",
-    "examples": [
-      "Translated by Google"
-    ],
-    "type": "string"
-  },
-  "url": {
-    "description": "Link.",
-    "examples": [
-      "https://translate.google.com"
-    ],
-    "type": "string"
-  }
-}

removedOutput schema / properties / attribution / items / required
```
Removed value: -[
-  "text",
-  "url"
-]
```
removedOutput schema / properties / attribution / items / type
```
Removed value: -"object"
```

removedOutput schema / properties / billing_warning / description

Removed value: -"Present only when the charge was recorded with a caveat."

removedOutput schema / properties / billing_warning / examples
```
Removed value: -[
-  "settlement pending"
-]
```
removedOutput schema / properties / price_usd / description
```
Removed value: -"What this call cost, in USD."
```
removedOutput schema / properties / price_usd / examples
```
Removed value: -[
-  0.02
-]
```

removedOutput schema / properties / provenance / description

Removed value: -"How the result was produced: which providers ran and how long each took."

removedOutput schema / properties / provenance / properties

Removed value: -{
-  "attempts": {
-    "description": "Provider attempts made, including retries and failovers.",
-    "examples": [
-      1
-    ],
-    "type": "integer"
-  },
-  "elapsed_ms": {
-    "description": "Wall-clock milliseconds for the whole job.",
-    "examples": [
-      340
-    ],
-    "type": "integer"
-  },
-  "providers_used": {
-    "description": "Providers that served the job.",
-    "examples": [
-      [
-        "coinbase-advanced-trade-public"
-      ]
-    ],
-    "items": {
-      "description": "Provider name.",
-      "examples": [
-        "coinbase-advanced-trade-public"
-      ],
-      "type": "string"
-    },
-    "type": "array"
-  },
-  "steps": {
-    "description": "Every step the job ran, in order.",
-    "items": {
-      "description": "One step of the job.",
-      "properties": {
-        "ms": {
-          "description": "Milliseconds the step took.",
-          "examples": [
-            312
-          ],
-          "type": "integer"
-        },
-        "ok": {
-          "description": "Whether the step succeeded.",
-          "examples": [
-            true
-          ],
-          "type": "boolean"
-        },
-        "provider": {
-          "description": "Provider that served the step.",
-          "examples": [
-            "coinbase-advanced-trade-public"
-          ],
-          "type": "string"
-        },
-        "reason": {
-          "description": "Failure reason, on a failed step.",
-          "examples": [
-            "provider_timeout"
-          ],
-          "type": "string"
-        },
-        "step": {
-          "description": "Step name inside the worker.",
-          "examples": [
-            "quote"
-          ],
-          "type": "string"
-        }
-      },
-      "required": [
-        "step",
-        "ok",
-        "ms"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  }
-}

removedOutput schema / properties / provenance / required

Removed value: -[
-  "steps",
-  "providers_used",
-  "attempts",
-  "elapsed_ms"
-]

removedOutput schema / properties / receipt_id / description
```
Removed value: -"Receipt id for this job."
```
removedOutput schema / properties / receipt_id / examples
```
Removed value: -[
-  "rcpt_9f1c2b3a4d5e6f70"
-]
```

removedOutput schema / properties / receipt_url / description

Removed value: -"Where to fetch the machine-readable receipt (free, no payment)."

removedOutput schema / properties / receipt_url / examples

Removed value: -[
-  "/work/receipts/rcpt_9f1c2b3a4d5e6f70"
-]

removedOutput schema / properties / result / properties

Removed value: -{
-  "attribution": {
-    "description": "Data credit.",
-    "properties": {
-      "license": {
-        "description": "Data licence.",
-        "examples": [
-          "Creative Commons Attribution 4.0 International"
-        ],
-        "type": "string"
-      },
-      "text": {
-        "description": "Credit required by the licence.",
-        "examples": [
-          "IP Geolocation by DB-IP"
-        ],
-        "type": "string"
-      },
-      "url": {
-        "description": "Credit link.",
-        "examples": [
-          "https://db-ip.com"
-        ],
-        "type": "string"
-      }
-    },
-    "required": [
-      "text",
-      "url",
-      "license"
-    ],
-    "type": "object"
-  },
-  "checked_at": {
-    "description": "When this node read the source (UTC). Nothing here is cached.",
-    "examples": [
-      "2026-09-26T18:00:00Z"
-    ],
-    "format": "date-time",
-    "type": "string"
-  },
-  "database_month": {
-    "description": "DB-IP Lite edition used (YYYY-MM).",
-    "examples": [
-      "2026-09"
-    ],
-    "type": [
-      "string",
-      "null"
-    ]
-  },
-  "ip": {
-    "description": "The address, normalised.",
-    "examples": [
-      "8.8.8.8"
-    ],
-    "type": "string"
-  },
-  "location": {
-    "description": "Registered location; null for a non-public or unknown address.",
-    "properties": {
-      "city": {
-        "description": "City.",
-        "examples": [
-          "Mountain View"
-        ],
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "continent": {
-        "description": "Continent.",
-        "examples": [
-          "North America"
-        ],
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "country": {
-        "description": "Country.",
-        "examples": [
-          "United States"
-        ],
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "country_code": {
-        "description": "ISO code.",
-        "examples": [
-          "US"
-        ],
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "latitude": {
-        "description": "Latitude.",
-        "examples": [
-          37.422
-        ],
-        "type": [
-          "number",
-          "null"
-        ]
-      },
-      "longitude": {
-        "description": "Longitude.",
-        "examples": [
-          -122.085
-        ],
-        "type": [
-          "number",
-          "null"
-        ]
-      },
-      "region": {
-        "description": "Region or state.",
-        "examples": [
-          "California"
-        ],
-        "type": [
-          "string",
-          "null"
-        ]
-      }
-    },
-    "required": [
-      "city",
-      "region",
-      "country",
-      "country_code",
-      "continent",
-      "latitude",
-      "longitude"
-    ],
-    "type": [
-      "object",
-      "null"
-    ]
-  },
-  "network": {
-    "description": "Who runs the network; null when unknown.",
-    "properties": {
-      "asn": {
-        "description": "Autonomous system number.",
-        "examples": [
-          15169
-        ],
-        "type": [
-          "integer",
-          "null"
-        ]
-      },
-      "organization": {
-        "description": "Network operator.",
-        "examples": [
-          "Google LLC"
-        ],
-        "type": [
-          "string",
-          "null"
-        ]
-      }
-    },
-    "required": [
-      "asn",
-      "organization"
-    ],
-    "type": [
-      "object",
-      "null"
-    ]
-  },
-  "notes": {
-    "description": "Caveats.",
-    "examples": [
-      []
-    ],
-    "items": {
-      "description": "A caveat.",
-      "examples": [
-        "IP location is approximate."
-      ],
-      "type": "string"
-    },
-    "type": "array"
-  },
-  "reverse_dns": {
-    "description": "Reverse DNS names.",
-    "examples": [
-      [
-        "dns.google"
-      ]
-    ],
-    "items": {
-      "description": "A PTR name.",
-      "examples": [
-        "dns.google"
-      ],
-      "type": "string"
-    },
-    "type": "array"
-  },
-  "scope": {
-    "description": "public addresses are looked up; others are described from the address alone.",
-    "enum": [
-      "public",
-      "private",
-      "loopback",
-      "link_local",
-      "multicast",
-      "shared",
-      "reserved"
-    ],
-    "examples": [
-      "public"
-    ],
-    "type": "string"
-  },
-  "version": {
-    "description": "4 or 6.",
-    "examples": [
-      4
-    ],
-    "type": "integer"
-  }
-}

removedOutput schema / properties / result / required

Removed value: -[
-  "ip",
-  "version",
-  "scope",
-  "reverse_dns",
-  "location",
-  "network",
-  "database_month",
-  "attribution",
-  "notes",
-  "checked_at"
-]

removedOutput schema / properties / status / description

Removed value: -"Present only on a delivered result."

removedOutput schema / properties / worker / description

Removed value: -"Catalog name of the worker that ran."

removedOutput schema / properties / worker / examples
```
Removed value: -[
-  "market.quote"
-]
```
removedOutput schema / title
```
Removed value: -"ip.lookup response"
```

AddedSep 28, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, openWorld), yet the description adds genuinely new behavioral facts: cost of $0.10 per call, data provenance and license (DB-IP Lite, CC BY 4.0, monthly refresh), and an important accuracy caveat that location is the network's registered place and never a street address. These are exactly the kind of traits an agent cannot get from structured fields.

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 capability statement, then pricing, provenance, and a long returns manifest. The returns list is largely redundant because an output schema exists, which costs it some efficiency, but no sentence is filler in the sense of being off-topic.

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 single-address lookup with full schema coverage and an output schema, the description supplies everything an agent still needs to decide and call correctly: scope (IPv4/IPv6), cost, data source and freshness, and the street-address limitation. Nothing material is missing.

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?

Schema description coverage is 100%, so the baseline is 3. The description says only 'Input: ip', repeating the required parameter and omitting the optional 'language' parameter entirely, so it adds essentially nothing beyond the schema and slightly understates the actual input surface.

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 ('IP geolocation / IP address lookup') and enumerates exactly what is returned: geolocation, ASN/organisation, reverse DNS, and public/private/reserved scope, for both IPv4 and IPv6. This is clearly distinguishable from siblings like hubvibe_domain_dns or hubvibe_identity_check without opening the schema.

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 strongly implied by the precision of the purpose statement, but there is no explicit when-to-use/when-not guidance and no routing to alternatives (e.g., 'for a hostname rather than an IP, use hubvibe_domain_dns'). The agent must infer the selection criteria.

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

All HubVibe: Pay-per-Call Agent Tools: Web Search, Email Verify, KYC Screening, Stocks, Crypto, News 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.