Audit the MCP servers in your setup with Claude Code

Prosy has 9 MCP servers connected to Claude Code and asked it to check the setup without changing anything. The list in .mcp.json was not complete.

Done with Claude CodeModerateOctober 31, 2026

What was done

Prosy has 9 MCP servers connected to Claude Code and asked it to check the setup without changing anything. The list in .mcp.json was not complete. The answer showed 4 local and 3 remote servers, 2 forgotten ones from old projects and 3 risky ones: a GitHub token in plain text, file access to the whole home folder and a package with no pinned version, but he does not show what he fixed.

How to do it

Paste the prompt into the tool, and replace the text in brackets with your own.
Read the answer through. Do not send, delete or publish anything until you have seen it yourself.
Check the original before you trust a figure, a name or a date.

Try it with Claude Code

Audit every MCP server that [tool] can load. Check [config files], the project folders and installed plugins. For each server: where it is defined, whether it is local or remote, and what it can reach in files, network and tokens. Flag plain-text secrets, file access wider than one project and packages without a pinned version. Mask every secret. Change nothing, and show me the list before I fix anything. You are done when every server has an assessment.

Replace text in brackets with your own.

Done when. Every server has an assessment.

Read the original

X · October 28, 2026

Check that your coding agent really ran the tests
Rohit is a security engineer who went through every time his coding agent said all tests pass over the last 30 days. Of 239 claims, 125 were backed by a passing test run after the last edit.
Claude Code X · Nov 2026
Make lots of clothing for your game with Codex
The developer behind the TESSERACT account is building a desktop pet app. The developer told Codex to hook itself up to the design program Marvelous Designer and make about 10 outfits.
Codex X · Oct 2026
Find what slows your websites down with parallel agents
A developer pulled out which pages used the most server time over the last day, then set four Grok agents to work, one per site. Each agent first took a baseline and tested three possible explanations. In 20 minutes they found and fixed, among other things, a database query that went from 550.7 to 0.45 milliseconds and a page that went from 228 to 11. He has shared the setup as open source.
Grok @illyism on X · Nov 2026
Move old research code to a safer language with agents
From Google, the company behind Gemini. According to Google, an agent in Antigravity moved the core of a 174,774 line Fortran and C ocean model to Rust in 59 minutes. It first recorded the original's output across 100 random runs, then planned all 264 files and rewrote the code. It found six old bugs, and the new code ran 1.88 times faster using about half the memory. The figures are Google's own.
Valgfri agent Google (the company behind Gemini) · Nov 2026

A short email each morning with five concrete examples of what people use AI agents for. Each example links to its source. You can unsubscribe at any time.

What was done

How to do it

Try it with Claude Code

More examples

Check that your coding agent really ran the tests

Make lots of clothing for your game with Codex

Find what slows your websites down with parallel agents

Move old research code to a safer language with agents

Five agents a day