Skip to main content
Glama
jphyqr

HashBuilds Secure Prompts

by jphyqr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
HASHBUILDS_API_URLNoOverride the API base URL (default: https://hashbuilds.com/api/secure-prompts). For local development, use http://localhost:3001/api/secure-promptshttps://hashbuilds.com/api/secure-prompts

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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
register_secure_promptA

Register a prompt with HashBuilds Secure Prompts for security verification and get embed options. This uses AI to scan the prompt for injection attacks, hidden instructions, data exfiltration, jailbreak attempts, and other security issues. Returns multiple display options (full badge, compact link, icon button) with implementation guidance. After registering, ASK THE USER which display option they prefer before implementing. The response includes an implementationGuide field with detailed instructions for styling and placement.

verify_secure_promptB

Verify an existing secure prompt by its ID. Returns the security scan results, risk level, and verification status.

get_embed_codeA

Generate HTML and React embed code for displaying a secure prompt badge. Use this after registering a prompt to get the code to add to your website.

audit_promptsA

Analyze a list of prompts found in a codebase and categorize them as user-facing (needs badge) or internal (audit only). This tool helps users who already have prompts in their codebase understand which ones should be registered with secure badges vs which are internal-only.

HOW TO USE:

  1. First, search the codebase for prompts using patterns like:

    • Files matching: public/PROMPT_*.txt, **/prompt*.ts

    • Code patterns: 'You are a', 'systemPrompt', 'SYSTEM_PROMPT', role: 'system'

  2. Extract the prompt text and file location for each found prompt

  3. Call this tool with the prompts array

  4. Present the audit results to the user, showing:

    • User-facing prompts that should get security badges

    • Internal prompts that are safe but should be audited

    • Prompts needing manual review

  5. Ask the user which prompts they want to register for badges

  6. Use register_secure_prompt for each selected prompt

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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

A4/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: audit_prompts analyzes existing prompts, register_secure_prompt registers new ones, verify_secure_prompt checks registered prompts, and get_embed_code generates display code. The descriptions clearly differentiate their roles in the workflow.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with snake_case: audit_prompts, get_embed_code, register_secure_prompt, verify_secure_prompt. The naming is predictable and aligns well with their functions.

Tool Count5/5

With 4 tools, this server is well-scoped for its purpose of securing prompts. Each tool earns its place by covering key aspects: auditing, registration, verification, and embedding, without being too sparse or bloated.

Completeness5/5

The tool set provides complete coverage for the secure prompt lifecycle: audit existing prompts, register new ones, verify registered prompts, and generate embed code. There are no obvious gaps, and the tools guide users through a logical workflow from discovery to implementation.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources