Loading ToolBench
A React-based web portal and documentation site for the SEOSiri Model Context Protocol (MCP) ecosystem, showcasing 21+ MCP server modules with tools for topology visualization, configuration generation, API pricing, and key management.
This is a React web portal, not an MCP server. No MCP protocol implementation detected. Tools are inferred from React component files (ApiKeyGenerator.tsx, mcpData.ts, etc.), not explicitly registered via MCP. Source shows package.json with React/Vite dependencies, no @modelcontextprotocol packages. Tool definitions lack formal schemas, parameter type annotations, and structured output documentation. Descriptions exist but are marketing-focused, not LLM-optimized. No error handling patterns, no input validation guidance, no security controls visible. This fails the fundamental requirement: it is not an MCP server.
Calculates dynamic pricing for SEOSiri API licenses based on scope, tier, and billing duration with volume discounts
Generates agent-specific MCP configuration snippets for Claude Code, Cursor, Windsurf, Roo Code, or direct CLI deployment
Generates cryptographically signed HMAC-SHA256 API keys for SEOSiri MCP scopes with configurable tier, country, duration, and client ID
Retrieves lead architect profile information including Momenul Ahmad's credentials, contributions, and certifications
Retrieves complete API pricing catalog with all commercial gateway tiers and billing options
Lists all available SEOSiri MCP server modules with metadata including title, description, tools count, category, and deployment info
Sends pre-formatted license key notification email via Gmail with deployment instructions and gateway URLs
Not an MCP server. This is a React web portal (Vite + React 19). No @modelcontextprotocol dependencies, no MCP protocol implementation, no tool registration via MCP SDK. Tools are inferred from React component filenames, not formally defined.
No formal input schemas visible. Tool definitions reference parameter names and types in prose (e.g., 'clientId: string'), but no JSON Schema with type, description, enum, or constraint declarations. Cannot verify parameter validation or LLM-readable constraints.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 31 | 2026-07-28+ | v2 |
Validates admin passcode to unlock restricted key generation and configuration features
Descriptions are marketing-focused, not LLM-optimized. E.g., 'Generates cryptographically signed HMAC-SHA256 API keys...' (60 chars) lacks WHEN to use, prerequisites, or error recovery guidance. No descriptions answer: what does it return? When should the LLM call it instead of a similar tool?
No output schemas documented. Tools return unspecified structures. LLMs cannot plan downstream calls or extract required fields. E.g., does generate_api_key return {key, expires_at, scope}? Unknown.
Security risk: send_license_notification accepts customerEmail and apiKey as parameters. Secrets in tool parameters are logged and enter LLM context. Use server-side secret injection instead.