Controllare lo stato dell'ordine

Entra a far parte di una comunità di amanti dei libri di tutto il mondo e ottieni numerosi vantaggi. Crea un account gratuito

Punto Poste 5.49 € Punto Poste 5.49 € Corriere DHL 6.99 € Corriere GLS 5.99 € Punto GLS 4.49 € Corriere Bartolini 4.49 € Punto Bartolini 3.49 €

Contatto

Come acquistare

Aiuto

Il mio account

▸ Vuoto :-(

SECURING THE MODEL CONTEXT PROTOCOL

Name: SECURING THE MODEL CONTEXT PROTOCOL
Brand: Staten House
SKU: 54225888
Price: 24.19 EUR
Availability: InStock
Author: Abhay Salpekar
ISBN: 9798907335714

Abhay Salpekar

Lingua

Inglese

Libro In brossura

Codice Libristo: 54225888

Casa editrice Staten House, ottobre 2026

Who This Book Is ForThis book is written for the people who have to make MCP deployments safe in pra... Descrizione completa

Codice Libristo: 54225888

59 b

Nuovi

24.19 €

Magazzino esterno Inviamo tra 9-13 giorni

Fino a 30 giorni per il reso

Who This Book Is For
This book is written for the people who have to make MCP deployments safe in practice, and it's written to be useful to three overlapping audiences at once, each of whom will naturally lean on different parts of it:

Security engineers and practitioners evaluating which servers to trust, designing authentication architectures, and responding when something goes wrong - Parts I and II are written primarily for you.
Software architects and developers wiring agents into production systems, who need to understand not just what to build but why the defaults they inherit from an SDK or a registry carry real risk - Chapters 3, 6, 7, and 11 are especially built around your work.
Enterprise security leaders and CISOs who have to answer for the result when something goes wrong, translate technical risk into governance and board-level reporting, and navigate a regulatory landscape that is moving faster than most had expected - Chapters 9 and 14, and the closing playbook in Chapter 15, are written with you specifically in mind.

The book assumes you already understand what MCP is and why your organization is adopting it; it does not assume you have a settled view of how to secure it, because as of mid-2026, very few organizations do.