Why RiskyPlugins Has a Hosted MCP Server
The hosted MCP endpoint lets agents query extension findings directly, with API-key access and usage controls. Here is the workflow it supports.
Copying a scorecard into an assistant loses context. The summary may omit the scanned version or the finding that explains the score. Then someone has to return to the browser and fetch the missing detail.
I added a hosted MCP service so an assistant can query RiskyPlugins during the investigation. It can work with the available analysis records while the user stays in the same workflow.
Keep the evidence with the request
An extension name alone is a poor identifier. Names can be reused across stores, and a familiar publisher can ship a compromised version. A useful lookup starts with the marketplace and exact extension, then checks the analysis available for it.
The service exposes RiskyPlugins data through authenticated tool calls. The API-key and quota controls apply at that boundary, and usage records make those calls inspectable. The setup guide contains the endpoint and client configuration. The API reference documents the HTTP interface for callers that do not use MCP.
I want a workflow where an assistant can search for an extension, examine the evidence and explain any gaps before asking to install it. When a record is stale or incomplete, that limitation needs to survive into the answer.
Access to a report does not approve an install
MCP supplies a way to call tools. The client still decides which tools it makes available and what actions require approval. Adding this endpoint to an assistant should not silently grant permission to change a machine's software.
The same applies to the assessment itself. Static findings and AI-assisted review can be wrong. A caller should retain the source of the finding and avoid converting a risk score into a claim that an extension is safe.
I wrote about a concrete failure in the Nx Console investigation: our scrape missed the malicious release window. A callable service is only useful if it tells the caller what it actually observed.
Operating the service
Hosted access needs limits because queries consume shared resources. Keys also need a revocation path, and users need to understand what their plan allows. The current pricing page is the reference for those limits; this post should not carry a second, ageing copy of them.
The wider product goal is to make extension evidence available where a decision is being made. Someone using the website should be able to inspect a report. An automated workflow should be able to request that report with the same care about versions and missing data.