AIUseCaseHub
REMOTE · BASIC-BACKEND713-DSD8HYGYFKC8D8F5.SWEDENCENTRAL-01.AZUREWEBSITES.NET · SCANNED SEP 20
Source-linked enterprise AI deployment search. Free preview; API keys unlock full results.
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 Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 587 tokens (~146/item across 4 items; 4 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 Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
How do I install the AIUseCaseHub MCP server?
AIUseCaseHub is a hosted endpoint at https://basic-backend713-dsd8hygyfkc8d8f5.swedencentral-01.azurewebsites.net/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 · basic-backend713-dsd8hygyfkc8d8f5.swedencentral-01.azurewebsites.net
claude mcp add --transport http flo7up-aiusecasehub 'https://basic-backend713-dsd8hygyfkc8d8f5.swedencentral-01.azurewebsites.net/api/mcp'
{
"mcpServers": {
"flo7up-aiusecasehub": {
"url": "https://basic-backend713-dsd8hygyfkc8d8f5.swedencentral-01.azurewebsites.net/api/mcp"
}
}
} {
"servers": {
"flo7up-aiusecasehub": {
"type": "http",
"url": "https://basic-backend713-dsd8hygyfkc8d8f5.swedencentral-01.azurewebsites.net/api/mcp"
}
}
} [mcp_servers.flo7up-aiusecasehub] url = "https://basic-backend713-dsd8hygyfkc8d8f5.swedencentral-01.azurewebsites.net/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"flo7up-aiusecasehub": {
"type": "remote",
"url": "https://basic-backend713-dsd8hygyfkc8d8f5.swedencentral-01.azurewebsites.net/api/mcp",
"enabled": true
}
}
} openclaw mcp add flo7up-aiusecasehub --url 'https://basic-backend713-dsd8hygyfkc8d8f5.swedencentral-01.azurewebsites.net/api/mcp' --transport streamable-http
mcp_servers:
flo7up-aiusecasehub:
url: "https://basic-backend713-dsd8hygyfkc8d8f5.swedencentral-01.azurewebsites.net/api/mcp" {
"McpServers": {
"flo7up-aiusecasehub": {
"Transport": "http",
"Url": "https://basic-backend713-dsd8hygyfkc8d8f5.swedencentral-01.azurewebsites.net/api/mcp"
}
}
} assistant mcp add flo7up-aiusecasehub -t streamable-http -u 'https://basic-backend713-dsd8hygyfkc8d8f5.swedencentral-01.azurewebsites.net/api/mcp'
{
"mcpServers": {
"flo7up-aiusecasehub": {
"type": "http",
"url": "https://basic-backend713-dsd8hygyfkc8d8f5.swedencentral-01.azurewebsites.net/api/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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 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 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 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.
- 7 Sept 26 0
- Stability: unverified → 0.03 ▲ 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 20 Sept 2026 · Probed https://basic-backend713-dsd8hygyfkc8d8f5.swedencentral-01.azurewebsites.net/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.azurewebsites.net,O=Microsoft Corporation,L=Redmond,ST=WA,C=US | CN=Microsoft TLS G2 RSA CA OCSP 04,O=Microsoft Corporation,C=US | 28 Aug 2026 | 14 Mar 2027 | RSA 2048 | SHA384-RSA | 4300e5be8b234f30f3dfcc2ddf000000e5be8b |
| SANs: *.azurewebsites.net, *.scm.azurewebsites.net, *.sso.azurewebsites.net, *.swedencentral-01.azurewebsites.net, *.scm.swedencentral-01.azurewebsites.net, *.sso.swedencentral-01.azurewebsites.net, *.swedencentral.c.azurewebsites.net, *.scm.swedencentral.c.azurewebsites.net, *.sso.swedencentral.c.azurewebsites.net, *.azure-mobile.net, *.scm.azure-mobile.net | ||||||
| CN=Microsoft TLS G2 RSA CA OCSP 04,O=Microsoft Corporation,C=US (CA) | CN=Microsoft TLS RSA Root G2,O=Microsoft Corporation,C=US | 1 Aug 2025 | 3 Jun 2029 | RSA 4096 | SHA384-RSA | 330000000b13e5667d4a9b558000000000000b |
| CN=Microsoft TLS RSA Root G2,O=Microsoft Corporation,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 21 May 2025 | 19 Jun 2029 | RSA 4096 | SHA384-RSA | b0c6b2c466917b04773c647d4afc0c8 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of basic-backend713-dsd8hygyfkc8d8f5.swedencentral-01.azurewebsites.net. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| net. | present | 37331 | 13 | Verified |
| azurewebsites.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://basic-backend713-dsd8hygyfkc8d8f5.swedencentral-01.azurewebsites.net/api/mcp | Verified | 200 | |
| http (plaintext) | http://basic-backend713-dsd8hygyfkc8d8f5.swedencentral-01.azurewebsites.net/api/mcp | HTTPS enforced | 301 | https://basic-backend713-dsd8hygyfkc8d8f5.swedencentral-01.azurewebsites.net/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_usecase_details Read an AI deployment case ~51
Fetch detailed information for a single AI use case by RowKey/id.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | Alias for row_key. |
| row_key | string | yes | The RowKey/id returned by search tools. |
No output schema declared.
No examples provided.
hybrid_search_usecases Search AI deployments with filters ~310
Search AI use cases with hybrid full-text and vector ranking. Supports provider, industry, geography, technology, customer, partner, and boolean case-type filters.
| Name | Type | Req | Description |
|---|---|---|---|
| cloud_provider | string | – | Microsoft, AWS, GCP, or comma-separated values. |
| country | string | – | Filter by country code, for example US or GB. |
| customer_name | string | – | Filter by the company adopting AI. |
| industry | string | – | Filter by the deployment industry. |
| isAgentCase | boolean | – | Filter for AI agent deployments. |
| isAvatar | boolean | – | Filter for AI avatar deployments. |
| isCopilot | boolean | – | Filter for copilot deployments. |
| isFineTuning | boolean | – | Filter for model fine-tuning deployments. |
| isMicrosoftFabric | boolean | – | Filter for Microsoft Fabric deployments. |
| isMultiAgentCase | boolean | – | Filter for multi-agent deployments. |
| isRag | boolean | – | Filter for retrieval-augmented generation deployments. |
| isSustainabilityCase | boolean | – | Filter for sustainability use cases. |
| isVision | boolean | – | Filter for computer vision deployments. |
| isVoice | boolean | – | Filter for voice AI deployments. |
| limit | integer | – | Maximum results requested. Public previews return at most 3; personal-key access permits up to 20. |
| partner_name | string | – | Filter by implementation partner. |
| query | string | yes | Natural-language query. |
| technologies_used | string | – | Filter by technology name. |
No output schema declared.
No examples provided.
search_usecases Search enterprise AI deployments ~82
Search curated AI use cases using the default hybrid ranking. Use this when an agent has a natural-language search term.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum results requested. Public previews return at most 3; personal-key access permits up to 20. |
| query | string | – | Alias for search_term. |
| search_term | string | yes | Natural-language search term. |
No output schema declared.
No examples provided.
vector_search_usecases Find semantically similar AI deployments ~62
Semantic vector search for AI use cases using the meaning of the query text.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum results requested. Public previews return at most 3; personal-key access permits up to 20. |
| query | string | yes | Natural-language query. |
No output schema declared.
No examples provided.
What is the AIUseCaseHub MCP server?
AIUseCaseHub is an MCP server listed in the public MCP registry as io.github.flo7up/aiusecasehub. Source-linked enterprise AI deployment search. Free preview; API keys unlock full results. This page covers its hosted endpoint (https://basic-backend713-dsd8hygyfkc8d8f5.swedencentral-01.azurewebsites.net/api/mcp).
Is the AIUseCaseHub MCP server safe to use?
AIUseCaseHub scores 78 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 AIUseCaseHub MCP server expose?
AIUseCaseHub exposes 4 tools: search_usecases, hybrid_search_usecases, vector_search_usecases, get_usecase_details. Their descriptions and schemas cost roughly 505 tokens of context every time the server is loaded.
Does the AIUseCaseHub MCP server require authentication?
No. We connected to AIUseCaseHub without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AIUseCaseHub MCP server still maintained?
AIUseCaseHub is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.