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.

Ace Website MCP

REMOTE · ACE-BL.TECH

Search and read public Ace pages with source URLs.

Available components

+6 this week 81 Trust /100

Last scanned (17 hours ago)

Scores higher than 84% of remote servers

Reachable. Last reached 4 Nov 2026.

Category E-commerce

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 Security77
Transport & Reachability100
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 309 tokens (~51/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.

  • 4 Nov 26 +6
    • Authorization: unverified → partial ▲ security
    • Stability: pass → 0.97 functional
  • 18 Oct 26 −7
    • Authorization: partial → unverified ▼ security
    • Tool “create_checkout” changed its title: Create a checkout link cosmetic
    • Tool “get_checkout” changed its title: Read checkout status cosmetic
    • Tool “list_products” changed its title: List products and prices cosmetic
    • Tool “read_page” changed its title: Read website page cosmetic
    • Tool “search_pages” changed its title: Search website pages cosmetic
    • Tool “site_info” changed its title: Site information cosmetic
  • 17 Oct 26 +1
    • Stability: 0.97 → pass security
  • 15 Oct 26 +1

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

  • 12 Oct 26 +1

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

  • 10 Oct 26 +2

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

  • 7 Oct 26 +1

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

  • 4 Oct 26 +1

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

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 4 Nov 2026 · Probed https://ace-bl.tech/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=ace-bl.tech CN=WE1,O=Google Trust Services,C=US 5 Oct 2026 3 Jan 2027 ECDSA 256 ECDSA-SHA256 c1c3cef253fd2b940e3805775c216c56
SANs: ace-bl.tech
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 secure

Validation of ace-bl.tech. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
tech. present 2185 13 Verified
ace-bl.tech. present 2371 13 Verified
ace-bl.tech. Verified address RRset verified with the apex keys
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://ace-bl.tech/mcp Verified 200
http (plaintext) http://ace-bl.tech/mcp HTTPS enforced 301 https://ace-bl.tech/mcp
MCP tools · 6 exposed · ~231 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
create_checkout ~56

Start a purchase of one offer. Returns a continue_url: send the buyer there to pay on the Stripe-hosted checkout page. This tool does not charge anything.

NameTypeReqDescription
offer_idstringyes–
quantityinteger––

No output schema declared.

No examples provided.

get_checkout ~24

Read a checkout started with create_checkout.

NameTypeReqDescription
checkout_idstringyes–

No output schema declared.

No examples provided.

list_products ~30

Everything an agent can buy from Ace, with Stripe-verified prices, billing terms, delivery and live availability.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

read_page ~44

Read one https://ace-bl.tech page as Markdown (Cloudflare Markdown for Agents) or stripped text, up to 40,000 characters.

NameTypeReqDescription
urlstringyes–

No output schema declared.

No examples provided.

search_pages ~46

Find pages on ace-bl.tech by words in their URL path (sitemap search). Returns URLs with a match score.

NameTypeReqDescription
limitinteger––
querystringyes–

No output schema declared.

No examples provided.

site_info ~31

What Ace (ace-bl.tech) is, with links to its sitemap, docs, contact and every discovery document.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Ace Website MCP server?

Ace Website MCP is a hosted endpoint at https://ace-bl.tech/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 · ace-bl.tech

# add to Claude Code
claude mcp add --transport http tech-ace-bl-site-mcp 'https://ace-bl.tech/mcp'
Common questions

What is the Ace Website MCP server?

Ace Website MCP is listed in the public MCP registry as tech.ace-bl/site-mcp. Search and read public Ace pages with source URLs. This page covers its hosted endpoint (https://ace-bl.tech/mcp).

Is the Ace Website MCP server safe to use?

Ace Website MCP scores 81 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 Ace Website MCP server expose?

Ace Website MCP exposes 6 tools: site_info, search_pages, read_page, list_products, create_checkout, get_checkout. Their descriptions and schemas cost roughly 231 tokens of context every time the server is loaded.

Does the Ace Website MCP server require authentication?

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

Is the Ace Website MCP server still maintained?

Ace Website MCP is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.