Flipvo: licenses, entities, NPI, OFAC and OIG screens, carriers, OSHA, drive times

license_verify

Read-only

$0.02 per call. Pay with x402 (USDC on Base) in _meta["x402/payment"]; MPP (tempo) on the HTTP URL /v1/license/verify. Contractor license status plus matching business-entity record. GET /v1/license/states (free) lists each served state, its source, and whether its entity is ever filled: entity is null where the state has no free registry. Some states also take profession; values at GET /v1/license/professions?state=. Empty licenses is a paid 200.

Input Schema

Name	Required	Description
`name`	No
`state`	Yes
`profession`	No	FL or TX only: a licensed profession instead of a contractor. GET /v1/license/professions?state=FL\|TX (free) lists them. Omit for contractors.
`license_number`	No

Output Schema

Name	Required	Description	Default
`query`	Yes
`state`	Yes
`licenses`	Yes
`data_as_of`	Yes
`attribution`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 30, 2026

changedInput schema / properties / profession / description

Previous value: -"FL only: a licensed profession instead of a contractor. GET /v1/license/professions (free) lists them. Omit for contractors."New value: +"FL or TX only: a licensed profession instead of a contractor. GET /v1/license/professions?state=FL|TX (free) lists them. Omit for contractors."

Changed1 schema field changedSep 29, 2026

addedInput schema / properties / profession

Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 32,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "FL only: a licensed profession instead of a contractor. GET /v1/license/professions (free) lists them. Omit for contractors.",
+  "title": "Profession"
+}

Changed1 schema field changedSep 28, 2026

addedOutput schema / $defs / LicenseOut / properties / name_match

Added value: +{
+  "anyOf": [
+    {
+      "const": "initials_ignored",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "initials_ignored: the name matched only with single-letter initials dropped from both names, tried when nothing matched exactly. A candidate, not a confirmation. Absent on an exact or number match.",
+  "title": "Name Match"
+}

Changed6 schema fields changedSep 27, 2026
- addedOutput schema / $defs / LicenseOut / properties / city / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / $defs / LicenseOut / properties / city / type
```
Removed value: -"string"
```
- addedOutput schema / $defs / LicenseOut / properties / state / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / $defs / LicenseOut / properties / state / type
```
Removed value: -"string"
```
- addedOutput schema / $defs / LicenseOut / properties / zip / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / $defs / LicenseOut / properties / zip / type
```
Removed value: -"string"
```

Changed1 schema field changedSep 27, 2026

changedInput schema / description

Previous value: -"Every input rule lives here, so an invalid body is refused before the 402 (#118)."New value: +"A two-letter state and either license_number or name."

First observedSep 24, 2026

TDQS

A4/5.0

Behavior5/5

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

Despite annotations (readOnly, openWorld), the description adds genuinely non-obvious behavior: a $0.02 per-call price, the payment mechanism (x402 USDC on Base via _meta["x402/payment"], MPP on the HTTP URL), and the crucial billing nuance that 'Empty licenses is a paid 200' — the call costs money even on zero results. It also explains that entity is null where a state has no free registry, preventing the agent from misreading an empty field as a data error.

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 cost, which is the highest-stakes fact, then payment, then result semantics. Every sentence carries information, though the telegraphic style ('Some states also take `profession`; values at ...') is dense enough that an agent must parse fragments.

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?

An output schema exists, so return-shape explanation is unnecessary, and the description instead covers the things structure cannot: price, payment channel, empty-result billing, and entity-null cases. What is missing is any mention of error/permission behavior on unpaid calls and no routing against sibling license_search.

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?

With only 25% schema coverage, the description carries real weight: it tells the agent that state must be one of the served states (resolvable via /v1/license/states), and that profession applies only to some states with values listed at /v1/license/professions. name and license_number are left to the schema's own 'either license_number or name' note, so the semantics of how those two interact (mutual exclusivity, matching behavior) are not expanded.

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

Purpose4/5

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

The sentence 'Contractor license status plus matching business-entity record' gives a concrete resource pair (license status + entity), which is more specific than the tool name. It is distinguishable from entity_lookup or npi_verify, but it never names the closest sibling, license_search, so the agent gets no explicit differentiation between the two license tools.

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 context is implied through prerequisite calls: check GET /v1/license/states for served states and GET /v1/license/professions?state= for profession values. However there is no statement of when to use this instead of license_search, nor any exclusion, so an agent must infer the choice from the tool name alone.

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

All Flipvo: licenses, entities, NPI, OFAC and OIG screens, carriers, OSHA, drive times 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?