npm:@usevyre/mcp-server

Item: npm:@usevyre/mcp-server
Rating: 55
Author: wmcp.sh

https://www.npmjs.com/package/@usevyre/mcp-server

55/100 · MCP Trust Grade · checked 3h ago · MCP 1.0.11

What it offers — 8 tools · Developer Tools

get_component_info

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

get_valid_props

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

check_valid_prop_value

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

suggest_component

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

get_full_context

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

get_anti_patterns

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

get_version_info

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

get_token_info

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

Spec / packaging20%100

✓ depends on an MCP SDK
✓ declares a bin entry (runnable server)
✓ 8 tool(s) detected in source

Security (OWASP MCP)30%15

⚠ prompt-injection / hidden-instruction markup in source
scanned 1 source file

Maintenance / popularity20%100

published within 90 days
17 published versions

Tool hygiene15%70

no TypeScript types
3 runtime deps

Transparency / provenance15%90

✓ public repository linked
✓ MIT license
40 weekly downloads

Findings

FAILMCP01 Prompt-injection / hidden-instruction markup found in package source.

INFO Static analysis of npm package @usevyre/mcp-server@1.0.11 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured.

Grade another server

We re-grade npm:@usevyre/mcp-server on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — npm:@usevyre/mcp-server grade F

Share on X Open card image

https://wmcp.sh/mcp/grade/npm%3A%40usevyre%2Fmcp-server

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

Markdown (for your README)

[![MCP Trust Grade F](https://wmcp.sh/mcp/grade/npm%3A%40usevyre%2Fmcp-server/badge.svg)](https://wmcp.sh/mcp/grade/npm%3A%40usevyre%2Fmcp-server)

HTML

<a href="https://wmcp.sh/mcp/grade/npm%3A%40usevyre%2Fmcp-server"><img src="https://wmcp.sh/mcp/grade/npm%3A%40usevyre%2Fmcp-server/badge.svg" alt="MCP Trust Grade F · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust

How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.