Skip to main content
Glama
Sim-xia

Blind-Auditor-MCP

by Sim-xia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
submit_draftC

Submit a code draft for audit.

submit_audit_resultD

Submit the audit result.

reset_sessionB

Reset the current audit session.

update_rulesA
Update audit rules configuration.

Args:
	action: Operation to perform - "add", "remove", "update", or "list"
	rule_id: Rule identifier (required for add/remove/update)
	severity: Rule severity level - "CRITICAL", "WARNING", or "PREFERENCE" (for add/update)
	description: Rule description (for add/update)
	weight: Point deduction weight 0-100 (for add/update)

Returns:
	Status message with operation result

Examples:
	# List all rules
	update_rules(action="list")
	
	# Add a new rule
	update_rules(
		action="add",
		rule_id="SEC-001",
		severity="CRITICAL",
		description="No hardcoded API keys",
		weight=50
	)
	
	# Remove a rule
	update_rules(action="remove", rule_id="SEC-001")
	
	# Update a rule
	update_rules(
		action="update",
		rule_id="SEC-001",
		description="Updated description"
	)

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

B3.1/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: reset_session handles session management, submit_audit_result and submit_draft handle different submission types (final results vs. code drafts), and update_rules handles rule configuration. The tools target different resources and actions, making misselection unlikely.

Naming Consistency4/5

Three tools follow a consistent verb_noun pattern (reset_session, submit_audit_result, submit_draft), while update_rules also fits this pattern but uses a different verb style ('update' vs. 'reset'/'submit'). The naming is mostly consistent with only minor deviation in verb choice.

Tool Count5/5

With 4 tools, this is well-scoped for an audit server. Each tool earns its place by covering core audit workflow stages: session management, rule configuration, draft submission, and result submission. The count is neither too sparse nor bloated for the domain.

Completeness4/5

The toolset covers the essential audit lifecycle: configure rules, submit drafts, submit results, and manage sessions. A minor gap exists in lacking a tool to retrieve or review audit results/history, but agents can work around this using the existing submission tools. Core workflows are well-supported.

Maintenance

ActivityInactive
ResponsivenessUnresponsive

Resources