# Strategic Innovations APIs (remote · strategic-innovations.ai)

Fetch web pages as Markdown, judged real or not first, and check sites for AI-agent readiness.

- Trust score: 71/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `strategic-innovations.ai`: 71/100 (this document), [markdown](https://verifymcp.io/servers/ai-strategic-innovations-apis/strategic-innovations.md), [page](https://verifymcp.io/servers/ai-strategic-innovations-apis/strategic-innovations)

## Channel facts

- Endpoint: `https://strategic-innovations.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 529 tokens (~176/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Strategic Innovations APIs MCP server?

Strategic Innovations APIs is a hosted endpoint at https://strategic-innovations.ai/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.

### Claude

```bash
claude mcp add --transport http ai-strategic-innovations-apis 'https://strategic-innovations.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-strategic-innovations-apis": {
      "url": "https://strategic-innovations.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-strategic-innovations-apis": {
      "type": "http",
      "url": "https://strategic-innovations.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-strategic-innovations-apis]
url = "https://strategic-innovations.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-strategic-innovations-apis": {
      "type": "remote",
      "url": "https://strategic-innovations.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-strategic-innovations-apis --url 'https://strategic-innovations.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-strategic-innovations-apis:
    url: "https://strategic-innovations.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-strategic-innovations-apis": {
      "Transport": "http",
      "Url": "https://strategic-innovations.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-strategic-innovations-apis -t streamable-http -u 'https://strategic-innovations.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-strategic-innovations-apis": {
      "type": "http",
      "url": "https://strategic-innovations.ai/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 71, +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.

### 2026-11-19 (score 70, +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.

### 2026-11-17 (score 69, +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.

### 2026-11-14 (score 68, +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.

### 2026-11-12 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-10 (score 66, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-09 (score 65)

First indexed and scored.

## MCP tools (3)

### `request_key` (~116 tokens)

Get an API key for this server

Get a working API key now, without a sign-up form. Give the email of the person you work for: the key works at once for a few calls a day, they get one email, and when they confirm it the same key moves to the free plan of 100 calls a day. Then send it as Authorization: Bearer <key> on this server.

Input parameters:

- `agent` (string): A short name for your agent, shown to that person
- `email` (string, required): Email of the person the agent works for

### `fetch_page` (~175 tokens)

Fetch a web page as clean Markdown

Fetch a web page and get its main text as Markdown, with the title, word count, outgoing links, the final URL after redirects, and a SHA-256 of the Markdown. Before returning it, the page is judged: an app shell that needs JavaScript, a bot challenge, a cookie wall, a sign-in redirect or an error page comes back as verdict not_content with the reason, and does not count against your calls. Plain HTTP only: it does not run JavaScript.

Input parameters:

- `api_key` (string): Your key (sik_…), only if your MCP client cannot send it as the Authorization header, for example a key you just got from request_key. The header wins when both are sent.
- `url` (string, required): The page to fetch, e.g. https://developers.cloudflare.com/workers/

### `check_agent_readiness` (~167 tokens)

Check whether AI agents can use a website

Check a website the way an AI agent meets it: robots.txt and content signals, sitemap, Markdown on request, llms.txt, the API catalog, OAuth discovery, an MCP server card, agent skills, an A2A card, and whether the home page lets an agent in. Each file is checked by its body against an address that cannot exist, so a site that answers every path with its home page is reported as a false pass instead of a pass.

Input parameters:

- `api_key` (string): Your key (sik_…), only if your MCP client cannot send it as the Authorization header, for example a key you just got from request_key. The header wins when both are sent.
- `url` (string, required): The site to check, e.g. example.com

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-strategic-innovations-apis/strategic-innovations#diagnostics

## Score history

- 2026-11-21: 71
- 2026-11-20: 70
- 2026-11-19: 70
- 2026-11-18: 69
- 2026-11-17: 69
- 2026-11-16: 68
- 2026-11-15: 68
- 2026-11-14: 68
- 2026-11-13: 67
- 2026-11-12: 67
- 2026-11-11: 66
- 2026-11-10: 66
- 2026-11-09: 65

## Common questions

### What is the Strategic Innovations APIs MCP server?

Strategic Innovations APIs is an MCP server listed in the public MCP registry as ai.strategic-innovations/apis. Fetch web pages as Markdown, judged real or not first, and check sites for AI-agent readiness. This page covers its hosted endpoint (https://strategic-innovations.ai/mcp).

### Is the Strategic Innovations APIs MCP server safe to use?

Strategic Innovations APIs scores 71 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 Strategic Innovations APIs MCP server expose?

Strategic Innovations APIs exposes 3 tools: request_key, fetch_page, check_agent_readiness. Their descriptions and schemas cost roughly 458 tokens of context every time the server is loaded.

### Does the Strategic Innovations APIs MCP server require authentication?

No. We connected to Strategic Innovations APIs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Strategic Innovations APIs MCP server still maintained?

Strategic Innovations APIs 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 Strategic Innovations APIs MCP server?

VerifyMCP ran 12 checks on Strategic Innovations APIs, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Strategic Innovations APIs: Authorization. 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.

## Links

- Remote endpoint: https://strategic-innovations.ai/mcp
- Website: https://strategic-innovations.ai/apis
- Changelog RSS feed: https://verifymcp.io/servers/ai-strategic-innovations-apis/strategic-innovations.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-strategic-innovations-apis/strategic-innovations/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/ai-strategic-innovations-apis/strategic-innovations.json
- HTML version of this page: https://verifymcp.io/servers/ai-strategic-innovations-apis/strategic-innovations
