AlpineDataWorks Intelligence Server
REMOTE · API.ALPINEDATAWORKS.COM · SCANNED SEP 22
Agent-ready economic, market & geo-health intelligence — 318 MCP tools, 309 driver-backed indices.
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 Security77
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 52214 tokens (~164/item across 318 items; 318 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 318 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 318 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the AlpineDataWorks Intelligence Server MCP server?
AlpineDataWorks Intelligence Server is a hosted endpoint at https://api.alpinedataworks.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 · api.alpinedataworks.com
claude mcp add --transport http com-alpinedataworks-adw-intelligence-server 'https://api.alpinedataworks.com/mcp'
{
"mcpServers": {
"com-alpinedataworks-adw-intelligence-server": {
"url": "https://api.alpinedataworks.com/mcp"
}
}
} {
"servers": {
"com-alpinedataworks-adw-intelligence-server": {
"type": "http",
"url": "https://api.alpinedataworks.com/mcp"
}
}
} [mcp_servers.com-alpinedataworks-adw-intelligence-server] url = "https://api.alpinedataworks.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-alpinedataworks-adw-intelligence-server": {
"type": "remote",
"url": "https://api.alpinedataworks.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-alpinedataworks-adw-intelligence-server --url 'https://api.alpinedataworks.com/mcp' --transport streamable-http
mcp_servers:
com-alpinedataworks-adw-intelligence-server:
url: "https://api.alpinedataworks.com/mcp" {
"McpServers": {
"com-alpinedataworks-adw-intelligence-server": {
"Transport": "http",
"Url": "https://api.alpinedataworks.com/mcp"
}
}
} assistant mcp add com-alpinedataworks-adw-intelligence-server -t streamable-http -u 'https://api.alpinedataworks.com/mcp'
{
"mcpServers": {
"com-alpinedataworks-adw-intelligence-server": {
"type": "http",
"url": "https://api.alpinedataworks.com/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.
- 22 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 21 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 20 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 19 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 18 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 17 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 16 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 15 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day 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 22 Sept 2026 · Probed https://api.alpinedataworks.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=alpinedataworks.com | CN=WE1,O=Google Trust Services,C=US | 19 Aug 2026 | 18 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 2e751fd9542848610e773378244a2fe9 |
| SANs: alpinedataworks.com, api.alpinedataworks.com, *.api.alpinedataworks.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 api.alpinedataworks.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| alpinedataworks.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="api.alpinedataworks.com", resource_metadata="https://api.alpinedataworks.com/.well-known/oauth-protected-resource"
Bearer realm="api.alpinedataworks.com", resource_metadata="https://api.alpinedataworks.com/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; connect-src 'self'; frame-ancestors 'self'; object-src 'none'; base-uri 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Protected resource metadata
| Document | https://api.alpinedataworks.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | No |
| Problem | metadata_http_error |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.alpinedataworks.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.alpinedataworks.com/mcp | Inconclusive | 404 |
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 →
adw.adw_254 ~169
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_255 ~161
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_256 ~155
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_257 ~148
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_258 ~162
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_259 ~156
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_260 ~155
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_261 ~161
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_262 ~157
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_263 ~157
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_264 ~156
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_310 ~161
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_311 ~171
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_312 ~161
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_313 ~168
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_314 ~163
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_335 ~176
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_339 ~166
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_347 ~173
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_348 ~162
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_349 ~173
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_354 ~168
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_355 ~172
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_356 ~167
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_357 ~171
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_377 ~164
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_382 ~167
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_383 ~166
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_384 ~165
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_385 ~162
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_386 ~161
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_387 ~160
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_388 ~157
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_390 ~161
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_391 ~154
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_392 ~165
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_393 ~159
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_394 ~156
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_395 ~166
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_397 ~165
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_400 ~163
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_401 ~158
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_402 ~162
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_404 ~162
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_405 ~158
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_408 ~165
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_409 ~164
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_411 ~175
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_412 ~169
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
adw.adw_413 ~169
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
No output schema declared.
No examples provided.
What is the AlpineDataWorks Intelligence Server MCP server?
AlpineDataWorks Intelligence Server is an MCP server listed in the public MCP registry as com.alpinedataworks/adw-intelligence-server. Agent-ready economic, market & geo-health intelligence, 318 MCP tools, 309 driver-backed indices. This page covers its hosted endpoint (https://api.alpinedataworks.com/mcp).
Is the AlpineDataWorks Intelligence Server MCP server safe to use?
AlpineDataWorks Intelligence Server scores 82 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.
Does the AlpineDataWorks Intelligence Server MCP server require authentication?
Yes. AlpineDataWorks Intelligence Server 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 AlpineDataWorks Intelligence Server MCP server still maintained?
AlpineDataWorks Intelligence Server is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.