Contract
{
"type": "object",
"required": [
"package"
],
"properties": {
"package": {
"type": "string"
}
},
"additionalProperties": false
}{
"type": "object",
"properties": {
"code": {
"type": "string",
"description": "Present instead of package fields when the queried name does not resolve to a real npm package, e.g. 'HTTP_400'."
},
"name": {
"type": "string",
"description": "The npm package name, e.g. 'react'."
},
"author": {
"description": "Package author/maintainer metadata as npm's own registry publishes it. Often `null` -- shape when populated (a plain string vs. an {name, email, url} object, npm's own registry supports both) is not documented; do not assume a fixed shape."
},
"created": {
"type": "string",
"description": "ISO 8601 timestamp the package was first published."
},
"license": {
"type": "string",
"description": "SPDX-style license identifier, e.g. 'MIT'."
},
"message": {
"type": "string",
"description": "Human-readable detail accompanying `code`, e.g. 'Invalid input: HTTP 400'."
},
"keywords": {
"type": "array",
"items": {
"type": "string"
},
"description": "Keyword tags the package's maintainer attached to it on npm."
},
"dist_tags": {
"type": "object",
"properties": {
"rc": {
"type": "string"
},
"beta": {
"type": "string"
},
"next": {
"type": "string"
},
"canary": {
"type": "string"
},
"latest": {
"type": "string"
},
"backport": {
"type": "string"
},
"experimental": {
"type": "string"
}
},
"description": "npm dist-tag pointers (which version each tag currently resolves to). A popular package may carry several tags (seven observed for react) -- a package that has never published under a given tag may omit that key.",
"additionalProperties": true
},
"description": {
"type": "string",
"description": "The package's own npm registry description."
},
"dependencies": {
"type": "array",
"description": "Runtime dependencies. Often empty (`[]`) -- item shape when populated is not documented."
},
"last_modified": {
"type": "string",
"description": "ISO 8601 timestamp of the package's most recent publish."
},
"latest_version": {
"type": "string",
"description": "e.g. '19.2.8'."
},
"total_versions": {
"type": "number",
"description": "Count of versions ever published for this package."
},
"recent_versions": {
"type": "array",
"items": {
"type": "object",
"properties": {
"version": {
"type": "string"
},
"published": {
"type": "string",
"description": "ISO 8601 publish timestamp."
}
},
"additionalProperties": true
},
"description": "The most recently published versions, newest first."
},
"dev_dependencies": {
"type": "array",
"description": "Development-only dependencies. Often empty (`[]`) -- item shape when populated is not documented."
},
"weekly_downloads": {
"type": "number",
"description": "Downloads over the trailing week."
}
},
"description": "The npm package record. A package name that does not resolve to a real npm package returns `code`/`message` instead of any package field below.",
"additionalProperties": true
}Pricing
Every real charge, itemised. A model that quietly omits one is a slow financial leak, so nothing here is rolled up, and a charge that only applies to some inputs says so rather than being added in.
Prices in this catalog are the provider's own list price, not your bill: Omnial MCP charges provider cost plus a platform markup on top, so what you are charged is higher than the figure shown. For the exact amount a specific call will cost, run omnial_execute with dry_run: true; that number includes the markup and is what we hold while the call runs. It is a quote, not a cap on the charge.
| Charge | Rate |
|---|---|
Per call Flat, regardless of what comes back | $0.081081 |
- Cost basis
- Not recorded
This tool's catalog entry does not record how its final bill is determined, so we will not tell you whether its cost is fixed before the call or reported by the provider afterwards. Either way what is held is a quote rather than a cap: you are charged what the call actually costs, bounded at 2x the quote.
- Updated
- Oct 12, 2026
