A
licenseB
qualityB
maintenanceEnables AI clients to connect locally over stdio, discover and read schemas for native page tools, and execute user-authorized operations supplied by websites and independent user scripts.
13
MIT
StealthMark MCP Server
OfficialRelated Servers
Alternatives to StealthMark MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables an AI agent to run local tools on the user's own machine via stdio, including command execution, workspace file read/write, and system status checks.52MIT
- AlicenseBqualityCmaintenanceA stdio helper that connects AI apps to the local SoftGlaze Browser MCP server, relaying token-scoped tool, prompt, and resource requests while requiring approval in the browser app.39MIT
molesignal mcpofficial
AlicenseNot gradedqualityBmaintenanceServes MoleSignal's tools over stdio to AI agent tools such as Claude Code, Cursor, Codex, VS Code, or Gemini CLI, enabling them to query logs, metrics, traces, incidents, approvals, deployments, and other capabilities under the user's permissions and organization policy.446 npmApache 2.0- AlicenseNot gradedqualityBmaintenanceExposes ReadyAgents' local workflow engine and built-in tools over MCP stdio, enabling MCP clients to define, run, inspect, and approve YAML/JSON agent workflows.83 PyPI1Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables an AI agent to create stateful signal sessions over stdio, feed synthetic or replayed event streams, and read advisory verdicts for evaluation, demos, and integration checks.MIT
TDQS
B3.4/5.0
Scored across 3 tools
Disambiguation5/5
The three tools have clearly distinct purposes: resolving a site manifest, invoking a declared action, and looking up agent status. An agent can easily choose between discovery, execution, and identity lookup without overlap.
Naming Consistency4/5
All names use snake_case and are readable, but the prefixes differ in style: gateway_resolve and gateway_invoke share a gateway_ action pattern, while kya_status uses an acronym-plus-noun pattern. This is a minor deviation rather than a confusing inconsistency.
Tool Count5/5
Three tools is well-scoped for a focused gateway server: resolve, invoke, and status lookup each cover a distinct part of the workflow. There is no obvious tool bloat or trivial single-tool surface.
Completeness3/5
The core resolve-then-invoke workflow is covered, and status lookup supports agent identity checks. However, the agent lifecycle is notably incomplete: there is no way to list registered agents, register a new agent, or update agent details, which may cause dead ends for administrative tasks.
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues