Skip to main content
Glama
fefergrgrgrg

Frontend Review MCP

by fefergrgrgrg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid
README.md
CS-Wallet [![Build Status](https://travis-ci.org/CoinSpace/cs-wallet.svg)](https://travis-ci.org/CoinSpace/cs-wallet)
=========

Wallet for [CoinSpace](https://github.com/CoinSpace/CoinSpace) app.
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.7/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap with other tools. The tool 'reviewEdit' has a single, clearly defined purpose focused on visual review of UI edits.

Naming Consistency5/5

Since there is only one tool, naming consistency is inherently perfect. The tool name 'reviewEdit' follows a clear verb_noun pattern, and there are no other tools to compare it against for inconsistency.

Tool Count2/5

A single tool is generally too few for a server's purpose, as it limits functionality and can feel thin. For a 'Frontend Review MCP', one might expect additional tools for tasks like listing reviews, managing requests, or handling different types of edits, making this count inappropriate for the apparent scope.

Completeness2/5

The tool set is severely incomplete for a frontend review domain. While 'reviewEdit' handles the core review action, there are obvious gaps such as tools for creating, listing, updating, or deleting review requests, which would be essential for a complete workflow and could cause agent failures due to missing operations.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources