SaltCrate Oracle
REMOTE · ORACLE.SALTCRATE.COM
Verify, monitor & diff web pages for agents. 100 free calls, $0.05/call or $9/mo.
Available components
Last scanned (15 hours ago)
Scores higher than 65% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Search and Retrieval
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 Security80
- 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 882 tokens (~110/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Nov 26 +9
- Authorization: unverified → partial ▲ security
- HSTS header: fail → pass ▲ security
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.1.6 → 1.1.9 functional
- 14 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 63 → 102 ▼ functional
- Schema quality: 63 → 103 ▼ functional
- 13 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Nov 26 +1
- Schema quality: 56 → 63 ▼ functional
- New tool “check_deps” functional
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 21 Nov 2026 · Probed https://oracle.saltcrate.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=saltcrate.com | CN=YE2,O=Let's Encrypt,C=US | 14 Oct 2026 | 12 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 66fd5f767b0f1f89d1b62b49bc3b902b0b4 |
| SANs: *.saltcrate.com, saltcrate.com | ||||||
| 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 oracle.saltcrate.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| saltcrate.com. | No DS | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://oracle.saltcrate.com/mcp | Verified | 200 | |
| http (plaintext) | http://oracle.saltcrate.com/mcp | HTTPS enforced | 301 | https://oracle.saltcrate.com/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 →
check_change ~50
Did this web page change since the last time it was checked? Hash-based change detection. First check reports 'new'; later checks report 'changed' or 'unchanged'.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
No output schema declared.
No examples provided.
check_deps ~115
Is this dependency current, and does the version in use have known vulnerabilities? Takes a package name and returns the latest version, deprecation/license, and advisories from OSV.dev with the version that fixes each. Accepts 'lodash@4.17.20' (npm-style), 'requests==2.19.0' (PyPI-style), or a prefix: npm:, pypi:, cargo:, go:, gem:. Backed by the live registries — no guessing.
| Name | Type | Req | Description |
|---|---|---|---|
| package | string | yes | – |
No output schema declared.
No examples provided.
check_link ~40
Is this URL live right now? Returns HTTP status, the redirect chain, final URL, and round-trip latency in milliseconds.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
No output schema declared.
No examples provided.
extract ~80
Schema-driven structured extraction: fetch a URL and map its content into typed entities that conform to a JSON Schema you provide. Pass the schema as a JSON string; returns schema-conforming JSON (e.g. pricing, company facts, product specs, events). Requires DEEPSEEK_API_KEY.
| Name | Type | Req | Description |
|---|---|---|---|
| schema | string | yes | – |
| url | string | yes | – |
No output schema declared.
No examples provided.
fetch ~57
Get clean, readable text from a web page — boilerplate, navigation, and ads stripped — so you can work with the actual content. Returns the text plus title, content-type, HTTP status, and length.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
No output schema declared.
No examples provided.
monitor ~61
Watch a URL over time — call periodically and pay per check. First call reports 'new'; later calls report 'changed' or 'unchanged', with changes_since_first_seen, first_seen, and last_checked timestamps for recurring monitoring.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
No output schema declared.
No examples provided.
search ~51
Live web search. Returns a list of {title, url, snippet} results plus which backend served them (free DuckDuckGo by default, or Brave/Serper when configured).
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
No output schema declared.
No examples provided.
verify ~57
Does this source URL support a given claim? Returns a confidence score, matched terms, and the best supporting excerpt. Heuristic term-overlap — not semantic fact-checking.
| Name | Type | Req | Description |
|---|---|---|---|
| claim | string | yes | – |
| source_url | string | yes | – |
No output schema declared.
No examples provided.
How do I install the SaltCrate Oracle MCP server?
SaltCrate Oracle is a hosted endpoint at https://oracle.saltcrate.com/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 · oracle.saltcrate.com
claude mcp add --transport http com-saltcrate-oracle 'https://oracle.saltcrate.com/mcp'
What is the SaltCrate Oracle MCP server?
SaltCrate Oracle is an MCP server listed in the public MCP registry as com.saltcrate/oracle. Verify, monitor & diff web pages for agents. 100 free calls, $0.05/call or $9/mo. This page covers its hosted endpoint (https://oracle.saltcrate.com/mcp).
Is the SaltCrate Oracle MCP server safe to use?
SaltCrate Oracle scores 76 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 SaltCrate Oracle MCP server expose?
SaltCrate Oracle exposes 8 tools: fetch, check_link, check_change, verify, extract, and 3 more. Their descriptions and schemas cost roughly 511 tokens of context every time the server is loaded.
Does the SaltCrate Oracle MCP server require authentication?
No. We connected to SaltCrate Oracle without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SaltCrate Oracle MCP server still maintained?
SaltCrate Oracle is still listed as active in the MCP registry. We last reached this channel on 21 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 SaltCrate Oracle MCP server?
VerifyMCP ran 13 checks on SaltCrate Oracle, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.