VarynForge
REMOTE · APP.VARYNFORGE.COM · SCANNED SEP 20
SEO research SaaS exposed as 30+ MCP tools. Forge niche analysis, plans, and writer-ready briefs.
Available components
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 Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 9371 tokens (~164/item across 57 items; 57 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 Management50
- Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 57 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage75
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 26% 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
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 57 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
How do I install the VarynForge MCP server?
VarynForge is a hosted endpoint at https://app.varynforge.com/api/mcp, 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 · app.varynforge.com
claude mcp add --transport http com-varynforge-server 'https://app.varynforge.com/api/mcp'
{
"mcpServers": {
"com-varynforge-server": {
"url": "https://app.varynforge.com/api/mcp"
}
}
} {
"servers": {
"com-varynforge-server": {
"type": "http",
"url": "https://app.varynforge.com/api/mcp"
}
}
} [mcp_servers.com-varynforge-server] url = "https://app.varynforge.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-varynforge-server": {
"type": "remote",
"url": "https://app.varynforge.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-varynforge-server --url 'https://app.varynforge.com/api/mcp' --transport streamable-http
mcp_servers:
com-varynforge-server:
url: "https://app.varynforge.com/api/mcp" {
"McpServers": {
"com-varynforge-server": {
"Transport": "http",
"Url": "https://app.varynforge.com/api/mcp"
}
}
} assistant mcp add com-varynforge-server -t streamable-http -u 'https://app.varynforge.com/api/mcp'
{
"mcpServers": {
"com-varynforge-server": {
"type": "http",
"url": "https://app.varynforge.com/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 4 Sept 26 −7
- Stability: pass → fail ▼ security
- Tool “send_feedback” rewrote its description, which is the text the model reads security
- Schema quality: 134 → 164 ▼ functional
- “accept_idea” added a required parameter “context”, so existing callers break ▼ functional
- “add_article_suggestion” added a required parameter “context”, so existing callers break ▼ functional
- “add_competitor_by_domain” added a required parameter “context”, so existing callers break ▼ functional
- “add_destination” added a required parameter “context”, so existing callers break ▼ functional
- “add_radar_topic” added a required parameter “context”, so existing callers break ▼ functional
- “check_idea” added a required parameter “context”, so existing callers break ▼ functional
- “create_article_suggestion_with_input” added a required parameter “context”, so existing callers break ▼ functional
- “create_content_plan_from_opportunities” added a required parameter “context”, so existing callers break ▼ functional
- “create_project” added a required parameter “context”, so existing callers break ▼ functional
- “delete_article_suggestion” added a required parameter “context”, so existing callers break ▼ functional
- “download_brief_markdown” added a required parameter “context”, so existing callers break ▼ functional
- “expand_idea” added a required parameter “context”, so existing callers break ▼ functional
- “expand_radar_topic” added a required parameter “context”, so existing callers break ▼ functional
- “generate_article_brief” added a required parameter “context”, so existing callers break ▼ functional
- “get_account_status” added a required parameter “context”, so existing callers break ▼ functional
- “get_article_brief” added a required parameter “context”, so existing callers break ▼ functional
- “get_article_suggestion” added a required parameter “context”, so existing callers break ▼ functional
- “get_changelog” added a required parameter “context”, so existing callers break ▼ functional
- “get_competitor_detail” added a required parameter “context”, so existing callers break ▼ functional
- “get_draft_status” added a required parameter “context”, so existing callers break ▼ functional
- “get_instructions” added a required parameter “context”, so existing callers break ▼ functional
- “get_keyword_detail” added a required parameter “context”, so existing callers break ▼ functional
- “get_lint_rubric” added a required parameter “context”, so existing callers break ▼ functional
- “get_onboarding_guide” added a required parameter “context”, so existing callers break ▼ functional
- “get_opportunity_detail” added a required parameter “context”, so existing callers break ▼ functional
- “get_page_dossier” added a required parameter “context”, so existing callers break ▼ functional
- “get_pitch_report_payload” added a required parameter “context”, so existing callers break ▼ functional
- “get_project” added a required parameter “context”, so existing callers break ▼ functional
- “get_project_asset” added a required parameter “context”, so existing callers break ▼ functional
- “get_project_overview” added a required parameter “context”, so existing callers break ▼ functional
- “get_research_status” added a required parameter “context”, so existing callers break ▼ functional
- “get_starting_point_report” added a required parameter “context”, so existing callers break ▼ functional
- “get_write_handoff” added a required parameter “context”, so existing callers break ▼ functional
- “get_writer_system_prompt” added a required parameter “context”, so existing callers break ▼ functional
- “lint_draft” added a required parameter “context”, so existing callers break ▼ functional
- “list_article_suggestions” added a required parameter “context”, so existing callers break ▼ functional
- “list_competitors” added a required parameter “context”, so existing callers break ▼ functional
- “list_destinations” added a required parameter “context”, so existing callers break ▼ functional
- “list_keywords” added a required parameter “context”, so existing callers break ▼ functional
- “list_opportunities” added a required parameter “context”, so existing callers break ▼ functional
- “list_organizations” added a required parameter “context”, so existing callers break ▼ functional
- “list_pages” added a required parameter “context”, so existing callers break ▼ functional
- “list_projects” added a required parameter “context”, so existing callers break ▼ functional
- “list_radar_topics” added a required parameter “context”, so existing callers break ▼ functional
- “mark_article_published” added a required parameter “context”, so existing callers break ▼ functional
- “register_derived_asset” added a required parameter “context”, so existing callers break ▼ functional
- “remap_asset” added a required parameter “context”, so existing callers break ▼ functional
- “resync_asset_profile” added a required parameter “context”, so existing callers break ▼ functional
- “send_feedback” added a required parameter “context”, so existing callers break ▼ functional
- “set_competitor_importance” added a required parameter “context”, so existing callers break ▼ functional
- “set_excluded_terms” added a required parameter “context”, so existing callers break ▼ functional
- “set_opportunity_status” added a required parameter “context”, so existing callers break ▼ functional
- “set_posting_cadence” added a required parameter “context”, so existing callers break ▼ functional
- “start_research_run” added a required parameter “context”, so existing callers break ▼ functional
- “update_article_status” added a required parameter “context”, so existing callers break ▼ functional
- “update_asset_profile” added a required parameter “context”, so existing callers break ▼ functional
- “update_niche” added a required parameter “context”, so existing callers break ▼ functional
- Tool coverage: 0% → 26% ▲ functional
- Server version: 1.20.0 → 1.21.0 functional
- 2 Sept 26 0
- Stability: 0.97 → pass security
- 1 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 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.
- 26 Aug 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 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 20 Sept 2026 · Probed https://app.varynforge.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.varynforge.com | CN=YR1,O=Let's Encrypt,C=US | 4 Sept 2026 | 3 Dec 2026 | RSA 2048 | SHA256-RSA | 5a0e6dde94cf4b6bc611294928c43932df2 |
| SANs: *.varynforge.com, varynforge.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| 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 insecure
Validation of app.varynforge.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| varynforge.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://app.varynforge.com/api/auth/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://app.varynforge.com/api/auth/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), interest-cohort=() |
Protected resource metadata
| Document | https://app.varynforge.com/api/auth/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://app.varynforge.com |
| Authorisation server | https://app.varynforge.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://app.varynforge.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://app.varynforge.com/api/mcp | HTTPS enforced | 308 | https://app.varynforge.com/api/mcp |
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 →
set_excluded_terms Set excluded terms ~136
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | One sentence: what is the operator trying to achieve right now? Describe their goal, not this tool's purpose. |
| projectId | string | yes | – |
| terms | array | yes | – |
No output schema declared.
No examples provided.
set_opportunity_status Set opportunity status ~144
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.
| Name | Type | Req | Description |
|---|---|---|---|
| clusterId | string | yes | – |
| context | string | yes | One sentence: what is the operator trying to achieve right now? Describe their goal, not this tool's purpose. |
| projectId | string | yes | – |
| status | string | yes | – |
No output schema declared.
No examples provided.
set_posting_cadence Set posting cadence ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | One sentence: what is the operator trying to achieve right now? Describe their goal, not this tool's purpose. |
| postsPerWeek | integer | yes | – |
| projectId | string | yes | – |
No output schema declared.
No examples provided.
start_research_run Start research run ~99
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | One sentence: what is the operator trying to achieve right now? Describe their goal, not this tool's purpose. |
| id | string | yes | – |
No output schema declared.
No examples provided.
update_article_status Update article status ~211
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | One sentence: what is the operator trying to achieve right now? Describe their goal, not this tool's purpose. |
| id | string | yes | – |
| lastActor | string | – | – |
| scheduledFor | – | – | – |
| status | string | yes | – |
No output schema declared.
No examples provided.
update_asset_profile Update asset profile ~164
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.
| Name | Type | Req | Description |
|---|---|---|---|
| benefits | array | – | – |
| context | string | yes | One sentence: what is the operator trying to achieve right now? Describe their goal, not this tool's purpose. |
| description | string | – | – |
| keyDifferentiators | array | – | – |
| primaryOffer | string | – | – |
| projectId | string | yes | – |
| useCases | array | – | – |
No output schema declared.
No examples provided.
update_niche Update niche ~136
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | One sentence: what is the operator trying to achieve right now? Describe their goal, not this tool's purpose. |
| coreProblem | string | – | – |
| country | string | – | – |
| id | string | yes | – |
| industry | string | – | – |
| language | string | – | – |
| name | string | yes | – |
| relatedTerms | array | – | – |
| targetCustomer | string | – | – |
No output schema declared.
No examples provided.
What is the VarynForge MCP server?
VarynForge is an MCP server listed in the public MCP registry as com.varynforge/server. SEO research SaaS exposed as 30+ MCP tools. Forge niche analysis, plans, and writer-ready briefs. This page covers its hosted endpoint (https://app.varynforge.com/api/mcp).
Is the VarynForge MCP server safe to use?
VarynForge scores 83 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 VarynForge MCP server expose?
VarynForge exposes 57 tools: get_instructions, get_changelog, get_writer_system_prompt, get_account_status, list_organizations, and 52 more. Their descriptions and schemas cost roughly 9,371 tokens of context every time the server is loaded.
Does the VarynForge MCP server require authentication?
Yes. VarynForge asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the VarynForge MCP server still maintained?
VarynForge is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.