Standard Titanium Quotations
REMOTE · API.TITANIUM.NET · SCANNED SEP 25
Request titanium quotations and check enquiry status with Standard Titanium.
Available components
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 183 tokens (~91/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management39
- Stability check failed: schema churn in the 28 days we've observed: 1 tool removals, 1 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Standard Titanium Quotations MCP server?
Standard Titanium Quotations is a hosted endpoint at https://api.titanium.net/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 · api.titanium.net
claude mcp add --transport http net-titanium-quotations 'https://api.titanium.net/mcp'
{
"mcpServers": {
"net-titanium-quotations": {
"url": "https://api.titanium.net/mcp"
}
}
} {
"servers": {
"net-titanium-quotations": {
"type": "http",
"url": "https://api.titanium.net/mcp"
}
}
} [mcp_servers.net-titanium-quotations] url = "https://api.titanium.net/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"net-titanium-quotations": {
"type": "remote",
"url": "https://api.titanium.net/mcp",
"enabled": true
}
}
} openclaw mcp add net-titanium-quotations --url 'https://api.titanium.net/mcp' --transport streamable-http
mcp_servers:
net-titanium-quotations:
url: "https://api.titanium.net/mcp" {
"McpServers": {
"net-titanium-quotations": {
"Transport": "http",
"Url": "https://api.titanium.net/mcp"
}
}
} assistant mcp add net-titanium-quotations -t streamable-http -u 'https://api.titanium.net/mcp'
{
"mcpServers": {
"net-titanium-quotations": {
"type": "http",
"url": "https://api.titanium.net/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 36.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 26 to 29.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 19 to 23.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 16.
- 17 Sept 26 −7
- Stability: 0.63 → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “request_titanium_quote” was removed ▼ security
- Tool “get_quote_status” rewrote its description, which is the text the model reads security
- Tool “request_quote” rewrote its description, which is the text the model reads security
- “request_quote” added a required parameter “deliveryLocation”, so existing callers break ▼ functional
- “request_quote” added a required parameter “items”, so existing callers break ▼ functional
- “request_quote” dropped the required parameter “description” ▼ functional
- “request_quote” dropped the required parameter “postcode” ▼ functional
- “request_quote” dropped the required parameter “service” ▼ functional
- Schema quality: fail → pass ▲ functional
- “get_quote_status” reworded the description of “enquiryId” cosmetic
- Tool “request_quote” changed its title: Request a quotation → Request a multi-line titanium quotation cosmetic
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
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 25 Sept 2026 · Probed https://api.titanium.net/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.titanium.net | CN=YE2,O=Let's Encrypt,C=US | 17 Aug 2026 | 15 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 56066c2bca62785d31153d95aa041394e6f |
| SANs: api.titanium.net | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.titanium.net. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| net. | present | 37331 | 13 | Verified |
| titanium.net. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.titanium.net/mcp | Verified | 200 | |
| http (plaintext) | http://api.titanium.net/mcp | HTTPS enforced | 301 | https://api.titanium.net/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_quote_status Check quotation status ~62
Check a submitted quotation. While pending review, only the pending-review state is returned. Once QUOTED, the response includes the quoted products, approved line prices and total amount.
| Name | Type | Req | Description |
|---|---|---|---|
| enquiryId | string | yes | The enquiry ID returned when the quotation was submitted |
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | yes | – |
| enquiryId | string | yes | – |
| items | array | yes | – |
| message | string | yes | – |
| quotedAmount | number | yes | – |
| status | string | yes | – |
| updatedAt | string | yes | – |
No examples provided.
request_quote Request a multi-line titanium quotation ~107
Submit one or more structured titanium line items for quotation review. Each item may include sectionShape (ROUND, HEX, FLAT or UNKNOWN). Only call after the customer has reviewed all interpreted items and explicitly agreed to submit them.
| Name | Type | Req | Description |
|---|---|---|---|
| customerName | string | yes | Customer's full name |
| deliveryLocation | string | yes | Delivery location or postcode |
| string | yes | Customer's email address | |
| items | array | yes | One or more structured titanium requirements. Include sectionShape where relevant. |
| Name | Type | Req | Description |
|---|---|---|---|
| createdAt | string | yes | – |
| enquiryId | string | yes | – |
| message | string | yes | – |
| status | string | yes | – |
No examples provided.
What is the Standard Titanium Quotations MCP server?
Standard Titanium Quotations is an MCP server listed in the public MCP registry as net.titanium/quotations. Request titanium quotations and check enquiry status with Standard Titanium. This page covers its hosted endpoint (https://api.titanium.net/mcp).
Is the Standard Titanium Quotations MCP server safe to use?
Standard Titanium Quotations scores 77 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 Standard Titanium Quotations MCP server expose?
Standard Titanium Quotations exposes 2 tools: get_quote_status, request_quote. Their descriptions and schemas cost roughly 169 tokens of context every time the server is loaded.
Does the Standard Titanium Quotations MCP server require authentication?
No. We connected to Standard Titanium Quotations without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Standard Titanium Quotations MCP server still maintained?
Standard Titanium Quotations is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.