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.

SURESOFT CT

REMOTE · APPS.SURESOFTTECH.COM

Answers questions about SURESOFT CT C/C++ unit and integration testing from its product page.

70 Trust /100

Last scanned (12 hours ago)

Scores higher than 54% of remote servers

Reachable. Last reached 21 Nov 2026.

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 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. 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
  • 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
Schema Quality & AI Usability66
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 395 tokens (~49/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 Management7
  • Stability observed for 2 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 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

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 →

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.

  • 20 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 19 Nov 26 69

    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://apps.suresofttech.com/ct/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=apps.suresofttech.com CN=WE1,O=Google Trust Services,C=US 4 Oct 2026 3 Jan 2027 ECDSA 256 ECDSA-SHA256 2d1dfd589011a3480e8f499abd2fc422
SANs: apps.suresofttech.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 apps.suresofttech.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
suresofttech.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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://apps.suresofttech.com/ct/mcp Verified 200
http (plaintext) http://apps.suresofttech.com/ct/mcp HTTPS enforced 301 https://apps.suresofttech.com/ct/mcp
MCP tools · 8 exposed · ~301 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
ct_ai_integration ~30

How CT works with AI and AI coding agents, as described on the SURESOFT site.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

ct_contact ~23

How to contact Suresofttech about CT: inquiries and demo requests.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

ct_get_section ~57

Returns one section of the CT product page, such as key features, editions, use cases or industry standards. Use a title from ct_list_sections.

NameTypeReqDescription
sectionstringyesSection title or anchor, e.g. "Key features".

No output schema declared.

No examples provided.

ct_list_sections ~23

Lists every section and subsection of the CT product page with its URL.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

ct_overview ~41

What SURESOFT CT is: the definition and overview from the official CT product page, with the list of page sections that ct_get_section can return.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

ct_resources ~22

White papers, product materials and videos listed in the CT resource library.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

ct_search_faq ~53

Searches the frequently asked questions on the CT product page. Leave query empty to list every question.

NameTypeReqDescription
querystring–Words to look for, e.g. "MISRA" or "air-gapped".

No output schema declared.

No examples provided.

ct_supported_languages ~52

Languages, versions and development environments CT supports, from the CT page and the Supported Languages page.

NameTypeReqDescription
languagestring–Optional: limit to one language, e.g. "C/C++", "Java".

No output schema declared.

No examples provided.

Install

How do I install the SURESOFT CT MCP server?

SURESOFT CT is a hosted endpoint at https://apps.suresofttech.com/ct/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 · apps.suresofttech.com

# add to Claude Code
claude mcp add --transport http suresofttechnologies-suresoft-ct 'https://apps.suresofttech.com/ct/mcp'
Common questions

What is the SURESOFT CT MCP server?

SURESOFT CT is an MCP server listed in the public MCP registry as io.github.SuresoftTechnologies/suresoft-ct. Answers questions about SURESOFT CT C/C++ unit and integration testing from its product page. This page covers its hosted endpoint (https://apps.suresofttech.com/ct/mcp).

Is the SURESOFT CT MCP server safe to use?

SURESOFT CT scores 70 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 SURESOFT CT MCP server expose?

SURESOFT CT exposes 8 tools: ct_overview, ct_list_sections, ct_get_section, ct_search_faq, ct_supported_languages, and 3 more. Their descriptions and schemas cost roughly 301 tokens of context every time the server is loaded.

Does the SURESOFT CT MCP server require authentication?

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

Is the SURESOFT CT MCP server still maintained?

SURESOFT CT 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 SURESOFT CT MCP server?

VerifyMCP ran 13 checks on SURESOFT CT, 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.