Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

useVyre Context

NPM · @USEVYRE/MCP-SERVER · SCANNED AUG 3

useVyre component context for AI agents — valid props, variants, anti-patterns, and design tokens.

Available components

+23 this week 69 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security87
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (96 of 100), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (96 of 100), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 470 tokens (~58/item across 8 items; 8 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @usevyre/mcp-server

# add to Claude Code
claude mcp add gapra-usevyre-context -- npx -y @usevyre/mcp-server
# add to Codex CLI
codex mcp add gapra-usevyre-context -- npx -y @usevyre/mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "gapra-usevyre-context": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@usevyre/mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add gapra-usevyre-context --command npx --arg -y --arg @usevyre/mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  gapra-usevyre-context:
    command: "npx"
    args: ["-y", "@usevyre/mcp-server"]
// mcp.json
{
  "mcpServers": {
    "gapra-usevyre-context": {
      "command": "npx",
      "args": [
        "-y",
        "@usevyre/mcp-server"
      ]
    }
  }
}
Changelog

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.

  • 3 Aug 26 +4
    • Stability: unverified → 0.27 functional
  • 2 Aug 26 +60
    • Provenance: unverified → fail security
    • Known CVEs: unverified → partial security
    • Install scripts: unverified → pass security
    • Malware scan: unverified → pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Tool coverage: unverified → 100 functional
    • License: unverified → pass functional
    • Dependency health: unverified → partial functional
    • Maintenance: unverified → pass functional
    • MCP protocol: unverified → pass functional
    • Schema quality: unverified → good functional
    • Licence: MIT functional
  • 1 Aug 26 −16
    • Tool coverage: 100 → unverified functional
    • First check of Schema quality: unverified functional
  • 31 Jul 26 −7
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −18
    • Malware scan: pass → unverified security
  • 27 Jul 26 46

    First indexed and scored.

Diagnostics

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 3 Aug 2026 · Analysed npm/@usevyre/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 96 packages

96 packages in the resolved dependency tree · 95 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 8 exposed · ~470 tokens

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.

Tool Tokens
check_valid_prop_value ~84

Check if a specific prop value is valid for a useVyre component. Returns valid/invalid + suggestion.

NameTypeReqDescription
componentstringyesComponent name (e.g. 'Button')
propstringyesProp name (e.g. 'variant', 'size')
valuestringyesValue to check (e.g. 'primary', 'xl')

No output schema declared.

No examples provided.

get_anti_patterns ~50

Get all known AI hallucination patterns for useVyre components — prop names and values that don't exist.

NameTypeReqDescription
componentstringFilter by component name. Leave empty for all anti-patterns.

No output schema declared.

No examples provided.

get_component_info ~52

Get full context for a useVyre component: props, valid values, anti-patterns, and examples.

NameTypeReqDescription
componentstringyesComponent name (e.g. 'Button', 'Badge', 'Card')

No output schema declared.

No examples provided.

get_full_context ~32

Get the complete useVyre AI context — all components, tokens, and rules. Use for system prompt injection.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_token_info ~121

Get design token information for useVyre. Query a specific token by name, or list all tokens in a category (color, spacing, typography, borderRadius, shadow, transition, zIndex).

NameTypeReqDescription
categorystringCategory to list: 'color', 'spacing', 'typography', 'borderRadius', 'shadow', 'transition', 'zIndex'
tokenstringToken name or CSS variable (e.g. 'accent', 'color.semantic.accent', '--vyre-color-semantic-accent', 'spacing-4')

No output schema declared.

No examples provided.

get_valid_props ~47

Get all valid prop values for a useVyre component. Use this before generating component code to avoid hallucinations.

NameTypeReqDescription
componentstringyesComponent name (e.g. 'Button')

No output schema declared.

No examples provided.

get_version_info ~28

Get the current version of useVyre AI context and which package versions it is valid for.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

suggest_component ~56

Suggest the best useVyre component(s) for a given use case or description.

NameTypeReqDescription
use_casestringyesDescribe what you want to build (e.g. 'loading state', 'user avatar with status', 'search interface')

No output schema declared.

No examples provided.