
Vreddie Mcp Server
io.github.vreddie2goPublished by GitHub account vreddie2gov1.0.1Updated Oct 24, 2026
VR Eddie's headset ratings, game reviews, deals, and compatibility checks via MCP.
Overview
A local MCP server that gives an assistant access to VR Eddie's headset ratings, game reviews, deals and compatibility checks.
- What you can do
- Look up VR headset ratings and reviews from VR Eddie's catalog, so an assistant can compare headsets by rating and reviewer verdicts. Retrieve game reviews to see how titles are assessed for VR play. Surface current deals on headsets and games. Run compatibility checks to see whether a headset and a game or setup work together. The manifest lists no individual tools, so the exact operations are not documented here.
- When to use it
- Useful when someone is shopping for a VR headset or game and wants ratings, reviews, deals and compatibility information brought into an assistant conversation instead of browsing the site manually.
- Requirements
- Runs as a local process over stdio, installed from the npm package vreddie-mcp-server, so a Node.js runtime is needed. It is desktop-only and not web-executable. No authentication, environment variables or headers are declared.
Installation
In SourceWeft
- Open Vreddie Mcp Server in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v1.0.1LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.