Agentic Security Shield
Server Details
12-layer security configs for AI coding agents. Autonomous purchase via x402 (USDC on Base).
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- ormuzdo/agentic-security-shield
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.3/5 across 4 of 4 tools scored.
Each tool has a distinct and well-defined purpose: preview, pricing, sample, and purchase. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern (get_preview, get_pricing, get_sample, purchase) using snake_case, making them predictable and easy to understand.
With only 4 tools, the server is tightly scoped to its core functions: providing information and facilitating purchase. This is appropriate for a security product acquisition flow.
The tool set covers the complete user journey: learning about the product (preview, pricing, sample) and completing the purchase (purchase). There are no obvious gaps for the intended domain.
Available Tools
4 toolsget_previewInspect
Get a free preview of Agentic Security Shield — what it does, which AI tools and backends it supports, and what security layers are included. No payment required.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
get_pricingInspect
Get pricing information and payment instructions for Agentic Security Shield. Returns price, accepted payment method (x402/USDC on Base), and step-by-step purchase flow.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
get_sampleInspect
Get a free sample security rule from Agentic Security Shield. Returns Layer 3 (Secrets Guard) with real code examples showing vulnerable vs. secure patterns. Demonstrates the quality and depth of all 12 layers.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
purchaseInspect
Purchase Agentic Security Shield and receive all security configuration files.
TWO-PHASE FLOW (you MUST do BOTH steps): STEP 1 — on-chain payment + token exchange: a) Send 19 USDC on Base network to the recipient address in /pricing or /.well-known/mcp/server-card.json (payTo field). b) POST /purchase (HTTP REST, not this MCP tool!) Header: x-payment-token: <on-chain transaction hash, 0x + 64 hex> Response: { "download_token": "dl_", "files": {...} }
STEP 2 — call this MCP tool with the dl_ token: purchase({ payment_token: "dl_" })
The on-chain tx hash is single-use and only valid in STEP 1. After STEP 1 you have a 24-hour-valid dl_ download token usable in this MCP tool. Most agents will get the files inline from STEP 1's response and never need to call this MCP tool — it exists for clients that prefer MCP-native delivery.
| Name | Required | Description | Default |
|---|---|---|---|
| ai_tool | No | Optional: the AI tool you use (e.g., 'claude-code', 'cursor', 'copilot'). If provided, the primary config file for this tool will be highlighted in the response. | |
| payment_token | Yes | Download token from STEP 1 (format: 'dl_<uuid>' returned by POST /purchase). NOT the raw on-chain tx hash — that goes to POST /purchase's x-payment-token header in STEP 1. |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!