targetly-mcp
NPM · TARGETLY-MCP
Deployment truth verification for AI agents. Verifies the live site matches the build.
Available components
Last scanned (21 hours ago)
Scores higher than 66% of npm servers
Category CI/CD and DevOps
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 42 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 317 tokens (~79/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 4 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
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.
- 31 Oct 26 +1
- Stability: 0.97 → pass security
- 30 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 +1
- Stability: 0.97 → pass security
- 22 Oct 26 −1
- Stability: pass → 0.93 functional
- 16 Oct 26 +1
- Stability: 0.97 → pass security
- 14 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 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 83. That category is still filling its 30-day observation window: 22 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.
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 · Analysed npm/targetly-mcp@0.1.4
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
targetly.cache ~55
Inspect the cache headers of a live URL and judge whether a deploy might be hidden behind a cached copy. Reports CDN cache status, cache control, age, and entity tags.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The URL to inspect |
No output schema declared.
No examples provided.
targetly.origin ~67
Resolve where a domain actually serves from. Returns the CNAME chain, A records, the detected platform, and the proxied status, so an agent knows the real origin before deploying.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain to resolve, for example tawakkul-labs.co.ke |
No output schema declared.
No examples provided.
targetly.route ~75
Compare what a domain points at with the deploy tooling present in a build directory. Catches the classic mistake of deploying to a platform that does not serve the domain.
| Name | Type | Req | Description |
|---|---|---|---|
| buildDir | string | – | Local build or project directory to inspect for platform markers |
| domain | string | yes | The domain that should be serving the build |
No output schema declared.
No examples provided.
targetly.verify ~120
Fetch a live URL and check whether it contains the expected markers and none of the forbidden markers. Use this after a deploy to prove the live site is the new build, not a stale one.
| Name | Type | Req | Description |
|---|---|---|---|
| markers | array | – | Strings the live page must contain, for example new feature names or version strings |
| mustNotContain | array | – | Strings that would prove the page is stale, for example old branding or removed names |
| url | string | yes | The URL to fetch, for example https://tawakkul-labs.co.ke/products |
No output schema declared.
No examples provided.
How do I install the targetly-mcp server?
targetly-mcp runs locally as an npm package, launched with npx -y targetly-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · targetly-mcp
claude mcp add abduljabbarbxr-targetly-mcp -- npx -y targetly-mcp
What is the targetly-mcp server?
targetly-mcp is listed in the public MCP registry as io.github.AbduljabbarBXR/targetly-mcp. Deployment truth verification for AI agents. Verifies the live site matches the build. This page covers its npm package (targetly-mcp).
Is the targetly-mcp server safe to use?
targetly-mcp scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. 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 targetly-mcp server expose?
targetly-mcp exposes 4 tools: targetly.origin, targetly.verify, targetly.cache, targetly.route. Their descriptions and schemas cost roughly 317 tokens of context every time the server is loaded.
Is the targetly-mcp server still maintained?
targetly-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.
What licence is the targetly-mcp server under?
targetly-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.