VarynForge MCP server
com.varynforge/servervarynforge.comstreamable-httpv1.21.0Scanned
SEO research SaaS exposed as 30+ MCP tools. Forge niche analysis, plans, and writer-ready briefs.
57 tools: 12 can delete or cancel things, 1 do something that can't be undone, 15 change things and 29 only read.
- Reads private data · 4
- Reads text others write · 13
- Can send data out · 5
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
12 tools here can delete or cancel things and 1 does something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the VarynForge MCP server can do
The VarynForge MCP server is published by varynforge.com, a domain the MCP Registry verified. It has 57 tools. It can delete or cancel things (12 tools: update_niche, set_competitor_importance, update_asset_profile, set_posting_cadence and 8 more), do things that cannot be undone, such as sending, paying or publishing (send_feedback) and create or change data (15 tools: create_project, add_destination, add_competitor_by_domain, create_content_plan_from_opportunities and 11 more). 29 tools only read.
4 tools read private data (get_instructions, get_pitch_report_payload, get_starting_point_report and 1 more); 13 tools bring in text other people can write (get_instructions, get_changelog, get_account_status and 10 more); 5 tools can send data out of your system (send_feedback, generate_article_brief, download_brief_markdown and 2 more). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
The fixed checks matched 2 findings (annotation-conflict and long-description). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 14, 2026, version 1.21.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
57 tools
Deletes or cancels 12Claude Code: deny
delete_article_suggestionDelete an article suggestion and its associated brief.No findings
Why it is in this group
- The name "delete_article_suggestion" says "delete": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Delete an article suggestion and its associated brief. Cascades to keyword and cluster links.
Annotations the server declares
- title: Delete article suggestion
- readOnlyHint: false
- destructiveHint: true
mark_article_publishedRecord that an article went live at a URL.No findings
Why it is in this group
- The name "mark_article_published" says "mark": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Record that an article went live at a URL. Flips the suggestion to published, writes the distribution ledger row, stamps the Passport, and pings IndexNow. Call it only once the URL actually resolves — the IndexNow ping fires immediately, and a ping for a dead URL is wasted (search engines crawl, hit the 404, drop it; nothing re-pings later). For a CMS-scheduled article, set scheduledFor via update_article_status and stay in ready_to_publish: publish auto-detect attests it (and pings IndexNow) when it appears. Use this instead of update_article_status for the published transition — a status flip alone records no URL, and without a URL the article is invisible to Search Console outcome tracking (clicks/impressions on the Earnings page). Also works on an already-published suggestion to attach a missing or corrected URL. Pass `publishedAt` (ISO datetime, must not be in the future) when the article went live EARLIER than this call — e.g. attesting after the fact or matching a CMS publish date — so the record carries the real go-live moment instead of the call time.
Annotations the server declares
- title: Mark article published
- readOnlyHint: false
- destructiveHint: true
remap_assetRe-crawl the project website and refresh its owned pages.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe description's first sentence says "crawl": it reads web pages, which anyone can write.
Description, as the server wrote it Re-crawl the project website and refresh its owned pages. Use when get_project_asset shows mappingStatus "error" or owned pages look stale. Rate-limited per site; returns an error naming the wait time if the cooldown is active.
Annotations the server declares
- title: Remap asset
- readOnlyHint: false
- destructiveHint: true
resync_asset_profileRe-read the project website and re-infer the asset profile (name, description, primary offer, benefits, differentiators, use cases) from its current content.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Re-read the project website and re-infer the asset profile (name, description, primary offer, benefits, differentiators, use cases) from its current content. Use before rendering a report when get_pitch_report_payload flags assetProfile.syncedBeforeRun — the stored profile facts may have drifted since they were written. Overwrites the profile facts (fields the site no longer supports inferring are left unchanged, never nulled) and stamps profileSyncedAt; the niche is not touched. Rate-limited per site; returns an error naming the wait time if the cooldown is active.
Annotations the server declares
- title: Resync asset profile
- readOnlyHint: false
- destructiveHint: true
set_competitor_importanceMark a competitor important, default, or ignored.No findings
Why it is in this group
- The name "set_competitor_importance" says "set": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Mark a competitor important, default, or ignored. Important applies a 1.25× boost on opportunity scores for clusters where the competitor ranks top-10. Scores are then normalized 0-100 against the highest-scoring cluster, so other clusters may appear to drop in relative ranking even when their absolute (raw) scores did not change — cross-check via get_opportunity_detail.rawOpportunityScore. Ignored hides the competitor from competitor surfaces and the editorial-score pipeline.
Annotations the server declares
- title: Set competitor importance
- readOnlyHint: false
- destructiveHint: true
set_excluded_termsSet the project-level exclusion terms — products or topics the operator explicitly does NOT sell (e.g.No findings
Why it is in this group
- The name "set_excluded_terms" says "set": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Set the project-level exclusion terms — products or topics the operator explicitly does NOT sell (e.g. "wedding suite", "free template", "printing"). Keywords mentioning any term are down-weighted in opportunity scoring and dropped from the content-plan harvest, before results reach the operator. Replaces the whole list; pass [] to clear. Survives research re-runs, unlike per-cluster dismissal.
Annotations the server declares
- title: Set excluded terms
- readOnlyHint: false
- destructiveHint: true
set_opportunity_statusDismiss or restore an opportunity cluster.No findings
Why it is in this group
- The name "set_opportunity_status" says "set": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Dismiss or restore an opportunity cluster. status=dismissed hides it from list_opportunities and the create_content_plan_from_opportunities harvest; status=default restores it. Dismissal lasts until the next research run rewrites the project clusters — for a durable "not my product" signal use set_excluded_terms. Removing a cluster from the pool changes the 0-100 normalization of every remaining cluster.
Annotations the server declares
- title: Set opportunity status
- readOnlyHint: false
- destructiveHint: true
set_posting_cadenceSet how many articles per week the operator actually publishes (1-14).No findings
Why it is in this group
- The name "set_posting_cadence" says "set": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Set how many articles per week the operator actually publishes (1-14). Sizes the pitch report’s 90-day content sequence; read back via get_project.postsPerWeek.
Annotations the server declares
- title: Set posting cadence
- readOnlyHint: false
- destructiveHint: true
start_research_runStart a research run for a project — discovers keywords, evaluates competitors, and writes opportunity clusters.No findings
Why it is in this group
- The name "start_research_run" says "start": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Start a research run for a project — discovers keywords, evaluates competitors, and writes opportunity clusters. Consumes one credit. Returns `{ runId }`; poll get_research_status for progress. Returns `{ entitlement }` instead when the operator is on the free plan.
Annotations the server declares
- title: Start research run
- readOnlyHint: false
- destructiveHint: true
update_article_statusMove an article through the production pipeline.No findings
Why it is in this group
- The name "update_article_status" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Move an article through the production pipeline. Statuses: planned, generating_brief, brief_ready, drafting, draft_ready, reviewing, ready_to_publish, published. For the published transition use mark_article_published instead — it records the live URL, which Search Console outcome tracking keys off; setting status to published here records no URL. When the article is scheduled to go live later (CMS/external scheduler), pass scheduledFor with the planned date — it shows in the app and holds the "stalled at ready_to_publish" flag until the schedule lapses; do NOT call mark_article_published before the URL is live, publish auto-detect attests it (and pings IndexNow) when it actually appears.
Annotations the server declares
- title: Update article status
- readOnlyHint: false
- destructiveHint: true
update_asset_profileCorrect the inferred profile of the project asset — description, primary offer, benefits, key differentiators, use cases.No findings
Why it is in this group
- The name "update_asset_profile" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Correct the inferred profile of the project asset — description, primary offer, benefits, key differentiators, use cases. Use when get_project_asset shows claims that contradict what the operator actually sells (profileStaleAt set, or the operator says so). Only the fields you pass are written; arrays replace the whole list. No re-crawl happens. Clears the profileStaleAt flag.
Annotations the server declares
- title: Update asset profile
- readOnlyHint: false
- destructiveHint: true
update_nicheUpdate a niche profile — name, industry, language, country, target customer, core problem, related terms.No findings
Why it is in this group
- The name "update_niche" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Update a niche profile — name, industry, language, country, target customer, core problem, related terms. Use after the operator refines their market definition; omitted fields keep their current values.
Annotations the server declares
- title: Update niche
- readOnlyHint: false
- destructiveHint: true
Can't be undone 1Claude Code: ask
send_feedbackFile a note to the VarynForge team: a bug, a missing capability, a friction point, or an operator idea.Can send data outNo findings
Why it is in this group
- The name "send_feedback" says "send": a word for sending, and what is sent cannot be taken back.
What it can reach
- outboundThe name "send_feedback" says "send": it sends or publishes something to other people.
Description, as the server wrote it File a note to the VarynForge team: a bug, a missing capability, a friction point, or an operator idea. Call when you hit something VarynForge cannot do, a confusing tool result, or the operator voices frustration or a wish. Whenever the task would benefit from a capability this tool list does not offer, file a missing_capability BEFORE you settle for a workaround with existing tools, even if they could work as a fallback. Do NOT file entitlement walls (PAYMENT_REQUIRED / RATE_LIMITED / FEATURE_LOCKED payloads) — those are working as designed. Feedback is a note to the team, never a ticket: do not promise the operator it will be fixed. There is no reply — read get_changelog over the following days to see whether the gap closed.
Annotations the server declares
- title: Send feedback
- readOnlyHint: false
- destructiveHint: false
Changes things 15Claude Code: ask
accept_ideaCommit an expanded idea (from expand_idea) to the content plan as a brief-ready article suggestion.No findings
Why it is in this group
- The description's first verb is "commit": a word for a change.
Description, as the server wrote it Commit an expanded idea (from expand_idea) to the content plan as a brief-ready article suggestion. Stores the verbatim idea as provenance, lands the suggestion in generating_brief, and forges its brief automatically (free tier: queues past the daily cap). Returns the new suggestionId.
Annotations the server declares
- title: Accept idea
- readOnlyHint: false
- destructiveHint: false
add_article_suggestionAdd a bare article suggestion to a content plan (title + optional intent and reasoning).No findings
Why it is in this group
- The name "add_article_suggestion" says "add": a word for a change.
Description, as the server wrote it Add a bare article suggestion to a content plan (title + optional intent and reasoning). For richer input that produces a brief-ready suggestion, use create_article_suggestion_with_input.
Annotations the server declares
- title: Add article suggestion
- readOnlyHint: false
- destructiveHint: false
add_competitor_by_domainAdd a competitor to a project by domain (e.g.No findings
Why it is in this group
- The name "add_competitor_by_domain" says "add": a word for a change.
Description, as the server wrote it Add a competitor to a project by domain (e.g. example.com). Marks the competitor as important or ignored on creation.
Annotations the server declares
- title: Add competitor by domain
- readOnlyHint: false
- destructiveHint: false
add_destinationAdd a destination to a project — where the operator publishes.No findings
Why it is in this group
- The name "add_destination" says "add": a word for a change.
Description, as the server wrote it Add a destination to a project — where the operator publishes. Pass `type` (website | youtube_channel | instagram | tiktok | x | linkedin | local_business) and `name` with `state: 'detected'` for a destination that already exists and belongs to the operator (website name = the domain like yourdomain.com; social types = the handle, @ optional), or `state: 'planned'` for one they intend to build (name is held, no live URL yet). Confirm the type and name with the operator before adding — this shapes where briefs, drafts, and lint formats anchor. A project holds up to 10 destinations; manage or remove them in the web UI.
Annotations the server declares
- title: Add destination
- readOnlyHint: false
- destructiveHint: false
add_radar_topicAdd selected angles from a radar topic to the content plan as radar-born article suggestions (provenance preserved; exact-title duplicates skipped).No findings
Why it is in this group
- The name "add_radar_topic" says "add": a word for a change.
Description, as the server wrote it Add selected angles from a radar topic to the content plan as radar-born article suggestions (provenance preserved; exact-title duplicates skipped). Angles come from expand_radar_topic; call list_radar_topics first to get signalObservationId + topicIndex. Auto-creates the content plan when the project has none. Each added suggestion lands in generating_brief and its brief forges automatically (free tier: queues past the daily cap and forges at reset) — do not also call generate_article_brief. Returns the created suggestionIds.
Annotations the server declares
- title: Add radar topic
- readOnlyHint: false
- destructiveHint: false
check_ideaAttach real search data to one article idea that is already in the project — runs one live Google search per target keyword and returns volume bands and the pages currently ranking…No findings
Why it is in this group
- The description's first verb is "attach": a word for a change.
Description, as the server wrote it Attach real search data to one article idea that is already in the project — runs one live Google search per target keyword and returns volume bands and the pages currently ranking for each. Use after create_article_suggestion_with_input, or on any existing suggestion the operator wants judged on data instead of instinct. Opportunity score and cluster placement are returned only when the project has a completed research run to compare against; on a project without one they are absent, and start_research_run is what produces them. Do not use to find new ideas or map a niche — that is start_research_run. Consumes no credits; daily- and monthly-capped per account.
Annotations the server declares
- title: Check idea
- readOnlyHint: false
- destructiveHint: false
create_article_suggestion_with_inputCreate a brief-ready article suggestion from the operator's own input.No findings
Why it is in this group
- The name "create_article_suggestion_with_input" says "create": a word for a change.
Description, as the server wrote it Create a brief-ready article suggestion from the operator's own input. Auto-resolves a default content plan; creates/links search-query rows for the keywords; returns suggestionId + contentPlanId. Free-tier compatible (no research run required).
Annotations the server declares
- title: Create article suggestion with input
- readOnlyHint: false
- destructiveHint: false
create_content_plan_from_opportunitiesCreate a content plan by harvesting the top-30 opportunity clusters from a completed research run.No findings
Why it is in this group
- The name "create_content_plan_from_opportunities" says "create": a word for a change.
Description, as the server wrote it Create a content plan by harvesting the top-30 opportunity clusters from a completed research run. Auto-creates article suggestions linked to each cluster. Left out of the harvest: dismissed clusters (set_opportunity_status), keywords matching the project exclusion terms (set_excluded_terms), and clusters the site already covers (>=80% of keywords covered — refresh work on existing pages surfaces via editorial scores, not here).
Annotations the server declares
- title: Create content plan from opportunities
- readOnlyHint: false
- destructiveHint: false
create_projectCreate a new project — pass either a website URL or a niche description (or both).No findings
Why it is in this group
- The name "create_project" says "create": a word for a change.
Description, as the server wrote it Create a new project — pass either a website URL or a niche description (or both). Returns projectId immediately; niche analysis and asset mapping run async. Poll get_project until niche.analysisStatus is ready. When the operator says whose site this is, pass siteRelation: mine (their own), client (an existing client), or prospect (a site they are pitching) — ask only if it is ambiguous, never guess. Optionally pass organizationId (see list_organizations) to create the project in a specific organization; it defaults to the personal organization.
Annotations the server declares
- title: Create project
- readOnlyHint: false
- destructiveHint: false
download_brief_markdownGet a brief as inline markdown the host agent can use as a writing prompt.Can send data out1 finding
Why it is in this group
- The description's first verb is "get": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
What it can reach
- outboundThe input takes a destination (input.channel): what the tool writes goes there.
Findings
- Warn
The server marks "download_brief_markdown" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false}; The description's first verb is "get": a word for reading.
Description, as the server wrote it Get a brief as inline markdown the host agent can use as a writing prompt. Pass format=markdown_inline, and `channel` (article default) to pick which of the suggestion’s per-channel briefs to render. Returns the brief assembled into a single markdown string capped at ~8K chars — markdown only; the structured fields are get_article_brief’s job and are omitted here.
Annotations the server declares
- title: Download brief markdown
- readOnlyHint: false
- destructiveHint: false
expand_ideaScore a raw article idea against the project's niche without writing anything to the plan.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Score a raw article idea against the project's niche without writing anything to the plan. Returns a title, angle, search intent, related queries, a coarse demand estimate, and a 0-100 niche-fit score. Pass the returned fields to accept_idea to commit the idea as a brief-ready suggestion.
Annotations the server declares
- title: Expand idea
- readOnlyHint: false
- destructiveHint: false
expand_radar_topicExpand one radar topic (by signalObservationId + topicIndex from list_radar_topics) into 3-6 candidate article angles with title, intent, and editorial positioning; each angle is f…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Expand one radar topic (by signalObservationId + topicIndex from list_radar_topics) into 3-6 candidate article angles with title, intent, and editorial positioning; each angle is flagged when a near-duplicate already exists in the content plan. Optionally pass customPov for angles from a specific point of view. No writes — pass chosen angles to add_radar_topic.
Annotations the server declares
- title: Expand radar topic
- readOnlyHint: false
- destructiveHint: false
generate_article_briefForge a writer-ready brief from an article suggestion.Can send data outNo findings
Why it is in this group
- The name "generate_article_brief" says "generate": a word for a change.
What it can reach
- outboundThe input takes a destination (input.channel): what the tool writes goes there.
Description, as the server wrote it Forge a writer-ready brief from an article suggestion. `channel` picks the brief template: article (default, SEO article outline), reels (hook/beats/shot list), youtube (retention beats/chapters), x (thread posts), linkedin (carousel slide deck: cover hook, one-idea slides, recap, CTA). A suggestion holds one brief per channel — generating a second channel adds a brief without touching the others. When the suggestion already has an article brief, channel briefs DERIVE from it (its key points, hook, and keyStats flow into the channel shape) and are free — they do not consume a daily brief slot. Idempotent per channel: if that channel already has a brief, returns it without consuming a slot; pass `force: true` to regenerate it. When regenerating, pass `guidance` — corrective direction the forge must follow (e.g. the angle the operator actually wants, a section to drop, an audience correction) — instead of re-rolling blind and hoping. Free tier: 10/day for article briefs and non-derived channel briefs. Returns `{ entitlement }` when the daily cap is reached.
Annotations the server declares
- title: Generate article brief
- readOnlyHint: false
- destructiveHint: false
lint_draftSubmit a draft for verification against its brief.Can send data out1 finding
Why it is in this group
- The description's first verb is "submit": a word for a change.
What it can reach
- outboundThe input takes a destination (input.channel): what the tool writes goes there.
Findings
- Info
The description is 2,168 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...et_account_status limits); re-submitting an unchanged draft is served from cache."
Description, as the server wrote it Submit a draft for verification against its brief. Returns a pass/flag verdict with per-check detail. Pass moves the article to ready_to_publish; flag moves it to draft_ready for revision. `channel` (article | reels | youtube | x | linkedin) declares WHICH of the suggestion's per-channel briefs the draft is graded against AND the submission shape — always pass it for non-article content; when omitted, the channel is inferred from `format`. Submission shapes (get_lint_rubric returns the same spec + the numeric limits): article = markdown draft; x = thread text with one post per --- separated section, NO links in post bodies (put links in a reply); linkedin = post/caption text first, optional --- separated carousel slides after, NO links in the body (put links in the first comment); reels/youtube = the production SCRIPT — the process is brief -> script -> video, this gate validates the script, and the video is produced after it passes (published URL is recorded at publish time, not here). `format` labels the storage destination: prefer one of the project's destination type ids (see list_destinations) so receipts and drafts group per destination — re-submitting the same `format` replaces that destination's draft, a different `format` keeps both. The response reports the suggestion's post-lint `status` and a `nextAction` hint; `thresholds` is the article ratio block on the article channel and null otherwise (channel limits live in get_lint_rubric checkParams). `waiveChecks` marks check ids the OPERATOR deliberately deviates from (e.g. a brief section they dropped on purpose): waived checks still run and are recorded as waived in the receipt, but no longer fail the verdict — only pass ids the operator explicitly waived, never waive on your own initiative. Verdicts and drafts are stored per `format` and re-readable any time via get_draft_status (free — never re-lint to recover a lost verdict). Status transitions are forward-only: a flagged re-submit never demotes a suggestion already at ready_to_publish or published. Daily-capped (cap and remaining are in get_account_status limits); re-submitting an unchanged draft is served from cache.
Annotations the server declares
- title: Lint draft
- readOnlyHint: false
- destructiveHint: false
register_derived_assetRegister a derived asset (LinkedIn carousel PDF, social post, video, image) produced from an article suggestion.Can send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- outboundThe input takes a destination (input.channel): what the tool writes goes there.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Register a derived asset (LinkedIn carousel PDF, social post, video, image) produced from an article suggestion. Appends a distribution-ledger row so the suggestion shows everything it produced — the article plus its derivatives — for content-ROI reporting (get_article_suggestion returns them as derivedAssets). Pass `channel` (reels | youtube | x | linkedin) so the app can show per-channel distribution status; register again with a new URL for repeat posts on the same channel — every registration is kept. `scheduledFor` records a future post date from an external scheduler (Buffer etc.) for display only — VarynForge never posts on your behalf. Derivative rows never affect publish status or Search Console attribution; use mark_article_published for the article itself.
Annotations the server declares
- title: Register derived asset
- readOnlyHint: false
- destructiveHint: false
Only reads 29Show 29 read-only tools
get_account_statusGet the operator account status — the organization whose plan/credits/limits this payload describes (plans and usage limits are per-organization; see list_organizations), current p…Reads text others writeNo findings
Why it is in this group
- The name "get_account_status" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "get" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it Get the operator account status — the organization whose plan/credits/limits this payload describes (plans and usage limits are per-organization; see list_organizations), current plan, available credits, brief quota state, the lint_draft daily verification cap (applies on every tier; check lint_drafts_remaining_today before a verification loop), the idea_checks allowance (check_idea is daily- AND monthly-capped on every tier; check remaining before a check loop), locked paid tools, the upgrade URL, and next_actions: the ranked cross-project queue of what to do next. Defaults to the personal organization; pass organizationId when working a project that belongs to a different organization — its shared caps are the ones project actions consume. Read on session start and after a wall hit.
Annotations the server declares
- title: Get account status
- readOnlyHint: true
get_article_briefGet the full content brief for an article suggestion.No findings
Why it is in this group
- The name "get_article_brief" says "get": a word for reading.
Description, as the server wrote it Get the full content brief for an article suggestion. A suggestion holds one brief per channel — pass `channel` (article default | reels | youtube | x | linkedin) to pick which. Every brief carries hookStatement (one verbatim-usable hook sentence naming the reader payoff); article briefs also carry keyStats (a stat bank of { claim, value, source, sourceUrl } entries for evidence blocks and data slides). Pass compact=true to drop referenceArticles (informational only). internalLinks, curatedTargetQueries, and targetKeywords always populate. When the requested channel's brief does not exist yet, returns { hasBrief: false, briefStatus: 'queued' | 'forging' | 'none', queuedUntil } — 'queued' means the forge is waiting for the free daily cap to reset at queuedUntil; poll after that moment.
Annotations the server declares
- title: Get article brief
- readOnlyHint: true
get_article_suggestionGet article suggestion details — metadata, cluster context, brief availability, registered derived assets (carousels, social posts), target keywords with volumes.Reads text others writeNo findings
Why it is in this group
- The name "get_article_suggestion" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "get" and "post": it reads posts, which other people can write.
Description, as the server wrote it Get article suggestion details — metadata, cluster context, brief availability, registered derived assets (carousels, social posts), target keywords with volumes. Call get_article_brief for the full brief. Status semantics: generating_brief with briefQueuedAt set means the brief is QUEUED behind the free daily cap (forges automatically at reset); briefQueuedAt null means actively forging.
Annotations the server declares
- title: Get article suggestion
- readOnlyHint: true
get_changelogGet the URL of the VarynForge product changelog — what shipped, newest first, in plain markdown.Reads text others writeNo findings
Why it is in this group
- The name "get_changelog" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "get" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it Get the URL of the VarynForge product changelog — what shipped, newest first, in plain markdown. Fetch it when the operator asks what is new, and in the days after a send_feedback report to check whether the gap they hit has been closed.
Annotations the server declares
- title: Get changelog
- readOnlyHint: true
get_competitor_detailGet a competitor company detail in a project context — domain, name, importance, top pages in the project SERPs, and top keywords they rank for.No findings
Why it is in this group
- The name "get_competitor_detail" says "get": a word for reading.
Description, as the server wrote it Get a competitor company detail in a project context — domain, name, importance, top pages in the project SERPs, and top keywords they rank for.
Annotations the server declares
- title: Get competitor detail
- readOnlyHint: true
get_draft_statusRe-read an article suggestion's verification state without re-linting: the suggestion's single pipeline status plus, per destination `format`, the stored draft and the latest gate …No findings
Why it is in this group
- The name "get_draft_status" says "get": a word for reading.
Description, as the server wrote it Re-read an article suggestion's verification state without re-linting: the suggestion's single pipeline status plus, per destination `format`, the stored draft and the latest gate receipt (verdict, per-check detail, thresholds) from its last lint_draft submission. Free and uncapped — always use this instead of lint_draft to recover a known verdict. Pass `format` to read one destination including the stored draft text; omit it for the per-destination overview (receipts only, no draft bodies). Status-ownership model: ONE suggestion status drives the pipeline while verdicts are per-destination (N receipts), and status transitions are forward-only — a later flagged submission on one destination never demotes a suggestion another destination already moved to ready_to_publish.
Annotations the server declares
- title: Get draft status
- readOnlyHint: true
get_instructionsGet the VarynForge agent guide — workflow paths (free vs paid), token-economy rules, walls and upgrade conversation conventions.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_instructions" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "get" and "conversation": it reads messages.
- untrusted-inputThe description's first sentence says "get" and "conversation": it reads messages, which other people can write.
Description, as the server wrote it Get the VarynForge agent guide — workflow paths (free vs paid), token-economy rules, walls and upgrade conversation conventions. Read this at session start.
Annotations the server declares
- title: Get instructions
- readOnlyHint: true
get_keyword_detailGet a keyword detail — pages ranking for it with positions and ownership, plus related keywords already tracked in the project.No findings
Why it is in this group
- The name "get_keyword_detail" says "get": a word for reading.
Description, as the server wrote it Get a keyword detail — pages ranking for it with positions and ownership, plus related keywords already tracked in the project.
Annotations the server declares
- title: Get keyword detail
- readOnlyHint: true
get_lint_rubricGet the verification rubric for an article suggestion: the submission format for the channel (markdown | --- separated thread | post-with-slides | production script), required vs a…Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_lint_rubric" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "get" and "thread": it reads messages.
- untrusted-inputThe description's first sentence says "get" and "thread": it reads messages, which other people can write.
Description, as the server wrote it Get the verification rubric for an article suggestion: the submission format for the channel (markdown | --- separated thread | post-with-slides | production script), required vs advisory checks, the exact numeric limits each check grades against (checkParams), plus the brief fields lint_draft reads (keywords, outline, FAQ, channel payload). Pass `channel` to read the rubric of that channel's brief (article default) — use the same channel you will pass to lint_draft. Fetch this before writing so the draft passes on the first submission.
Annotations the server declares
- title: Get lint rubric
- readOnlyHint: true
get_onboarding_guideDiagnose where the operator is in their VarynForge journey and get a guided setup path.No findings
Why it is in this group
- The name "get_onboarding_guide" says "get": a word for reading.
Description, as the server wrote it Diagnose where the operator is in their VarynForge journey and get a guided setup path. Call when the operator asks to set up VarynForge, get started, or seems unsure what to do next — and always when list_projects returns empty. Returns the server-derived stage, a stage-tailored pitch to relay to the operator, a setup checklist with done/pending status per step, and the ranked next_actions queue. Diagnose before prescribing: never run the welcome pitch on an operator whose stage says producing.
Annotations the server declares
- title: Get onboarding guide
- readOnlyHint: true
get_opportunity_detailGet a cluster detail — top-20 keywords by score, top-10 ranked pages by position, top-5 competitor podium, linked article suggestions, and rawOpportunityScore (un-normalized; list_…No findings
Why it is in this group
- The name "get_opportunity_detail" says "get": a word for reading.
Description, as the server wrote it Get a cluster detail — top-20 keywords by score, top-10 ranked pages by position, top-5 competitor podium, linked article suggestions, and rawOpportunityScore (un-normalized; list_opportunities returns the 0-100 normalized version).
Annotations the server declares
- title: Get opportunity detail
- readOnlyHint: true
get_page_dossierGet a page dossier — URL, title, project rankings, ownership.Reads text others writeNo findings
Why it is in this group
- The name "get_page_dossier" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "get" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it Get a page dossier — URL, title, project rankings, ownership. `headingOutline`, `targetKeywords`, and `contentAnalysis` populate for owned (asset-mapped) pages only.
Annotations the server declares
- title: Get page dossier
- readOnlyHint: true
get_pitch_report_payloadAssemble the client-ready pitch report payload for a completed research run — niche + solution profile, competitor landscape, ranked opportunity map holding GAPS ONLY (0-100 normal…Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_pitch_report_payload" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "note": it reads notes.
- untrusted-inputThe description's first sentence says "post": it reads posts, which other people can write.
Description, as the server wrote it Assemble the client-ready pitch report payload for a completed research run — niche + solution profile, competitor landscape, ranked opportunity map holding GAPS ONLY (0-100 normalized; demand sized as volumeBucket buckets, no search-volume numbers by design; each entry carries overlapStatus net_new|partial plus siteOverlap — covered-keyword share + closest owned pages), coveredOpportunities as a separate defend-and-refresh list (topics the site already covers — never pitch these as new work), and a derived 90-day content sequence sized to the project posting cadence (postsPerWeek, up to 12 weeks; planned articles first, then gap topics marked type: topic — topics to develop, not article titles; covered clusters never enter the sequence; entries may carry advisory notes — near-duplicates, already-published near-matches, working titles needing a rewrite — keep the notes visible when rendering). assetProfile reports when the profile facts were last synced; when assetProfile.syncedBeforeRun is true, offer the operator the choice between resync_asset_profile first and rendering with the profile as-is, and always render the "Asset profile last synced <date>" stamp. renderGuide carries the full report structure with an explicit branding slot: render it in the operator’s own template (Docs, Slides, Notion, or PDF) under the operator’s name. Included with every run, no extra cost. Pass the runId from get_research_status; a run that is not completed returns { runStatus, report: null }.
Annotations the server declares
- title: Get pitch report payload
- readOnlyHint: true
get_projectGet one project — its canonical name (operator-set, falling back to site brand then niche name), niche profile, target audience, current research status, and postsPerWeek (the oper…Reads text others writeNo findings
Why it is in this group
- The name "get_project" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "get" and "post": it reads posts, which other people can write.
Description, as the server wrote it Get one project — its canonical name (operator-set, falling back to site brand then niche name), niche profile, target audience, current research status, and postsPerWeek (the operator’s publishing cadence, settable via set_posting_cadence; sizes the pitch report’s 90-day sequence). Address the project by `name`; `niche.name` is the market niche, not the project name.
Annotations the server declares
- title: Get project
- readOnlyHint: true
get_project_assetGet the asset (website/product) associated with a project — URL, name, description, solution profile.Reads text others writeNo findings
Why it is in this group
- The name "get_project_asset" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "get" and "website": it reads web pages, which anyone can write.
Description, as the server wrote it Get the asset (website/product) associated with a project — URL, name, description, solution profile.
Annotations the server declares
- title: Get project asset
- readOnlyHint: true
get_project_overviewGet the at-a-glance read on a project — niche summary, keyword stats, nextActions (the ranked queue of what to do next in this project — offer its first entry when the operator ask…No findings
Why it is in this group
- The name "get_project_overview" says "get": a word for reading.
Description, as the server wrote it Get the at-a-glance read on a project — niche summary, keyword stats, nextActions (the ranked queue of what to do next in this project — offer its first entry when the operator asks "what now?"), and topPriorities: the ranked queue of article suggestions (best first — priorityScore desc; radar-born suggestions carry no score until briefed and rank oldest-first below scored ones; source tells you why score/cluster may be null). Entries already at ready_to_publish or published are done, not next — "do the next piece" = the first entry whose status still needs work (planned, brief_ready, drafting, draft_ready, reviewing).
Annotations the server declares
- title: Get project overview
- readOnlyHint: true
get_research_statusPoll the latest research run for a project — runId, status, current pipeline phase, progress percent, elapsed seconds, and structured failure diagnostics when failed.No findings
Why it is in this group
- The name "get_research_status" says "get": a word for reading.
Description, as the server wrote it Poll the latest research run for a project — runId, status, current pipeline phase, progress percent, elapsed seconds, and structured failure diagnostics when failed. failure carries failureClass (upstream_timeout | upstream_rate_limited | invalid_input | internal | unknown), the phase the run died in, retryable (true = transient upstream issue, safe to retry; false = retrying will fail again — fix inputs or report it; null = unknown, retry at most once before reporting), and the raw message. A running run with phase "initializing" and large elapsedSeconds is stalled, not queued — report it instead of waiting. Token-light: returns a small fixed shape, no step payloads.
Annotations the server declares
- title: Get research status
- readOnlyHint: true
get_starting_point_reportGet the free starting-point report for a project — a client-facing document assembled from setup-time data: positioning (niche + market profile), the site and its current content i…Reads private dataNo findings
Why it is in this group
- The name "get_starting_point_report" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "get" and "document": it reads documents.
Description, as the server wrote it Get the free starting-point report for a project — a client-facing document assembled from setup-time data: positioning (niche + market profile), the site and its current content inventory, the curated competitor set, and early rising-topic signals. Free on every plan, no research run required. markdown is the ready-to-send render; the structured fields are the same data for custom rendering. lockedSections names the sections a research run adds (full opportunity map, 90-day sequence, competitor gap analysis) — absent here, not previewed. Once the project has a completed run, prefer get_pitch_report_payload: that is the full report.
Annotations the server declares
- title: Get starting point report
- readOnlyHint: true
get_write_handoffOne-call writer handoff: returns a compact writing payload for an article suggestion (brief essentials, keywords, acceptance criteria, lint instructions).No findings
Why it is in this group
- The name "get_write_handoff" says "get": a word for reading.
Description, as the server wrote it One-call writer handoff: returns a compact writing payload for an article suggestion (brief essentials, keywords, acceptance criteria, lint instructions). Compact by design — FAQs cap at 6 and long sections degrade to fit a deep-link budget; the FULL brief is get_article_brief and the full check list is get_lint_rubric, so verify against those, not this. deepLinks (ChatGPT/Claude URLs embedding the payload) is null over MCP — it exists for web users without a connected agent.
Annotations the server declares
- title: Get write handoff
- readOnlyHint: true
get_writer_system_promptGet the writer system prompt for drafting one content type from its brief.No findings
Why it is in this group
- The name "get_writer_system_prompt" says "get": a word for reading.
Description, as the server wrote it Get the writer system prompt for drafting one content type from its brief. The writer works with your Varyn account context: every channel prompt binds to the brief, its acceptance rubric, and the opportunity behind the brief fetched from the account, and degrades to generic writing advice without them. Pass `channel` (article | x | linkedin | reels | youtube) — each channel has its own methodology: article covers voice adaptation, structure rules, and the acceptance checklist; x covers thread mechanics; linkedin covers post + carousel slides; reels and youtube cover the production script (brief -> script -> video). Load the prompt for the channel you are about to draft; article is the default.
Annotations the server declares
- title: Get writer system prompt
- readOnlyHint: true
list_article_suggestionsList article suggestions for a project — title, status, priority, cluster, intent, source, publishedAt, scheduledFor, and a per-channel distributions rollup ({ channel, count, late…No findings
Why it is in this group
- The name "list_article_suggestions" says "list": a word for reading.
Description, as the server wrote it List article suggestions for a project — title, status, priority, cluster, intent, source, publishedAt, scheduledFor, and a per-channel distributions rollup ({ channel, count, latestAt, scheduledFor } per channel the content went out on). Use distributions to spot gaps from the list alone — e.g. items with no linkedin entry have no LinkedIn post yet — without per-item reads. Page through suggestions; call get_article_suggestion for the full record. Status semantics: generating_brief with briefQueuedAt set means the brief is QUEUED behind the free daily cap and forges automatically at cap reset (get_article_brief returns queuedUntil); generating_brief with briefQueuedAt null means it is actively forging — re-check within a minute.
Annotations the server declares
- title: List article suggestions
- readOnlyHint: true
list_competitorsList companies for a project — marked competitors (important / default / ignored) and SERP-discovered companies (unmarked).No findings
Why it is in this group
- The name "list_competitors" says "list": a word for reading.
Description, as the server wrote it List companies for a project — marked competitors (important / default / ignored) and SERP-discovered companies (unmarked). Sorted important → default → unmarked → ignored, then by domain. Pass `importance` to filter to one bucket. Capped at 100.
Annotations the server declares
- title: List competitors
- readOnlyHint: true
list_destinationsList the project's destinations — where the operator publishes (website, youtube_channel, tiktok, instagram, x, linkedin, local_business).Reads text others writeNo findings
Why it is in this group
- The name "list_destinations" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "list" and "website": it reads web pages, which anyone can write.
Description, as the server wrote it List the project's destinations — where the operator publishes (website, youtube_channel, tiktok, instagram, x, linkedin, local_business). Destination type ids are the `format` labels lint_draft stores drafts under. Each row carries its capabilities so you never cross-reference other tools: `briefChannel` is the brief/lint channel the type maps onto (null for open slots), `verifiable` says lint_draft can grade drafts for it, `publishable` says it is live and its published URLs can be recorded, and `publishVia` names the recording tool (mark_article_published for article-channel destinations, register_derived_asset for social/video; null while planned). An empty list means the operator has not configured destinations — add one with add_destination, or fall back to the brief channel name as the lint_draft `format` label.
Annotations the server declares
- title: List destinations
- readOnlyHint: true
list_keywordsList keywords tracked for a project — text, difficulty, intent, volume bucket (no_traffic | long_tail | average | high).No findings
Why it is in this group
- The name "list_keywords" says "list": a word for reading.
Description, as the server wrote it List keywords tracked for a project — text, difficulty, intent, volume bucket (no_traffic | long_tail | average | high). Paginated; supports sorting and intent filter.
Annotations the server declares
- title: List keywords
- readOnlyHint: true
list_opportunitiesList content opportunity clusters sorted by opportunity score.No findings
Why it is in this group
- The name "list_opportunities" says "list": a word for reading.
Description, as the server wrote it List content opportunity clusters sorted by opportunity score. Goal filters: fast_wins, high_intent, authority_building, competitor_gap. coverage filters by site-coverage status and defaults to ["gap","partial"] — clusters the site already COVERS (ranks top-10 for a cluster keyword) are hidden unless "covered" is included (refresh candidates). Dismissed clusters (set_opportunity_status) are hidden, and keywords matching the project exclusion terms (set_excluded_terms) down-weight their cluster scores. Clusters flagged by the asset-fit assessment (fitFlag unservable_feature | off_catalog, with fitReason explaining why) are down-weighted rather than hidden — treat them as comparison-content candidates at best, never headline opportunities. Scores are normalized 0-100 against the highest-scoring visible cluster, so coverage filtering, dismissing, excluding, or fit-flagging can shift the relative numbers of other clusters.
Annotations the server declares
- title: List opportunities
- readOnlyHint: true
list_organizationsList the organizations this account belongs to — id, name, your role (owner | admin | member), is_personal, plan, and member_count — plus pending invitations awaiting a response (a…Reads text others writeNo findings
Why it is in this group
- The name "list_organizations" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "list" and "web": it reads web pages, which anyone can write.
Description, as the server wrote it List the organizations this account belongs to — id, name, your role (owner | admin | member), is_personal, plan, and member_count — plus pending invitations awaiting a response (accept them in the web app). Plans, credits, and usage limits are per-organization, and a project belongs to exactly one organization. Pass an organizationId to create_project to target a specific organization, or to get_account_status to read that organization’s caps.
Annotations the server declares
- title: List organizations
- readOnlyHint: true
list_pagesList ranked pages tracked for a project — URL, title, company, query count, ownership.Reads text others writeNo findings
Why it is in this group
- The name "list_pages" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "list" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it List ranked pages tracked for a project — URL, title, company, query count, ownership. Filter by ownership or company domain.
Annotations the server declares
- title: List pages
- readOnlyHint: true
list_projectsList all projects for the authenticated operator — paginated, sortable by createdAt, niche, or industry.No findings
Why it is in this group
- The name "list_projects" says "list": a word for reading.
Description, as the server wrote it List all projects for the authenticated operator — paginated, sortable by createdAt, niche, or industry. `name` is the canonical project name (operator-set, falling back to site brand then niche name) — match operator references against it; `niche.name` is the market niche, distinct metadata. lastActivityAt is the most recent change to the project or any of its content pieces — when the operator says "my project" without naming one, the highest lastActivityAt is the right pick.
Annotations the server declares
- title: List projects
- readOnlyHint: true
list_radar_topicsList the latest emergent-topic radar snapshot for a project: rising narrative topics (label, summary, momentum, novelty, drivers, evidence) with per-topic index and how many articl…No findings
Why it is in this group
- The name "list_radar_topics" says "list": a word for reading.
Description, as the server wrote it List the latest emergent-topic radar snapshot for a project: rising narrative topics (label, summary, momentum, novelty, drivers, evidence) with per-topic index and how many article suggestions were already added from each. Returns null when the project has no radar snapshot yet. Use expand_radar_topic to turn a topic into article angles.
Annotations the server declares
- title: List radar topics
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
260 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 4 private-data tools breaks every one.
- Reads private data4
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write13
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out5
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__varynforge__get_instructions",
"mcp__varynforge__get_lint_rubric",
"mcp__varynforge__get_pitch_report_payload",
"mcp__varynforge__get_starting_point_report"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:49 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 28
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://app.varynforge.com/.well-known/oauth-protected-resource/api/mcp
- Authorization servers
- https://app.varynforge.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 28 tools that change things (12 destructive, 1 irreversible, 15 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://app.varynforge.com/api/mcp: tools/list returned 57 tools to an anonymous client, including update_niche (destructive), set_competitor_importance (destructive), update_asset_profile (destructive), set_posting_cadence (destructive), resync_asset_profile (destructive) and 23 more
Findings
Matches of fixed checks, with the text they matched.
The server marks "download_brief_markdown" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false}; The description's first verb is "get": a word for reading.
- Infolint_draft
The description is 2,168 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...et_account_status limits); re-submitting an unchanged draft is served from cache."
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.21.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http varynforge https://app.varynforge.com/api/mcpclaude mcp add --transport http varynforge https://app.varynforge.com/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__varynforge__get_instructions",
"mcp__varynforge__get_changelog",
"mcp__varynforge__get_writer_system_prompt",
"mcp__varynforge__get_account_status",
"mcp__varynforge__list_organizations",
"mcp__varynforge__get_onboarding_guide",
"mcp__varynforge__get_project",
"mcp__varynforge__get_project_asset",
"mcp__varynforge__list_destinations",
"mcp__varynforge__list_competitors",
"mcp__varynforge__list_projects",
"mcp__varynforge__get_competitor_detail",
"mcp__varynforge__get_project_overview",
"mcp__varynforge__get_research_status",
"mcp__varynforge__get_pitch_report_payload",
"mcp__varynforge__get_starting_point_report",
"mcp__varynforge__list_opportunities",
"mcp__varynforge__get_opportunity_detail",
"mcp__varynforge__list_keywords",
"mcp__varynforge__get_keyword_detail",
"mcp__varynforge__list_pages",
"mcp__varynforge__get_page_dossier",
"mcp__varynforge__list_article_suggestions",
"mcp__varynforge__get_article_suggestion",
"mcp__varynforge__get_draft_status",
"mcp__varynforge__get_article_brief",
"mcp__varynforge__get_lint_rubric",
"mcp__varynforge__get_write_handoff",
"mcp__varynforge__list_radar_topics"
],
"ask": [
"mcp__varynforge__send_feedback",
"mcp__varynforge__create_project",
"mcp__varynforge__add_destination",
"mcp__varynforge__add_competitor_by_domain",
"mcp__varynforge__create_content_plan_from_opportunities",
"mcp__varynforge__add_article_suggestion",
"mcp__varynforge__create_article_suggestion_with_input",
"mcp__varynforge__generate_article_brief",
"mcp__varynforge__download_brief_markdown",
"mcp__varynforge__register_derived_asset",
"mcp__varynforge__lint_draft",
"mcp__varynforge__expand_idea",
"mcp__varynforge__accept_idea",
"mcp__varynforge__check_idea",
"mcp__varynforge__expand_radar_topic",
"mcp__varynforge__add_radar_topic"
],
"deny": [
"mcp__varynforge__update_niche",
"mcp__varynforge__set_competitor_importance",
"mcp__varynforge__update_asset_profile",
"mcp__varynforge__set_posting_cadence",
"mcp__varynforge__resync_asset_profile",
"mcp__varynforge__remap_asset",
"mcp__varynforge__start_research_run",
"mcp__varynforge__set_opportunity_status",
"mcp__varynforge__set_excluded_terms",
"mcp__varynforge__update_article_status",
"mcp__varynforge__delete_article_suggestion",
"mcp__varynforge__mark_article_published"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as varynforge. Review it before you use it.
Capability tags behind 19 rules
- mcp__varynforge__get_instructions private-data, untrusted-input
- mcp__varynforge__get_changelog untrusted-input
- mcp__varynforge__get_account_status untrusted-input
- mcp__varynforge__list_organizations untrusted-input
- mcp__varynforge__send_feedback outbound
- mcp__varynforge__get_project untrusted-input
- mcp__varynforge__get_project_asset untrusted-input
- mcp__varynforge__list_destinations untrusted-input
- mcp__varynforge__remap_asset untrusted-input
- mcp__varynforge__get_pitch_report_payload private-data, untrusted-input
- mcp__varynforge__get_starting_point_report private-data
- mcp__varynforge__list_pages untrusted-input
- mcp__varynforge__get_page_dossier untrusted-input
- mcp__varynforge__generate_article_brief outbound
- mcp__varynforge__get_article_suggestion untrusted-input
- mcp__varynforge__download_brief_markdown outbound
- mcp__varynforge__register_derived_asset outbound
- mcp__varynforge__get_lint_rubric private-data, untrusted-input
- mcp__varynforge__lint_draft outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.varynforge/server/verify?hash=c1c5ac11bb97d9bed83a1633df96ae7c4223e91faef4dd484d91b9cc05d8a2a8" | jq -e '.changed == false'Pinned hash c1c5ac11bb97, from Nov 14, 2026, 17:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.varynforge/server/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.varynforge/server)Source: MCP Registry. Synced Oct 21, 2026, 18:10 UTC.
VarynForge MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the VarynForge MCP server safe?
- No scan can promise that. What its definitions show: 57 tools, 28 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the VarynForge MCP server delete data?
- Yes. 12 tools can delete, cancel or revoke something: update_niche, set_competitor_importance, update_asset_profile, set_posting_cadence, resync_asset_profile, remap_asset and 6 more.
Can the VarynForge MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: send_feedback.
What tools does the VarynForge MCP server have?
- 57 tools: 12 destructive, 1 irreversible, 15 write, 29 read. update_niche, set_competitor_importance, update_asset_profile, set_posting_cadence, resync_asset_profile, remap_asset, start_research_run, set_opportunity_status and 49 more.
Does the VarynForge MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the VarynForge MCP server send data to outside services?
- 5 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): send_feedback, generate_article_brief, download_brief_markdown, register_derived_asset and lint_draft.
Has the VarynForge MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 14, 2026.