Skip to content
Request beta access

Integrations

Use the tools you already use.

Keep the same rule, evidence and verification target across the workflows Vybentis currently supports. Use the local CLI and configured MCP and API paths. The GitHub repository path remains private to Core Industry.

Explore MCP & CLI Read the docs

Use MCP, the local CLI or configured API paths. GitHub repository context remains private to Core Industry.

CursorClaude CodeCodexGitHub CopilotWindsurfVS CodeReplitAntigravityLovableBoltv0Base44GitHubVercelSupabaseFirebase

One finding, every workflow

The evidence does not get lost between tools.

Vybentis keeps the rule ID, observed evidence, confidence and verification target together. The destination changes. The meaning does not.

Public scanyourapp.dev18 routes observed
Evidence attachedCanonical points to a redirect
Rule
SEO_CANONICAL_003
Confidence
High
Expected
One final URL

Sending to Coding agent

Coding agentSend one scoped taskfix_prompt.md
Terminal and CIRun the same ruleverified · exit 0
1 / 2: Coding agent

Choose the right path

Use only the access the job needs.

Start with the public URL. Use the local CLI or configured MCP and API paths for additional context. The GitHub path remains limited to Core Industry.

GitHub · private Core Industry path

Keep repository context private to Core Industry.

The GitHub repository path is setup required for the private Core Industry workspace. It is not a customer integration or public GitHub App. When enabled internally, Vybentis pins one immutable read only commit to the scan.

No customer installation or public GitHub App.
setup requiredRead the GitHub boundary
MCP

Read Vybentis evidence from a compatible agent.

The implemented MCP surface exposes project and scan status, findings, redacted evidence, fix prompts and Markdown reports. Scan and verification tools require explicit target authorization and an idempotency key.

Scoped API token and organization context required.
8 typed toolsSet up MCP
CLI and CI

Use the same checks in your own workflow.

The implemented CLI runs bounded repository checks locally and in CI. It requires the explicit --local mode, keeps source code on your machine and returns structured output that scripts can understand.

Remote URL and account commands are not available in the MVP.
vybentis scan . --localSet up the CLI

SEO and AI visibility

See what search tools can actually read.

Vybentis reads the public signals that shape discovery. Each issue points to the observed page and a clear expected result.

Vybentis does not promise search rankings or citations by AI systems.
https://yourapp.dev/pricingLive page

yourapp.dev › pricing

Simple plans for your next release

Scan a live app, understand each finding and send a focused fix to your coding agent.

Canonical/pricingIndexableYes
Indexing signalsRobots rules, meta robots, sitemaps and reachable pages.
Page meaningTitles, descriptions, headings, canonical links and language signals.
Structured dataSchema markup is compared with the content people can actually see.
AI crawler accessSearch crawlers and training crawlers are shown as separate signals.

Check canonical links, redirects, page titles, sitemaps, robots rules, structured data, language signals and server rendered content.

See every public check

A simple setup

From live page to checked change.

The workflow stays small enough to understand and strict enough to repeat.

  1. Start with the live URL

    Vybentis checks the pages and responses that people and search tools can reach.

  2. Add one source when needed

    Use the local CLI or configured MCP and API paths when the release question needs more context. GitHub repository context is reserved for the private Core Industry setup.

  3. Move one clear task

    The rule ID, evidence and expected result travel together into the next tool.

  4. Run the same check again

    A finding changes to verified only when the documented evidence matches.

Integration routes

One contract, several ways to use it.

Every route keeps stable identifiers and scope, so a report, an agent and a script can refer to the same finding.

RouteBest forWhat movesAccess
RoutePublic URLBest forLive pages, SEO and public security signalsWhat movesReachable evidenceAccessNo account credentials
RouteGitHubBest forPrivate Core Industry repository contextWhat movesRead only resolved commitAccessSetup required, no customer install
RouteMCPBest forConfigured compatible coding agentsWhat movesTyped project, scan and finding toolsAccessScoped token and organization context
RouteCLIBest forLocal repository checks and CIWhat movesHuman, JSON, Markdown or SARIF outputAccessRequires --local; source stays local
RouteREST APIBest forConfigured product workflowsWhat movesVersioned JSON contractsAccessScoped credentials and organization context
Card 1 / 5

Clear boundaries

Your tools receive a task, not a master key.

Repository access is read only and the GitHub path remains private to Core Industry. Secrets are redacted before storage and AI processing. MCP and API require scoped credentials with organization context.

Minimum accessOnly the permission needed for the selected route.
Read only by defaultWrite permissions are separate and never assumed.
Evidence stays attachedThe conclusion always points back to what was observed.

Keep your current workflow

Add Vybentis where the evidence needs to move.

Start with a public scan. Use the local CLI or configured MCP and API paths when the next release question needs more context. GitHub remains a private Core Industry path.

Scan your app Open MCP and CLI setup