The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
I graded the official MCP servers. Two got an A, one got an F — and the most useful finding came from a layer nobody else measures.
mcp-vitals (open source) grades an MCP server's reliability A–F across three layers: static schema quality, behavioral tests run against the live server, and — the novel part — agent-usability: hand an LLM the tool list and a real task, and see if it picks the right tool and builds a valid call.
Results on the official reference servers:
• memory — A (94)
• everything — A (92)
• filesystem — C (71)
• sequential-thinking — F (57)*
The finding that matters came from the agent-usability layer. On the filesystem server, a model given a "read this file" task couldn't tell read_file from read_text_file and picked the tool that doesn't exist. A security scanner or a static grader never sees that — but it silently breaks agents in production.
*The F is honest: sequential-thinking's single tool needs a payload my schema-only generator can't synthesize, so the behavioral layer couldn't exercise it. A conservative grader that won't vouch for what it can't verify — I document that plainly in the report.
Security scanners tell you a server is safe. mcp-vitals tells you if it's any good.
Live report → https://enached134-ctrl.github.io/mcp-vitals
Repo (MIT, drop-in GitHub Action) → https://github.com/enached134-ctrl/mcp-vitals
enached134-ctrl.github.io
The State of MCP Reliability — graded A–F
I graded the official MCP reference servers for reliability and agent-usability. Two got an A, one got an F. Open-source CLI + GitHub Action.
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Trending
Claude
Claude has entered the design space. How are you using it?
Contra University
Learn from expert creatives how to earn more using next-gen AI tools.
Brand Design
The best brand designers are on Contra. Scroll to see what's trending in brand design. What are you building?
creativeaiflow
Creative AI workflows are evolving. What tools do you use, and what are their strengths and weaknesses?
freelancerlife
Freelancer life is wins, pivots, and everything in between. What’s yours right now?
Related posts
10 SOPs Every Business Should Have
A business shouldn’t rely on memory. It should run on systems.
Here are 10 Standard Operating Procedures (SOPs) every growing business needs:
1. File Management SOP
2. Client Onboarding SOP
3. Email Management SOP
4. Calendar & Meeting Management SOP
5. Task & Project Management SOP
6. Invoicing & Payment Collection SOP
7. Employee/Contractor Onboarding SOP
8. Customer Support SOP
9. Document & Knowledge Management SOP
10. Client Offboarding SOP
Without documented processes, businesses often experience:
- Constantly answering the same questions.
- Time wasted figuring out “how things are done.”
- Inconsistent client experiences.
- Missed tasks and avoidable mistakes.
- Slow onboarding for new team members.
- Operations that depend on one person’s memory.
A well-documented SOP library creates consistency, improves efficiency, and makes your business easier to scale.
If your business is missing these systems, I’d love to help.
I design clear, professional SOPs that simplify operations, improve team productivity, and keep your business running smoothly, whether you’re documenting one workflow or building a complete operations manual.
Let’s build systems your business can grow on.
Project: Operations Documentation & SOP System
Problem:
The business had no standardized file management process, leading to inconsistent file naming, disorganized folders, duplicate documents, and wasted time searching for important files.
Challenges:
Inconsistent file naming...
Project: Operations Documentation & SOP System
Problem:
The business had no standardized file management process, leading to inconsistent file naming, disorganized folders, duplicate documents, and wasted time searching for important files.
Challenges:
Inconsistent file naming conventions.
Poor folder organization.
Duplicate and outdated file versions.
Difficulty locating documents quickly.
Lack of clear ownership and access control.
Solution:
Designed a comprehensive File Management Standard Operating Procedure (SOP) that established standardized file naming conventions, folder structures, version control, permission guidelines, and maintenance best practices to ensure consistent document organization across the business.
Results:
Improved file organization and accessibility.
Reduced time spent searching for documents.
Minimized duplicate files and version confusion.
Established a repeatable document management process.
Increased operational consistency and team efficiency.
