Skip to main content
Glama

BRAINIAC SOAP Security

Server Details

Paid SOAP Security API via x402. Unpaid tool calls return 402.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A3.7/5.0

Scored across 2 tools

Disambiguation4/5

The two tools take clearly different inputs and answer different questions: one grades a caller-supplied algorithm suite/token posture, the other compares WS-Policy assertions across WSDL bindings and emits audit_status/risk_level. There is conceptual overlap since both assess 'declared' SOAP security without verifying enforcement, which could tempt a misselection, but the input contracts keep them separable.

Naming Consistency4/5

Both names use the same soap-security_ prefix and kebab-case action suffixes, so the pattern is predictable. Minor gripe: 'policy-strength' omits the domain qualifier while 'soap-security-policy-audit' redundantly repeats the server prefix, making the pair slightly asymmetric.

Tool Count3/5

Two tools is thin for a domain as broad as SOAP/WS-Security, which invites suspicion that the surface was truncated rather than deliberately scoped. Each tool is individually well-scoped and non-redundant, so it is borderline rather than badly mismatched.

Completeness2/5

Both tools are purely declarative static analyses; neither validates certificates, fetches imports/policy files, or checks whether a server actually enforces what it declares. The lifecycle dead-ends after scoring/auditing, with no verification, probing, or remediation path, leaving significant gaps for an agent tasked with real SOAP security assessment.

Available Tools

2 tools
soap-security_policy-strengthScore SOAP policy strengthA
Read-onlyIdempotent
Inspect

Score a caller-supplied algorithm suite, body signature, body encryption, timestamp, and token kind. Basic256Sha256 contributes the most, TripleDes and None the least. A username token scores below an X.509 token. The grade follows that score. No certificate is validated and no policy file is fetched. Price $0.04 USDC. POST /api/v1/soap-security/policy-strength. An unpaid call returns the x402 payment terms and does not run.

Inputs: token (required), timestamp (required), body_signed (required), body_encrypted (required), +1 more. Returns: security_policy_grade, cryptographic_strength_score

soap-security_soap-security-policy-auditAudit SOAP security policyA
Read-onlyIdempotent
Inspect

Compare WS-Policy and WS-SecurityPolicy assertions across caller-supplied WSDL 1.1 bindings and operations. audit_status is valid, warnings, policy_conflicts, invalid, or incomplete. risk_level is low, medium, high, or critical. A declared policy is not evidence that a server enforces it. Imports are not fetched. Price $0.05 USDC. POST /api/v1/soap-security/soap-security-policy-audit. An unpaid call returns the x402 payment terms and does not run.

Inputs: documents (required), expected, selection. Returns: findings, risk_level, limitations, audit_status, +5 more

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources