RelayShield Agentic Attack Surface (AWS Marketplace)
by relayshieldadminco.huggingface.relayshieldadmin/relayshield-agentic-attack-surface-aws
- Remote endpoint
- 13 tools
Uptime
Checked · every day
100%from 4 days of checks
Up without downtime on 3 of 3 days with data.
- No downtime
- Degraded
- Down over 5 minutes
- No data
- Not checked yet
Response time
Median 967 ms, slowest 5% 1187 ms for the handshake and the tool list, over 30 days.
How far each check got
- Reached the address 100%
- Completed the handshake 100%
- Listed its tools 100%
13 tools at the last answer.
Every day
| Day | Result | Checks | Median |
|---|---|---|---|
| 3 Nov (today) | No verdict yet | 0 | – |
| 2 Nov | No downtime | 1of 1 | 1118 ms |
| 1 Nov | No downtime | 1of 1 | 970 ms |
| 31 Oct | No downtime | 2 | 976 ms |
A failure counts as down time only when a second check five minutes later fails too. How we check
Connect to the publisher's own endpoint
Paste into Settings › Connectors › Add custom connector:
https://relayshieldadmin-relayshield-agentic-attack-surface-aws.hf.space/gradio_api/mcp/sse Run in a terminal:
claude mcp add --transport sse relayshield-agentic-attack-surface-aws https://relayshieldadmin-relayshield-agentic-attack-surface-aws.hf.space/gradio_api/mcp/sse Add to ~/.cursor/mcp.json:
Add to ~/.config/devin/mcp_config.json:
Add to mcp.json (Program › Install › Edit mcp.json):
Add to ~/.gemini/settings.json:
Add to config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows):
Add to ~/.config/eca/config.json (global) or .eca/config.json in the project:
{
"mcpServers": {
"relayshield-agentic-attack-surface-aws": {
"url": "https://relayshieldadmin-relayshield-agentic-attack-surface-aws.hf.space/gradio_api/mcp/sse"
}
}
} Add to .vscode/mcp.json:
{
"servers": {
"relayshield-agentic-attack-surface-aws": {
"type": "sse",
"url": "https://relayshieldadmin-relayshield-agentic-attack-surface-aws.hf.space/gradio_api/mcp/sse"
}
}
} Add to ~/.config/zed/settings.json:
{
"context_servers": {
"relayshield-agentic-attack-surface-aws": {
"url": "https://relayshieldadmin-relayshield-agentic-attack-surface-aws.hf.space/gradio_api/mcp/sse"
}
}
} This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers):
Add to anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory:
Add to Augment Settings Panel – MCP section – Import from JSON (VS Code extension):
{
"mcpServers": {
"relayshield-agentic-attack-surface-aws": {
"type": "sse",
"url": "https://relayshieldadmin-relayshield-agentic-attack-surface-aws.hf.space/gradio_api/mcp/sse"
}
}
} Add to ~/.continue/config.yaml:
mcpServers:
- name: "relayshield-agentic-attack-surface-aws"
type: sse
url: "https://relayshieldadmin-relayshield-agentic-attack-surface-aws.hf.space/gradio_api/mcp/sse" Add to ~/.config/goose/config.yaml:
extensions:
"relayshield-agentic-attack-surface-aws":
type: streamable_http
name: "relayshield-agentic-attack-surface-aws"
enabled: true
uri: "https://relayshieldadmin-relayshield-agentic-attack-surface-aws.hf.space/gradio_api/mcp/sse"
headers: {}
env_keys: []
envs: {}
timeout: 300 This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Run in a terminal:
codex mcp add relayshield-agentic-attack-surface-aws --url https://relayshieldadmin-relayshield-agentic-attack-surface-aws.hf.space/gradio_api/mcp/sse This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to ~/.llm/config.json:
Add to resources/assets/config/mcp.json in the installed app:
Add to ~/.boltai/mcp.json:
Add to ~/.bob/settings/mcp.json (global) or .bob/mcp.json (project):
Add to ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace):
Add to ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace):
{
"mcpServers": {
"relayshield-agentic-attack-surface-aws": {
"url": "https://relayshieldadmin-relayshield-agentic-attack-surface-aws.hf.space/gradio_api/mcp/sse"
}
}
} This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to ~/.config/agenvoy/mcp.json:
{
"servers": {
"relayshield-agentic-attack-surface-aws": {
"url": "https://relayshieldadmin-relayshield-agentic-attack-surface-aws.hf.space/gradio_api/mcp/sse"
}
}
} This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):
{
"amp.mcpServers": {
"relayshield-agentic-attack-surface-aws": {
"url": "https://relayshieldadmin-relayshield-agentic-attack-surface-aws.hf.space/gradio_api/mcp/sse"
}
}
} For agents: the install prompt
Every step above as one Markdown text, for an assistant installing it for you.
# Install the MCP server RelayShield Agentic Attack Surface (AWS Marketplace) (`co.huggingface.relayshieldadmin/relayshield-agentic-attack-surface-aws`)
Its page: https://plug.directory/servers/co.huggingface.relayshieldadmin/relayshield-agentic-attack-surface-aws
It runs on the publisher's servers; the client connects to its URL.
Use the section for the person's client.
## Claude Desktop
Paste into Settings › Connectors › Add custom connector:
```text
https://relayshieldadmin-relayshield-agentic-attack-surface-aws.hf.space/gradio_api/mcp/sse
```
## Claude Code
Run in a terminal:
```sh
claude mcp add --transport sse relayshield-agentic-attack-surface-aws https://relayshieldadmin-relayshield-agentic-attack-surface-aws.hf.space/gradio_api/mcp/sse
```
## Cursor, Devin Desktop, LM Studio, Gemini CLI, oterm, ECA
Merge into the place for the person's client:
- Cursor: ~/.cursor/mcp.json
- Devin Desktop: ~/.config/devin/mcp_config.json
- LM Studio: mcp.json (Program › Install › Edit mcp.json)
- Gemini CLI: ~/.gemini/settings.json
- oterm: config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows)
- ECA: ~/.config/eca/config.json (global) or .eca/config.json in the project
```json
{
"mcpServers": {
"relayshield-agentic-attack-surface-aws": {
"url": "https://relayshieldadmin-relayshield-agentic-attack-surface-aws.hf.space/gradio_api/mcp/sse"
}
}
}
```
## VS Code
Merge into .vscode/mcp.json:
```json
{
"servers": {
"relayshield-agentic-attack-surface-aws": {
"type": "sse",
"url": "https://relayshieldadmin-relayshield-agentic-attack-surface-aws.hf.space/gradio_api/mcp/sse"
}
}
}
```
## Zed
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## Cline, AnythingLLM, Augment Code
Merge into the place for the person's client:
- Cline: cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers)
- AnythingLLM: anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory
- Augment Code: Augment Settings Panel – MCP section – Import from JSON (VS Code extension)
```json
{
"mcpServers": {
"relayshield-agentic-attack-surface-aws": {
"type": "sse",
"url": "https://relayshieldadmin-relayshield-agentic-attack-surface-aws.hf.space/gradio_api/mcp/sse"
}
}
}
```
## Continue
Merge into ~/.continue/config.yaml:
```yaml
mcpServers:
- name: "relayshield-agentic-attack-surface-aws"
type: sse
url: "https://relayshieldadmin-relayshield-agentic-attack-surface-aws.hf.space/gradio_api/mcp/sse"
```
## Goose
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## Codex
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## mcp-client-cli, TUUI, BoltAI, Bob Shell, Kiro, Kiro CLI
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## Agenvoy
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## Amp
Merge into ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):
```json
{
"amp.mcpServers": {
"relayshield-agentic-attack-surface-aws": {
"url": "https://relayshieldadmin-relayshield-agentic-attack-surface-aws.hf.space/gradio_api/mcp/sse"
}
}
}
```
Then restart the client, or reload its MCP servers, and ask it to list the server's tools to confirm it started.
Tools 13
relayshield_agentic_attack_surface_aws_check_agent_risk_summaryComposite risk check -- one call instead of four. Runs breach exposure, LLM credential exposure, and tech-stack CVE checks together and returns a single fused risk verdict, so a calling agent doesn't have to make multiple tool calls and reason about how to combine their results itself. Returns: A structured result combining all sub-checks that were run, with the, highest severity found across them driving the overall outcome.relayshield_agentic_attack_surface_aws_check_bulk_identity_riskHierarchical org + AI-agent-identity risk scoring for a domain and up to 5 agent/service-account identities. A critically-exposed agent automatically elevates the organizational risk rating. Returns: A structured result: outcome/recommended_action plus evidence and reason codes.relayshield_agentic_attack_surface_aws_check_llm_credential_exposureCheck a domain for exposed LLM/AI provider API keys (OpenAI, Anthropic, Google, Groq, xAI, Replicate) in criminal stealer logs -- LLMjacking, a fast-growing threat where a leaked key becomes a live, uncapped billing liability rather than just a data exposure. Real incidents have run from tens of thousands of dollars per day to a $500K single-month bill from one leaked, unthrottled key. Returns: A structured result: outcome/recommended_action plus evidence and reason codes.relayshield_agentic_attack_surface_aws_check_mcp_server_riskCheck an MCP server URL for typosquat risk, presence in RelayShield's criminal IOC corpus, and domain-registration age. Returns: A structured result: outcome/recommended_action plus evidence and reason codes.relayshield_agentic_attack_surface_aws_check_nhi_exposureCheck a domain, or up to 10 vendor domains, for exposed non-human- identity (NHI) credentials — API keys, service-account tokens, personal access tokens, and other machine identities found in criminal stealer logs. Returns: A structured result: outcome/recommended_action plus evidence and reason codes.relayshield_agentic_attack_surface_aws_check_oauth_watchlistCheck an email for OAuth-connected-app exposure: apps matched against breach history, plus stolen OAuth/session tokens found in criminal stealer logs. Returns: A structured result: outcome/recommended_action plus evidence and reason codes.relayshield_agentic_attack_surface_aws_check_prompt_injection_breachCheck an email address for credential exposure sourced specifically from prompt-injection attacks against AI agents, distinct from ordinary phishing/malware-sourced breaches. Returns: A structured result: outcome/recommended_action plus evidence and reason codes.relayshield_agentic_attack_surface_aws_check_secret_scanCheck a domain, or up to 5 vendor domains, for secrets and credentials exposed in public GitHub/GitLab repositories. Returns: A structured result: outcome/recommended_action plus evidence and reason codes.relayshield_agentic_attack_surface_aws_check_server_statusCheck which RelayShield tools and data sources are currently live on this MCP server -- a lightweight introspection call for an agent (or a human debugging) to confirm connectivity and see what's available before making a real check. Requires no API key. Returns: A structured result listing available tools and a live upstream connectivity check.relayshield_agentic_attack_surface_aws_check_session_riskCheck an email for active or reusable stolen session material (cookies, tokens) found in criminal stealer logs — exposure that can bypass MFA/authentication entirely, not just a password. Returns: A structured result: outcome/recommended_action plus evidence and reason codes.relayshield_agentic_attack_surface_aws_check_supply_chainCheck up to 10 vendor domains for breach and infostealer exposure — third-party and supply-chain risk inherited through vendor relationships. Returns: A structured result: outcome/recommended_action plus evidence and reason codes.relayshield_agentic_attack_surface_aws_check_tech_stack_cveCheck a declared AI agent framework / tech stack for CISA KEV or high-EPSS CVEs actively being exploited. Covers AI agent orchestration frameworks (LangChain, CrewAI, AutoGPT, Flowise, n8n self-hosted) and common companion infrastructure (Nacos, MinIO). Returns: A structured result: outcome/recommended_action plus evidence and reason codes.
From Hugging Face Spaces. Report a problem