VS Code OpenChainBench Resource/Perp DEX security track record: days without a recorded exploit, live ·…
How to: VS Code OpenChainBench Perp DEX security track record: days without a recorded exploit, live ·…
Add OpenChainBench to VS Code
-
01
Open .vscode/mcp.json and merge this in. Keep any servers already there.
{
"servers": {
"openchainbench": {
"type": "http",
"url": "https://openchainbench.com/api/mcp/mcp"
}
}
}-
02
Save the file and restart VS Code.
-
03
Perp DEX security track record: days without a recorded exploit, live ·… is surfaced wherever your client lets you attach context. It is context to attach, not an action to run.
-
04
If it does not appear, check that OpenChainBench is connected and that you are looking at its resources rather than its tools.
Requires agent mode. MCP: Open User Configuration puts the same block in every workspace. VS Code docs
Same resource, other clients
Read from the server itself, by connecting to it and calling resources/list on 24 September 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.