Omnicost
REMOTE · OMNICOST.COM
Construction unit prices with source and date for Spain, the US and the EU. OAuth or API key.
Available components
Last scanned (13 hours ago)
Scores higher than 35% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
Checks we ran (5)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
Checks we could not complete (6)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Transport in Transport & Reachability (scores 0 for this)Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Tool safety in Tool Safety (scores 0 for this)Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Capabilities in Capabilities (scores 0 for this)Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 −33
- Endpoint reachability: reachable → behind authorisation ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.07 → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: partial → pass ▲ security
- First check of Authorization: pass security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 1 Nov 26 +35
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Authorization: fail → partial ▲ security
- First check of Judged manipulation: pass security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- First check of Tool coverage: 80 functional
- 29 Oct 26 36
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://omnicost.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=omnicost.com | CN=WE1,O=Google Trust Services,C=US | 30 Oct 2026 | 28 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | e12abbb44e08759a130e48c3d20bfcd4 |
| SANs: omnicost.com, *.omnicost.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of omnicost.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| omnicost.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer realm="omnicost", error="missing_token", resource_metadata="https://omnicost.com/.well-known/oauth-protected-resource"
Bearer realm="omnicost", error="missing_token", resource_metadata="https://omnicost.com/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
| www-authenticate | Bearer realm="omnicost", error="missing_token", resource_metadata="https://omnicost.com/.well-known/oauth-protected-resource" |
Protected resource metadata
| Document | https://omnicost.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://omnicost.com/api/mcp |
| Authorisation server | https://omnicost.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://omnicost.com/api/mcp | Auth required | 401 | |
| http (plaintext) | http://omnicost.com/api/mcp | HTTPS enforced | 301 | https://omnicost.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_decomposition Get item cost breakdown ~117
BC3 recipe tree for an item: material+labor+machinery components per unit. Returns parent_code and component rows {child_code, factor, yield, per_unit, name, unit, unit_price, item_id}; item_id (vsku_…) can be passed back to get_decomposition. Deprecated (kept for one release): parentId, parentCode, and per component catalog_item_id and position.
| Name | Type | Req | Description |
|---|---|---|---|
| item_id | string | yes | Canonical id or vendor SKU id (ci_xxx / vsku_xxx) |
No output schema declared.
No examples provided.
get_item Get catalog item ~54
Fetch a canonical item with vendor breakdown and recent price history. Returns Markdown for readability. Deprecated in structuredContent (kept for one release): item.category_id.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Canonical id (ci_xxx) |
No output schema declared.
No examples provided.
list_categories List catalog categories ~48
Catalog categories: structuredContent.categories items are {id, name, parentId, parent} where parent is the parent category's name. Deprecated (kept for one release): id, parentId.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_catalog Search construction cost catalog ~97
Semantic search for canonical construction-cost items. Returns top-K matches with median price, vendor count, and source trust. Deprecated in structuredContent.results (kept for one release): score, category_id.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| q | string | yes | Free-text query (e.g. 'concrete HA-25 m³') |
| region | string | – | Restrict to canonicals with at least one vendor in this region |
No output schema declared.
No examples provided.
How do I install the Omnicost MCP server?
Omnicost is a hosted endpoint at https://omnicost.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · omnicost.com
claude mcp add --transport http com-omnicost-catalog 'https://omnicost.com/api/mcp'
What is the Omnicost MCP server?
Omnicost is an MCP server listed in the public MCP registry as com.omnicost/catalog. Construction unit prices with source and date for Spain, the US and the EU. OAuth or API key. This page covers its hosted endpoint (https://omnicost.com/api/mcp).
Is the Omnicost MCP server safe to use?
Omnicost scores 39 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Omnicost MCP server expose?
Omnicost exposes 4 tools: search_catalog, get_item, list_categories, get_decomposition. Their descriptions and schemas cost roughly 316 tokens of context every time the server is loaded.
Does the Omnicost MCP server require authentication?
Yes. Omnicost asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Omnicost MCP server still maintained?
Omnicost is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Omnicost MCP server?
VerifyMCP ran 5 checks on Omnicost, covering TLS certificate, Authorization, HTTPS, HSTS header and 1 more. 6 items could not be completed, a gap on our side rather than a finding about Omnicost: Transport, Schema quality, Stability, Tool coverage and 2 more. 6 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.