Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Strategic Innovations APIs

REMOTE · STRATEGIC-INNOVATIONS.AI

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

+3 this week 71 Trust /100

Last scanned (16 hours ago)

Scores higher than 56% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Web Scraping

Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
  • Stability observed for 12 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation 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.

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 →

Changelog

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 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.

  • 19 Nov 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.

  • 17 Nov 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.

  • 14 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.

  • 12 Nov 26 +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.

  • 10 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 9 Nov 26 65

    First indexed and scored.

Diagnostics

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://strategic-innovations.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=strategic-innovations.ai CN=WE1,O=Google Trust Services,C=US 18 Nov 2026 16 Feb 2027 ECDSA 256 ECDSA-SHA256 3477e40dd8b05ff0e3d86f1635cc5b0
SANs: strategic-innovations.ai, holoemail.strategic-innovations.ai, *.holoemail.strategic-innovations.ai
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 strategic-innovations.ai. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814 8 Verified
strategic-innovations.ai. 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=31536000; includeSubDomains
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://strategic-innovations.ai/mcp Verified 200
http (plaintext) http://strategic-innovations.ai/mcp HTTPS enforced 301 https://strategic-innovations.ai/mcp
MCP tools · 3 exposed · ~458 tokens

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 →

Tool Tokens
check_agent_readiness ~167

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.

NameTypeReqDescription
api_keystring–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.
urlstringyesThe site to check, e.g. example.com

No output schema declared.

No examples provided.

fetch_page ~175

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.

NameTypeReqDescription
api_keystring–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.
urlstringyesThe page to fetch, e.g. https://developers.cloudflare.com/workers/

No output schema declared.

No examples provided.

request_key ~116

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.

NameTypeReqDescription
agentstring–A short name for your agent, shown to that person
emailstringyesEmail of the person the agent works for

No output schema declared.

No examples provided.

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.

remote · strategic-innovations.ai

# add to Claude Code
claude mcp add --transport http ai-strategic-innovations-apis 'https://strategic-innovations.ai/mcp'
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.