Skip to content

91 results for “MCP servers”

ListGrid
What you seeeverything
RecentOldestAddedA–Z
All types91Articles28Repos24Papers10Threads10Write-ups9Advisories6Talks2Tools2
“MCP servers”
pillar.securityarticle🛡️ Security

SAIL Framework: A Practical Guide for AI Security

The SAIL Framework from Pillar Security is a seven-phase, lifecycle-oriented method for securing AI systems. The phases are AI policy and safe experimentation, AI asset discovery, AI security posture management, AI red teaming, runtime guardrails, sandboxed execution for agents and MCP servers, and AI activity tracing. It argues for a "Shift Up" approach that protects the business logic AI controls, and it is meant to sit on top of existing standards.

Model Context Protocol
SAIL FrameworkPillar Securityprompt injection+3

AI Security, GRC· Added 29 Oct 2026

endorlabs.comarticle🧠 AI

What is an AIBOM? AI bill of materials explained for security teams | Endor Labs

An AIBOM is a machine-readable inventory of models, datasets, dependencies, AI services, agents and MCP servers, with evidence of origin, license, integrity and evaluation. The Endor Labs explainer walks through a worked CycloneDX example for a fine-tuned support assistant. It compares CycloneDX ML-BOM, SPDX 3.x, the OWASP AIBOM project and the May 2026 CISA/G7 guidance, and lists what an AIBOM cannot show: runtime behavior and agent actions.

CycloneDXSPDXSBOM+5
Endor LabsOWASPCISA+3

ai-policy, ai-infra· Published and added 29 Oct 2026

endorlabs.comarticle🛡️ Security

What is an AIBOM? AI bill of materials explained for security teams | Endor Labs

AIBOM explainer from Endor Labs: an AI bill of materials is a machine-readable inventory of models, datasets, dependencies, AI services, agents and MCP servers, with origin, license and integrity evidence. It walks through a CycloneDX entry for a fine-tuned model, compares CycloneDX ML-BOM, SPDX 3.x, the OWASP AIBOM Generator and the May 2026 CISA/G7 minimum-elements guidance, and lists a six-step build process. It also states what an AIBOM cannot show: model safety, runtime behavior and coding-agent actions.

CycloneDXSPDXSBOM+2
EU AI ActISO/IEC 42001CISA+5

Supply Chain, AI Security, GRC· Published and added 29 Oct 2026

x.comthread🧠 AI

Kizuno18 (@Kizuno18) on X

Kizuno18's X post argues that the move from local stdio and Docker MCP servers to remote HTTP/SSE endpoints matures the Model Context Protocol in enterprise infrastructure. It lists three trade-offs: short-lived OAuth/JWT bearer tokens replace mounted admin credentials, deferred tool discovery avoids roughly 20k tokens of eager schema loading, and HCP Terraform enforces Sentinel/OPA policy, audit trails and approvals server-side. Opinion post with no benchmarks or code.

Model Context ProtocolDockerTerraform+5
Kizuno18HCP TerraformOPA

mcp· Added 29 Oct 2026, published 27 Oct 2026

x.comthread🛡️ Security

cubillas (@cubillas888) on X

The tweet relays Pillar Security research that opencode on Windows and WSL could run attacker-controlled code during remote MCP server OAuth sign-in. The fix shipped in opencode 1.18.33 on 28 September, with no advisory or CVE published. It advises users of remote MCP servers to update and review which servers they connect to. Technical details are not in the post.

OpenCodeModel Context ProtocolOAuth+1
Pillar Security

AI Security, AppSec· Added 29 Oct 2026, published 27 Oct 2026

arxiv.orgpaper🛡️ Security

Log-To-Leak: Prompt Injection Attacks on Tool-Using LLM Agents via the Model Context Protocol

Log-To-Leak is a prompt-injection attack on tool-using LLM agents that abuses Model Context Protocol tool metadata to trigger an attacker-controlled logging call after the last legitimate call, leaking the user query, server name, server response and agent response. Evaluated on five MCP servers and four agents, it reaches 62.64-100% attack success with 76.55-95.64% logging accuracy. Three defenses leave over 55% residual ASR on GitHub MCP with GPT-4o.

Model Context ProtocolGitHubGPT-4o+1
Log-To-Leaktool poisoningprompt injection

AI Security· Added 28 Oct 2026, published 26 Oct 2026

x.comthread🧠 AI

Prasenjit Sarkar (@stretchcloud) on X

Post explaining Claude's new support for MCP Tasks and Elicitations. A server returns a durable task handle instead of blocking. The client polls tasks/get every 250 ms to 30 s, and states are working, input_required, completed, failed or cancelled. Elicitations pause a task at input_required for human approval. It also notes Cloudflare's stateless MCP servers and Code Mode, and Sentry and Linear adoption.

Model Context ProtocolClaude CodeGitHub Actions+3
AnthropicClaudeAWS+4

mcp, agents· Added 25 Oct 2026, published 24 Oct 2026

endorlabs.comarticle🛡️ Security

ADLC Security Best Practices for Teams Shipping with Coding Agents | Endor Labs

ADLC Security Best Practices is an Endor Labs guide to controlling what AI coding agents can access, run, install and ship. It covers inventorying agents and MCP servers, sandboxing, pre-execution hooks instead of AGENTS.md rules, install-time package checks against slopsquatting and malware, reachability-based triage of agent PRs, and CI/CODEOWNERS protections. A five-step worked example and coverage metrics are included.

Model Context ProtocolClaude CodeCursor+3
slopsquattingindirect prompt injectiontool poisoning+5

AI Security, Supply Chain, DevSecOps· Published and added 23 Oct 2026

x.comthread🛡️ Security

VibecodersHQ (@VibeCodrHQ) on X

Post summarising Pillar Security's finding of a remote code execution flaw in OpenCode, the open-source AI coding agent. Versions 1.0.137 through 1.18.32 could run code from a remote MCP server during OAuth sign-in on Windows and WSL, with no prompt injection needed. The fix is in 1.18.33 (released 28 September). No advisory or CVE was issued, so scanners will not flag old installs. Interim advice is to remove unvetted remote MCP servers.

OpenCodeModel Context ProtocolOAuth+1
Pillar SecurityOpenCode Console breach

AI Security, AppSec· Added 22 Oct 2026, published 21 Oct 2026

x.comthread🧠 AI

Paulo Pierrondi | AI agents (@paulopierrondi) on X

Paulo Pierrondi's X post, part 9 of a series on installing MCP servers, lists a monthly review of installed servers. The checks are which tools the agent used, servers not called in weeks, overlapping tools that confuse the model, and whether each server still has an owner. A reply adds a decommissioning check: after removal, confirm the server's old credentials can no longer call the backend.

Model Context Protocol
Paulo Pierrondi

mcp· Published and added 20 Oct 2026

arxiv.orgpaper🧠 AI

ToFu: Exploiting and Fuzzing the LLM–Orchestrator–Tool Trust Boundary

ToFu is a tool-aware fuzzing framework for LLM tools, including MCP servers. It maps each tool argument, using its metadata, to one of 74 CWE-guided semantics-aware sanitizers (path, URL, SQL and similar). It then generates schema-valid Atheris harnesses and semantic oracles, using runtime tracers for in-process tools and outcome oracles for opaque ones. The LLM (gpt-4.1) only maps sanitizers and writes seeds; it is never the security judge. The paper also shows a "Repeat-After-Me" trick, where an LLM told to repeat attacker-crafted text emits a tool call the orchestrator executes, reproduced on LangGraph, MAF, ADK 2.0, AutoGen, Strands and CrewAI. Across 273 runnable MCP servers (3,405 tools) it reports 253 verified bugs in 343 tools across 118 servers, such as path traversal, log injection and exfiltration. These are failures a crash-based fuzzer would miss. The result matters because it shows LLM-generated tool arguments cannot be treated as trusted.

Model Context ProtocolAtherisCodeQL+7
ToFuStrandsMAF+10

mcp, research, agents· Added 18 Oct 2026

arxiv.orgpaper🛡️ Security

ToFu: Exploiting and Fuzzing the LLM–Orchestrator–Tool Trust Boundary

ToFu is a tool-aware fuzzing framework that derives semantic security checks for LLM tools (mainly MCP servers) from their metadata and a corpus of 74 CWE-guided sanitizers. It generates schema-valid Atheris harnesses, uses runtime tracers and outcome oracles to catch bugs that don't crash, and uses an LLM only to map sanitizers and seed inputs, never as the judge. It also describes a "Repeat-After-Me" attack, in which the LLM is told to repeat attacker-written text that the orchestrator then dispatches as a tool call. It was reproduced on LangGraph, MAF, ADK, AutoGen, Strands and CrewAI. On 273 MCP servers it reports 253 verified bugs across 343 tools in 118 repositories, including path traversal, log injection, exfiltration and command bypass.

Model Context ProtocolAtherisLangGraph+3
Repeat-After-Mepath traversalSSRF+6

AI Security, AppSec· Added 18 Oct 2026

x.comthread🛡️ Security

Steven Daugherty (@StevenDaugherty) on X

Post warning that FastMCP had a critical flaw where a malicious MCP server could execute code on the connecting client through a crafted tool schema. Fixed in FastMCP 3.4.8 and 4.0.11, and there is no patch for the 2.x line. It matters to anyone whose agents connect to MCP servers they don't control. The post gives no CVE ID or technical root cause.

FastMCPModel Context ProtocolPython
malicious MCP servercrafted tool schemaclient-side RCE

AI Security, AppSec· Added 18 Oct 2026, published 17 Oct 2026

x.comthread🛡️ Security

Nicholas Martin (@ndgmlondon) on X

An X post advises auditing every MCP write tool against the database role it actually runs under. A shared service key lets prompt injection trigger unapproved writes, so each agent session should get a read-only role, with a test that writes are denied. Replies note that MCP servers often inherit ambient host credentials or can escalate through a second connection pool, and suggest also testing that another tenant's rows are unreadable with the same role.

Model Context Protocol
prompt injection

AI Security, Identity & Access· Added 18 Oct 2026, published 16 Oct 2026

arxiv.orgpaper🛡️ Security

My Credentials, Please: Detecting Filesystem Capability Laundering in MCP Servers at Scale

Studies "filesystem capability laundering" in MCP servers: client approval of a tool call grants the server process broad host filesystem access, so attacker-steered arguments can reach sensitive files outside the tool's declared contract. The authors build MCP-FSD, which infers per-tool least-privilege boundaries, plants credential fixtures outside them, and tests exploitability and sandbox containment by paired dynamic execution. Of 21,097 servers from nine registries, 16.4% of 4,806 triaged servers have filesystem capabilities despite non-filesystem classifications. Dynamic validation confirmed 150 vulnerable instances, and disclosure produced 13 advisories, including two CVEs in Anthropic's Git MCP Server.

Model Context ProtocolAnthropicGit
filesystem capability launderingMCP-FSDpath traversal+1

AI Security, AppSec· Added 17 Oct 2026, published 15 Oct 2026

ethereum-magicians.orgthread🧠 AI

ERC-8444: Agentic Resource Discovery (ARD) Onchain

An Ethereum Magicians proposal for ERC-8444, which adds an onchain value and settlement layer under Google's Agentic Resource Discovery (ARD) spec for finding MCP servers, A2A agents, skills and APIs. A thin kernel records kind (skill, task, agent, registry), a CAIP-19/CAIP-10 anchor, a JCS+SHA-256 descriptor hash, a canonical URN and a status. Authority belongs to the paid address, and domains act as collected endorsements through /.well-known/ard.json. The reference implementation has Foundry-tested Solidity adapters and a Node.js gateway that passes the official ARD conformance CLI. It introduces a "task" kind (application/ai-task+json) for tenders aimed at suppliers, and the author asks for feedback on the trust root, the hash scope, same-chain anchors and the task payload.

Model Context ProtocolEthereumSolidity+2
GoogleMicrosoftHugging Face

mcp, agents· Added 14 Oct 2026, published 13 Oct 2026

linkedin.comarticle🧠 AI

AI Agents for Cybersecurity: A Guided Tour of a Repository with Tons of Resources and Examples

A guided tour of a GitHub repository of resources and examples for building AI agents, published on the Becoming a Hacker blog. Per the routing note, it covers LangChain 1.x, LCEL, RAG, LangGraph, CrewAI, DeepAgents, MCP servers and token-cost control such as caching, routing and budget guards. The fetched page held only a LinkedIn redirect notice, so the article text was not read.

LangChainLangGraphCrewAI+4

agents, llm-apps, mcp· Added 13 Oct 2026

becomingahacker.orgarticle🧠 AI

AI Agents for Cybersecurity: A Guided Tour of a Repository with Tons of Resources and Examples

Guided tour of Omar Santos's eight-part AI-agents-for-cybersecurity repository. It moves from LLM building blocks (LangChain, RAG) to security agents built with LangGraph, CrewAI, DeepAgents and MCP servers (nmap, CISA KEV, Shodan). It also covers a hardening guide for six agentic frameworks, token-cost control, and a spec for a supervisor-led, human-gated assessment harness. Design lessons include least-privilege subagents, single-use approvals and kill switches.

LangChainRAGLangGraph+7
Omar SantosOWASPCISA+1

agents, mcp, llm-apps· Added 13 Oct 2026

github.comrepo🧠 AI

santosomar/AI-agents-for-cybersecurity

Companion repository for Omar Santos's Pearson and O'Reilly trainings and books. It has eight parts of runnable Python labs: chat models, embeddings, prompt templates, LCEL prompt chaining, Chroma-based RAG, ReAct/LangGraph/CrewAI/DeepAgents agents, and FastMCP servers (nmap, CISA KEV, Shodan). It also includes guides to six agentic frameworks (OpenClaw, Hermes, Agent Zero, OpenHands, Paperclip, Buzz), a tokenomics module on agent cost (context compounding, prompt caching, model routing, token budget guards, batch API, cost per accepted outcome), and a vendor-neutral design spec for a human-gated multi-agent assessment harness. It is a current, practical curriculum for building and operating agents. Some examples act on real systems and should only be run in an authorized lab.

PythonuvLangChain+17
Omar SantosPearsonO'Reilly+15

agents, llm-apps, mcp· Added 13 Oct 2026

becomingahacker.orgarticle🛡️ Security

AI Agents for Cybersecurity: A Guided Tour of a Repository with Tons of Resources and Examples

Omar Santos walks through his eight-part AI-agents-for-cybersecurity repository: LLM building blocks (LangChain, RAG), then security agents with LangGraph, CrewAI, DeepAgents and MCP servers (nmap, CISA KEV, Shodan), a hardening guide for six agentic frameworks, token-cost control for agents, and a spec for a supervisor-led, human-gated security-assessment harness. It covers concrete design lessons such as least-privilege subagents, staged response actions, single-use approvals bound to exact actions, kill switches, and mapping controls to the OWASP Top 10 for Agentic Applications. Also notes Project CodeGuard rules shipped for AI coding assistants.

LangChainModel Context ProtocolPython+3
Omar SantosProject CodeGuardOWASP Top 10 for Agentic Applications+5

AI Security, Learning, Blue Team & Detection· Added 13 Oct 2026

linkedin.comarticle🛡️ Security

AI Agents for Cybersecurity: A Guided Tour of a Repository with Tons of Resources and Examples

Omar Santos walks through his AI-agents-for-cybersecurity GitHub repo, which has eight parts. Parts 1–4 cover LLM basics (LangChain, prompting, LCEL, RAG). Parts 5–8 cover building security agents with LangGraph, CrewAI, DeepAgents and MCP servers (nmap, CISA KEV, Shodan), and a hardening baseline for six ready-made agentic frameworks. They also cover token-cost control (caching, routing, budget guards, cost per accepted outcome) and a supervisor-led, human-gated security-assessment harness spec with single-use approvals, a kill switch and an append-only audit log. The post also covers Project CodeGuard rules for AI coding assistants. It is a practical learning path and a reference for governing and securing agents.

LangChainLangGraphCrewAI+5
Omar SantosProject CodeGuardOWASP Top 10 for Agentic Applications+9

AI Security, Learning, Blue Team & Detection· Added 13 Oct 2026

github.blogarticle🧠 AI

GitHub Copilot app for Beginners: How to teach Copilot about your codebase

Beginner-oriented GitHub blog guide to giving GitHub Copilot project context through four mechanisms: repository custom instructions (.github/copilot-instructions.md and path-specific .github/instructions files with applyTo), agent skills (SKILL.md folders under .github/skills), custom agents (.github/agents profiles), and MCP servers such as Playwright. It explains when to use each and how they combine, using examples like a quality-checks skill and an accessibility-review agent. Useful as a concrete reference for the repo layout Copilot reads, with a pointer to the community Awesome Copilot collection.

GitHub CopilotModel Context ProtocolPlaywright+1
Awesome Copilot

coding-agents, prompting, mcp· Published and added 12 Oct 2026

endorlabs.comarticle🧠 AI

Context Engineering for Application Security | Endor Labs

Endor Labs whitepaper on using context engineering to make AI coding assistants produce secure code. It covers secure prompting (priming, decomposition, refinement with design-spec and test-first patterns), reusable system rules such as Cursor rules and the CSA R.A.I.L.G.U.A.R.D. framework, and external SAST/SCA tools wired in through MCP servers with a rule that triggers scans. It also covers the costs and risks: extra token use, models ignoring rules, untrusted community rules, and MCP server supply-chain threats. It cites figures such as 62% of AI-generated solutions containing flaws and a 77.5% reduction in weaknesses from recursive prompting.

CursorModel Context ProtocolClaude+1
Endor LabsOWASPCloud Security Alliance

prompting, coding-agents, llm-apps· Published and added 12 Oct 2026

endorlabs.compaper🛡️ Security

State of Dependency Management 2025 | Endor Labs

Endor Labs' 2025 State of Dependency Management report examines how AI coding agents and MCP servers add supply chain risk. Researchers analysed 10,663 GitHub MCP server repositories and tested AI-generated dependency recommendations across PyPI, npm, Maven and NuGet, finding agents import vulnerable or non-existent packages. MCP servers are immature: 75% are built by individuals, 41% lack license info, and 82% use sensitive APIs. The report advises treating AI-generated code as untrusted third-party input subject to code review, SAST/SCA and dependency governance.

Model Context ProtocolGitHubPyPI+3
Henrik Plate

Supply Chain, AI Security· Published and added 12 Oct 2026

github.comrepo🧠 AI

sepehr071/iran-mcp

iran-mcp is an open-source catalog of 39 MCP servers (488 tools) that let AI agents query Iranian websites such as Digikala, Torob, Divar, Snappfood, Jabama, Paziresh24, TSETMC and qavanin.ir, with prices normalised to Toman. Most servers are unofficial, read-only Python packages run with uvx; three are official hosted servers. It ships Claude Code plugins, Agent Skills, bundles, proxy lists and a machine-readable servers.json.

Model Context ProtocolPythonPyPI+11
DigikalaTorobDivar+10

mcp, coding-agents· Added 24 Oct 2026, published 11 Oct 2026

adversa.aiarticle🛡️ Security

Top MCP security resources — October 2026

Adversa AI's October 2026 MCP security roundup, aggregating and synthesizing 15 resources: authentication-bypass vulnerabilities in LiteLLM's MCP endpoint (CVE-2026-59822, now CISA KEV), Grafana's MCP server session spoofing/SSRF (CVE-2026-19516), an MCP Python SDK OAuth-fallback flaw exploited by a malicious server returning a 404, and an Obot gateway route-matching bypass reopening GHSA-vw82. It also covers detection failures (two malicious MCP servers passing five scanners including Cisco mcp-scanner and Snyk agent-scan, 12% of 82,000 public MCP configs hardcoding secrets), a malicious npm wallet-signing package (gadgethumans-mcp), the A2M agent-hijacking attack technique, and CoSAI's MCP Security v2.0 governance model.

Model Context ProtocolLiteLLMnpm+3
CVE-2026-59822CVE-2026-59821CVE-2026-19516+6

AI Security, AppSec, Identity & Access· Published and added 8 Oct 2026

latent.spacearticle🧠 AI

Can a Cloud-Native Harness Make Agents Reliable Beyond the Desktop?

Latent Space interviews Stacklok founders Craig McLuckie and Joe Beda (Kubernetes co-creators) about Mecatl, an open-source "cloud-native harness" for coding agents that separates the agent loop from local tool execution, session state and model provider so enterprises can run and govern agents centrally rather than on individual desktops. The piece also covers Stacklok's earlier pivot from supply-chain security to ToolHive, an open-source platform/Kubernetes operator for running and governing MCP servers, and a not-yet-open-sourced "AI Gateway" focused on access control, budgets and provider routing for regulated enterprises (banks, telcos, semiconductor firms). The framing draws an explicit analogy to how Kubernetes decoupled enterprises from cloud providers, arguing agent harnesses need the same "cattle not pets" treatment to scale beyond desktop tools like Claude Code, Codex and GitHub Copilot.

KubernetesModel Context ProtocolDocker+4
StacklokMecatlToolHive+8

agents, ai-infra, mcp· Published and added 7 Oct 2026

vulnerablemcp.inforepo🛡️ Security

The Vulnerable MCP Project — MCP vulnerability database

The Vulnerable MCP Project is a curated, continuously growing database of security vulnerabilities and attack techniques specific to the Model Context Protocol ecosystem. Entries cover concrete CVEs (e.g. CVE-2025-68143/68144/68145 in Anthropic's mcp-server-git), transport-layer SDK flaws (cross-client response leakage, missing DNS rebinding protection in the official TypeScript/Python SDKs), unauthenticated/0.0.0.0-bound servers enabling RCE (MCPJam inspector, MCP Inspector, Grafana MCP), command/path injection in dozens of third-party servers (gemini-mcp-tool, mcp-server-kubernetes, Framelink Figma MCP, Zen MCP, filesystem-mcp), SSRF chains reaching cloud metadata (MarkItDown MCP, mcp-fetch-server), and a large set of AI-specific attacks: tool poisoning, trigger-phrase data exfiltration, prompt injection via GitHub issues, Jira and Google Docs, rug-pull tool mutation, and cross-server tool-name collisions. It functions as the de facto vulnerability registry for the MCP ecosystem, useful for tracking disclosed issues before patching or adopting third-party MCP servers.

Model Context ProtocolCursorKubernetes+3
CVE-2025-68143CVE-2025-68144CVE-2025-68145+3

AI Security, AppSec· Added 6 Oct 2026

x.comthread🧠 AI

Dave Gilbert (@docgotham) on X

A Twitter/X thread reacting to OpenAI's announcement that ChatGPT Sites can now host MCP servers, including turning plugin extensions into deployable MCP servers (e.g. "@sites create a todo list that I can use in ChatGPT"). User Dave Gilbert (@docgotham) flags a concrete operational bug: with a ChatGPT Pro account, custom MCP servers can't be refreshed — disconnecting/reconnecting or even deleting and re-adding a server still serves the old cached plugin version after an update.

Model Context ProtocolChatGPT
OpenAI

mcp· Published and added 2 Oct 2026

x.comthread🧠 AI

Average AI Bro (@AverageAiBro) on X

Claude Code added a `claude --desktop` command that opens the Desktop app on the current directory or a resumed/continued session, plus `claude plugin configure` to view a plugin's options. Bundled .mcpb MCP servers can now have their settings set at `plugin install --config` time so they start immediately without a manual Configure step. The post also notes CLAUDE_CODE_DISABLE_WEB_FETCH to disable WebFetch and an allowedProviders setting to restrict which API providers a managed machine can use.

Claude CodeModel Context Protocol
AnthropicClaude Desktop

coding-agents, mcp· Published and added 30 Sep 2026

Showing 30 of 91

Show more