Evercraft Clip
REMOTE · BASE44.APP
Start with plan_clip_job to plan authorized social-video work and route complex media when needed.
Available components
Last scanned (22 hours ago)
Scores higher than 61% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Design and Media
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 Security83
- 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
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability57
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 604 tokens (~201/item across 3 items; 3 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 Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage80
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 41% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
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 →
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.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 −11
- Stability: pass → 0.23 functional
- 11 Nov 26 +58
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 19 Oct 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.73 → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 30 Sept 26 0
- Schema quality: 378 → 604 ▼ functional
- Tool coverage: 100% → 41% ▼ functional
- Server version: 2.0.0 → 2.1.0 functional
- New tool “plan_distribution_campaign” functional
- 29 Sept 26 0
- Tool “plan_clip_job” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Tool coverage: 0% → 100% ▲ functional
- Schema quality: fair → good functional
- “plan_clip_job” reworded the description of “caption_mode” cosmetic
- “plan_clip_job” reworded the description of “complex_media” cosmetic
- “plan_clip_job” reworded the description of “creative_style” cosmetic
- “plan_clip_job” reworded the description of “goal” cosmetic
- “plan_clip_job” reworded the description of “needs_deduplication” cosmetic
- “plan_clip_job” reworded the description of “needs_full_timeline” cosmetic
- “plan_clip_job” reworded the description of “source_duration_seconds” cosmetic
- “plan_clip_job” reworded the description of “source_file_size_bytes” cosmetic
- “plan_clip_job” reworded the description of “target_platforms” cosmetic
- Tool “plan_clip_job” changed its title: Plan an Evercraft Clip social-video job → Start here: plan an Evercraft Clip social-video job cosmetic
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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://base44.app/api/apps/6a83af980c9f995f588c7df3/functions/clipMcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.base44.app | CN=YR2,O=Let's Encrypt,C=US | 11 Nov 2026 | 9 Feb 2027 | RSA 2048 | SHA256-RSA | 60242839d924e3cf2c79a57e3ebe91d4b46 |
| SANs: *.base44.app, base44.app | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of base44.app. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| app. | DS published | 23684 | 8 | Verified |
| base44.app. | DS published | 2371 | 13 | Verified |
| base44.app. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| content-security-policy | script-src 'none'; object-src 'none'; |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://base44.app/api/apps/6a83af980c9f995f588c7df3/functions/clipMcp | Verified | 200 | |
| http (plaintext) | http://base44.app/api/apps/6a83af980c9f995f588c7df3/functions/clipMcp | HTTPS enforced | 301 | https://base44.app/api/apps/6a83af980c9f995f588c7df3/functions/clipMcp |
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 →
get_clip_capabilities Get Evercraft Clip capabilities ~49
Read the current code-backed Evercraft Clip capability boundary, rendering limits, platform lanes, commercial truth, and authority constraints. Use when deciding whether Clip fits a social-video production or governed distribution problem.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
plan_clip_job Start here: plan an Evercraft Clip social-video job ~329
PRIMARY TOOL when the user has authorized source media or a concrete social-video goal. Produces a non-executing Creative Director plan, checks the current 35 MiB bounded customer pipeline, selects creative style and caption treatment, and plans Facebook/LinkedIn/Instagram copy. It recommends ForensiScope upstream for oversized, long, deduplication-heavy, or full-timeline media. Use get_clip_capabilities only for a general capability question. It does not upload media, create an order, charge a user, transfer private media, or publish.
| Name | Type | Req | Description |
|---|---|---|---|
| caption_mode | string | – | Caption treatment to plan for the finished clip. |
| complex_media | boolean | – | Set true for media that needs deeper scene, evidence, or structure analysis before clipping. |
| creative_style | string | – | Preferred creative treatment for the planned edit. |
| goal | string | – | Plain-language outcome the user wants from the social-video job. |
| needs_deduplication | boolean | – | Set true when repeated or near-duplicate segments need to be detected before clip planning. |
| needs_full_timeline | boolean | – | Set true when the job requires understanding the full source timeline rather than only bounded clip selection. |
| source_duration_seconds | number | – | Source media duration in seconds when known. |
| source_file_size_bytes | number | – | Source media file size in bytes when known. Used to detect the current bounded-render limit and recommend ForensiScope when needed. |
| target_platforms | array | – | Desired output platforms, such as YouTube, Instagram, TikTok, Facebook, or LinkedIn. Planning does not publish. |
No output schema declared.
No examples provided.
plan_distribution_campaign Plan an Evercraft Clip cross-platform campaign ~226
Plan one authorized source package as a non-executing Evercraft Clip campaign with an objective, audience intent, CTA or commerce handoff, conversion event, creative treatment, and per-platform derivatives. Use for awareness, education, revenue, lead generation, recruiting, product discovery, retention, or other campaign goals. Facebook, LinkedIn and Instagram have authenticated execution lanes. YouTube can be staged but remains provider-authorization/canary gated. TikTok remains unverified. This tool does not upload media, create checkout, charge, or publish.
| Name | Type | Req | Description |
|---|---|---|---|
| audience_intent | string | – | – |
| campaign_key | string | – | – |
| canonical_url | string | – | – |
| caption_mode | string | – | – |
| commerce_offer_id | string | – | – |
| conversion_event | string | – | – |
| creative_style | string | – | – |
| cta_label | string | – | – |
| cta_url | string | – | – |
| objective | string | – | – |
| source_package_key | string | – | – |
| target_platforms | array | – | – |
| title | string | – | – |
No output schema declared.
No examples provided.
How do I install the Evercraft Clip MCP server?
Evercraft Clip is a hosted endpoint at https://base44.app/api/apps/6a83af980c9f995f588c7df3/functions/clipMcp, 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 · base44.app
claude mcp add --transport http jgaethle10-evercraft-clip 'https://base44.app/api/apps/6a83af980c9f995f588c7df3/functions/clipMcp'
What is the Evercraft Clip MCP server?
Evercraft Clip is an MCP server listed in the public MCP registry as io.github.jgaethle10/evercraft-clip. Start with plan_clip_job to plan authorized social-video work and route complex media when needed. This page covers its hosted endpoint (https://base44.app/api/apps/6a83af980c9f995f588c7df3/functions/clipMcp).
Is the Evercraft Clip MCP server safe to use?
Evercraft Clip scores 74 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 Evercraft Clip MCP server expose?
Evercraft Clip exposes 3 tools: get_clip_capabilities, plan_clip_job, plan_distribution_campaign. Their descriptions and schemas cost roughly 604 tokens of context every time the server is loaded.
Does the Evercraft Clip MCP server require authentication?
No. We connected to Evercraft Clip without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Evercraft Clip MCP server still maintained?
Evercraft Clip 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 Evercraft Clip MCP server?
VerifyMCP ran 13 checks on Evercraft Clip, 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.