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

Identity check: sanctions, email, phone and IP in one call

hubvibe_identity_check

Read-onlyIdempotent

KYC screening / identity risk check in one call: a name screened against OFAC, UK and EU sanctions; an email's mailbox, disposable and role checks; a phone's validity, country and line type; an IP's country and network. Returns each result, fraud flags (sanctions hit, disposable email, VoIP, countries that disagree) and one risk level: low, review or high. Use it before onboarding a user or counterparty. Input: any of name, email, phone, ip; optional country, birth_year. $0.10 per call. Returns: input{}, risk (low | review | high), flags[{code, severity, detail}], checks{sanctions, email, phone, ip}, checks_run[], checks_failed[], notes[], checked_at.

Input Schema

TableJSON Schema

Name	Required	Description
`ip`	No	The client's IPv4 or IPv6 address.
`name`	No	Person or company name to screen against sanctions lists.
`email`	No	Email address to verify.
`phone`	No	Phone number, international (+44 20 7946 0958) or national with `phone_region`.
`country`	No	Country the person says they are in (US or United States), compared with phone and IP.
`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.
`birth_year`	No	Birth year, to narrow sanctions matches for a person.
`phone_region`	No	Two-letter country for a national-format phone number.

Output Schema

TableJSON 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: -{
-  "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"
-  },
-  "checks": {
-    "description": "Each check's result; null when not asked for or failed.",
-    "properties": {
-      "email": {
-        "description": "email.verify result (verdict, reason, disposable, role_account, free_provider, did_you_mean...), or null.",
-        "properties": {
-          "reason": {
-            "description": "Why.",
-            "examples": [
-              "mailbox_exists"
-            ],
-            "type": "string"
-          },
-          "verdict": {
-            "description": "email.verify verdict.",
-            "examples": [
-              "deliverable"
-            ],
-            "type": "string"
-          }
-        },
-        "required": [
-          "verdict",
-          "reason"
-        ],
-        "type": [
-          "object",
-          "null"
-        ]
-      },
-      "ip": {
-        "description": "ip.lookup result (scope, location, network, reverse_dns, attribution), or null.",
-        "properties": {
-          "scope": {
-            "description": "public, private, reserved...",
-            "examples": [
-              "public"
-            ],
-            "type": "string"
-          }
-        },
-        "required": [
-          "scope"
-        ],
-        "type": [
-          "object",
-          "null"
-        ]
-      },
-      "phone": {
-        "description": "phone.parse result (valid, e164, country, region, carrier, line_type), or null.",
-        "properties": {
-          "line_type": {
-            "description": "Line type.",
-            "examples": [
-              "fixed_line"
-            ],
-            "type": "string"
-          },
-          "valid": {
-            "description": "Valid number.",
-            "examples": [
-              true
-            ],
-            "type": "boolean"
-          }
-        },
-        "required": [
-          "valid",
-          "line_type"
-        ],
-        "type": [
-          "object",
-          "null"
-        ]
-      },
-      "sanctions": {
-        "description": "sanctions.screen result (verdict, match_count, matches[], lists[]), or null.",
-        "properties": {
-          "match_count": {
-            "description": "Matches.",
-            "examples": [
-              0
-            ],
-            "type": "integer"
-          },
-          "verdict": {
-            "description": "Screen verdict.",
-            "enum": [
-              "potential_match",
-              "no_match",
-              "incomplete"
-            ],
-            "examples": [
-              "no_match"
-            ],
-            "type": "string"
-          }
-        },
-        "required": [
-          "verdict",
-          "match_count"
-        ],
-        "type": [
-          "object",
-          "null"
-        ]
-      }
-    },
-    "required": [
-      "sanctions",
-      "email",
-      "phone",
-      "ip"
-    ],
-    "type": "object"
-  },
-  "checks_failed": {
-    "description": "Checks that failed; the rest still ship.",
-    "examples": [
-      []
-    ],
-    "items": {
-      "description": "A check that did not complete.",
-      "examples": [
-        "email"
-      ],
-      "type": "string"
-    },
-    "type": "array"
-  },
-  "checks_run": {
-    "description": "Checks that completed.",
-    "examples": [
-      [
-        "sanctions",
-        "email"
-      ]
-    ],
-    "items": {
-      "description": "A check that completed.",
-      "examples": [
-        "sanctions"
-      ],
-      "type": "string"
-    },
-    "type": "array"
-  },
-  "flags": {
-    "description": "Everything worth a look, most severe first.",
-    "examples": [
-      []
-    ],
-    "items": {
-      "properties": {
-        "code": {
-          "description": "Flag code.",
-          "examples": [
-            "country_mismatch_ip"
-          ],
-          "type": "string"
-        },
-        "detail": {
-          "description": "What was found.",
-          "examples": [
-            "Stated country GB but the ip is in United States."
-          ],
-          "type": "string"
-        },
-        "severity": {
-          "description": "How much it matters.",
-          "enum": [
-            "high",
-            "medium",
-            "low"
-          ],
-          "examples": [
-            "low"
-          ],
-          "type": "string"
-        }
-      },
-      "required": [
-        "code",
-        "severity",
-        "detail"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  },
-  "input": {
-    "description": "What was checked.",
-    "properties": {
-      "birth_year": {
-        "description": "Birth year given.",
-        "examples": [
-          1980
-        ],
-        "type": [
-          "integer",
-          "null"
-        ]
-      },
-      "country": {
-        "description": "Stated country.",
-        "examples": [
-          "GB"
-        ],
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "email": {
-        "description": "Email checked.",
-        "examples": [
-          "jane@stripe.com"
-        ],
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "ip": {
-        "description": "IP checked.",
-        "examples": [
-          "8.8.8.8"
-        ],
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "name": {
-        "description": "Name screened.",
-        "examples": [
-          "Jane Smith"
-        ],
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "phone": {
-        "description": "Phone checked.",
-        "examples": [
-          "+44 20 7031 3000"
-        ],
-        "type": [
-          "string",
-          "null"
-        ]
-      }
-    },
-    "required": [
-      "name",
-      "email",
-      "phone",
-      "ip",
-      "country",
-      "birth_year"
-    ],
-    "type": "object"
-  },
-  "notes": {
-    "description": "Notes.",
-    "examples": [
-      []
-    ],
-    "items": {
-      "description": "A note.",
-      "examples": [
-        "Flags are leads to review, not a determination."
-      ],
-      "type": "string"
-    },
-    "type": "array"
-  },
-  "risk": {
-    "description": "high: a high-severity flag (sanctions match). review: a medium flag. low: none or only low flags.",
-    "enum": [
-      "low",
-      "review",
-      "high"
-    ],
-    "examples": [
-      "review"
-    ],
-    "type": "string"
-  }
-}

removedOutput schema / properties / result / required

Removed value: -[
-  "input",
-  "risk",
-  "flags",
-  "checks",
-  "checks_run",
-  "checks_failed",
-  "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: -"identity.check response"

AddedSep 28, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, non-destructive, openWorld), so the bar is lower. The description adds genuinely useful context beyond that: the $0.10 per-call cost, the meaning of the fraud flags (sanctions hit, disposable email, VoIP, country disagreement), and the risk-level semantics. It does not mention auth or rate limits, keeping it short of a 5.

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 core purpose and use case, and information-dense. However, the return content is stated twice — once in prose ('Returns each result, fraud flags...') and again as a structured 'Returns: input{}, risk...' block — which is redundant, especially since an output schema exists.

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 complex multi-check aggregator, the description covers inputs, the anyOf constraint, cost, use case, flag semantics and risk levels. With an output schema also present, an agent has everything needed to select and invoke it correctly.

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 schema already documents all 8 parameters in detail. The description summarizes the key inputs ('any of name, email, phone, ip; optional country, birth_year') and conveys the anyOf requirement, but omits language and phone_region and adds no syntax the schema lacks. Baseline 3 is appropriate.

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 clear verb+resource (KYC screening / identity risk check) and enumerates exactly what is screened for each input type (OFAC/UK/EU sanctions, mailbox/disposable/role email checks, phone validity/country/line type, IP country/network). This lets an agent distinguish it from the narrower siblings hubvibe_sanctions_screen, hubvibe_email_verify, hubvibe_phone_parse and hubvibe_ip_lookup, which each cover only one facet.

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

Usage Guidelines4/5

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

Gives a concrete usage context ('Use it before onboarding a user or counterparty'), which is actionable. It does not, however, state when NOT to use it or explicitly route the agent to the single-purpose siblings when only one check is needed, so the routing guidance is implied rather than explicit.

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.