targetly-mcp

io.github.AbduljabbarBXRPublished by GitHub account AbduljabbarBXRv0.1.4Updated Oct 24, 2026

Deployment truth verification for AI agents. Verifies the live site matches the build.

VerifiedSTDIODesktop onlyCloud & Infrastructure Developer Tools

Server details

Identifier: io.github.AbduljabbarBXR/targetly-mcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 17, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account AbduljabbarBXR for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.AbduljabbarBXR%2Ftargetly-mcp.svg)](https://sourceweft.com/mcp/io.github.AbduljabbarBXR%2Ftargetly-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

targetly-mcp is a local MCP server that lets an assistant verify that a deployed live site matches the build it was produced from.

What you can do: Checks a live site against the build it was produced from, so an assistant can confirm what is actually deployed rather than what was intended to be deployed. Reports whether the live site matches the build, giving the assistant a way to flag drift between the two. The registry description gives no further detail on the checks performed or the sites it can inspect.
When to use it: Use it when you want an assistant to confirm that what is running in production matches the build you expect, for example after a deploy or when investigating whether a live site has drifted from its source.
Requirements: Runs as a local process on the user's machine, installed from the npm package targetly-mcp over stdio. Desktop only; no web executable. No authentication, environment variables or headers are declared.

Before you install

The registry description is brief and no tool list, instructions or README were provided, so the exact checks and any data sent to third parties cannot be confirmed before installing. Review the package before use.

Installation

In SourceWeft

Open targetly-mcp in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.1.4LatestSep 17, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.