Skip to main content
Glama
CSOAI-ORG

meok-mcp-injection-scan-mcp

pricing

Retrieve subscription plans and pricing for the MCP injection scan service, which detects prompt-injection, tool-poisoning, and SSRF vulnerabilities.

Instructions

Pricing + subscribe links for this MCP.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The 'pricing' tool handler function. Returns pricing tiers (free, starter, pro, enterprise) with Stripe subscribe links and scan limits.
    @mcp.tool()
    def pricing() -> dict:
        """Pricing + subscribe links for this MCP."""
        return {
            "free": {"price_gbp": 0, "limit": f"{_FREE_DAILY_LIMIT} scans / day", "signed_reports": False},
            "starter_29": {"price_gbp": 29, "subscribe": STRIPE_29, "limit": "unlimited scans", "signed_reports": True},
            "pro_79": {"price_gbp": 79, "subscribe": STRIPE_79, "limit": "unlimited scans + scheduled rescans", "signed_reports": True, "support": "48h"},
            "enterprise_1499": {"price_gbp": 1499, "subscribe": STRIPE_1499, "limit": "unlimited + custom rule packs + SLA", "signed_reports": True, "support": "4h"},
            "verify_any_cert": "https://meok-attestation-api.vercel.app/verify",
        }
  • server.py:552-552 (registration)
    The @mcp.tool() decorator registers 'pricing' as an MCP tool on the FastMCP instance.
    @mcp.tool()
  • Docstring and return type annotation define the schema: no inputs, returns a dict.
    def pricing() -> dict:
  • Constants used by the pricing tool: Stripe subscribe URLs and the free daily limit.
    STRIPE_29 = "https://buy.stripe.com/4gM6oJ1BW4gi6kd6as8k838"   # Starter
    STRIPE_79 = "https://buy.stripe.com/eVq9AV4O87sudMF42k8k839"   # Pro
    STRIPE_1499 = "https://buy.stripe.com/4gM9AV80kaEG0ZT42k8k837"  # Enterprise
    
    _PRO_KEYS = set(k.strip() for k in os.environ.get("MEOK_PRO_KEYS", "").split(",") if k.strip())
    _FREE_DAILY_LIMIT = 5
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, and the description does not disclose behavioral traits such as read-only status, side effects, or required authentication. The user must assume it is safe but no additional context is given.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence that conveys the essential purpose without any superfluous words, achieving maximum conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple with no parameters and no output schema, so the description is adequate but could be improved by specifying the return format or content, such as 'Returns a JSON object with pricing tiers and subscription URLs.'

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With zero parameters, the input schema is fully descriptive. The baseline for 0 params is 4, and the description does not need to add parameter information.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Pricing + subscribe links for this MCP' clearly indicates the tool provides pricing and subscription information for the MCP server, distinguishing it from sibling tools like audit_tool_descriptions or list_rules.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool over alternatives or any prerequisites, leaving the agent to infer context from the tool name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/CSOAI-ORG/meok-mcp-injection-scan-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server