Skip to main content
Glama
CSOAI-ORG

MEOK MCP Hardening MCP

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
audit_server_jsonC

Full OWASP LLM Top 10 + MCP-specific security audit of an MCP server.json.

audit_tool_descriptionC

Deep-scan a single tool description for injection / destructive / spoof signals.

check_destructive_surfaceC

Return only the destructive-surface findings (LLM08) — fast gate for CI.

check_supply_chainC

Return only supply-chain findings (LLM05) — pin + provenance audit.

list_owasp_findingsA

Return the canonical OWASP LLM Top 10 (2025) → MCP-Hardening rule map.

generate_hardened_templateA

Return a minimal-passing server.json starter that scores A.

sign_security_reportC

HMAC-seal an audit result so it can be published as a signed badge.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 7 tools

Disambiguation5/5

Each tool targets a distinct security audit task: full server audit, per-description scan, specific vulnerability checks, template generation, listing rules, and signing reports. No overlap in purpose.

Naming Consistency3/5

Tool names use underscore and follow verb_noun pattern, but verbs vary: 'audit', 'check', 'generate', 'list', 'sign'. While readable, the mix of verbs reduces consistency compared to a uniform pattern.

Tool Count5/5

7 tools is well-scoped for a security hardening server. Each tool addresses a distinct need without being too few or excessive.

Completeness4/5

Covers core audit workflows: full server audit, per-tool scan, specific checks (destructive, supply chain), template generation, reference map, and report signing. Minor gap: no direct apply/patch tool, but overall comprehensive.

Maintenance

ActivityInactive
ResponsivenessNo issues