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.
+30 this week 49 Trust /100

Last scanned (23 hours ago)

Scores higher than 85% of MCPB servers

Category Communication

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to gridhra/chat-tool-ui-preview). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 10 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability62
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 460 tokens (~460/item across 1 items; 1 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 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

Unverified: 2 categories

Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

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.

  • 13 Oct 26 +30
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • First check of Tool coverage: 100 functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: excellent functional
    • First check of Destructive annotations: pass functional
    • First check of Schema quality: fail functional
    • First check of Tool coverage: 100 functional
  • 7 Oct 26 19

    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 18 Oct 2026 · Analysed mcpb/https://github.com/gridhra/chat-tool-ui-preview/releases/download/v0.1.1/chat-preview_0.1.1_linux_amd64.mcpb@0.1.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem mcpb
Reason Verified
Discovered via GitHub artifact attestations
Source repo gridhra/chat-tool-ui-preview
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/gridhra/chat-tool-ui-preview/.github/workflows/release.yml@refs/tags/v0.1.1
Rekor log index 3125788742
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha256:86ed2a5d16b6f91fba28fbae9af3be5f8fc3278a0094b8adfc6070814db07ad8

Background: How many MCP packages publish verified provenance →

MCP tools · 1 exposed · ~327 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
preview_message ~327

Render a chat post as a preview page, open it in the user's browser, and return the file path and the warnings found (unresolved mentions, @here/@channel broadcasts, unknown emoji, length limits, invalid blocks). Does not send anything. Call it before sending a message on the user's behalf, then ask the user to confirm in chat.

NameTypeReqDescription
asstring–user (default) when sent as the user, bot when sent as an app
blocksnull|array–Block Kit blocks array when format=blocks
channel_idstring–destination channel or user ID exactly as it will be sent
channel_namestring–human-readable channel name if known
formatstringyesmarkdown (Claude's Slack tools), mrkdwn (Slack Web API text) or blocks (Block Kit JSON). Required; never guessed
namesobject–ID to display name map for users, channels and user groups mentioned, when known
reply_broadcastboolean–true when the thread reply will also be shown in the channel
sender_namestring–display name of the sender when known
sourcestring–claude-slack-mcp, slack-web-api or manual; controls which notes are shown
targetstring–destination service; only slack for now (default)
textstring–the message body for markdown/mrkdwn; for blocks, the fallback text used in notifications
thread_tsstring–parent message timestamp when replying in a thread
NameTypeReqDescription
nextstringyeswhat to do next
openedbooleanyestrue when the browser was opened; otherwise ask the user to open path by hand
pathstringyespath of the preview HTML file
warningsnull|arrayyespoints the user must check; empty when none

No examples provided.

Install

How do I install the chat-tool-ui-preview MCP server?

chat-tool-ui-preview ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 86ed2a5d16b6f91fba28fbae9af3be5f8fc3278a0094b8adfc6070814db07ad8; the commands to do that are on this page. If it does not match, do not open it.

mcpb · chat-preview_0.1.1_linux_amd64.mcpb

Download bundle

Check the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.

SHA-256

86ed2a5d16b6f91fba28fbae9af3be5f8fc3278a0094b8adfc6070814db07ad8

macOS / Linux

echo "86ed2a5d16b6f91fba28fbae9af3be5f8fc3278a0094b8adfc6070814db07ad8  chat-preview_0.1.1_linux_amd64.mcpb" | shasum -a 256 -c

Windows (PowerShell)

(Get-FileHash -Algorithm SHA256 .\chat-preview_0.1.1_linux_amd64.mcpb).Hash -eq "86ed2a5d16b6f91fba28fbae9af3be5f8fc3278a0094b8adfc6070814db07ad8"

Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.

Common questions

What is the chat-tool-ui-preview MCP server?

chat-tool-ui-preview is an MCP server listed in the public MCP registry as io.github.gridhra/chat-tool-ui-preview. Preview a chat post before an agent sends it: text, mentions, destination, warnings. Never sends. This page covers its MCPB bundle (https://github.com/gridhra/chat-tool-ui-preview/releases/download/v0.1.1/chat-preview_0.1.1_linux_amd64.mcpb).

Is the chat-tool-ui-preview MCP server safe to use?

chat-tool-ui-preview scores 49 out of 100 on VerifyMCP. Its build provenance is signed and verified. 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 chat-tool-ui-preview MCP server expose?

chat-tool-ui-preview exposes 1 tool: preview_message. Their descriptions and schemas cost roughly 327 tokens of context every time the server is loaded.

What licence is the chat-tool-ui-preview MCP server under?

chat-tool-ui-preview declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.